Options not found: exec_exit_mark, edit_marker[_error]

[kriswilk]

Running on NixOS with ble.sh installed from nixos-unstable and sourced by adding it to programs.bash.initExtra. ble.sh works as expected but I want to disable the [ble: ...] messages. So (as per the docs) my .blerc is:

# Disable EOF marker like "[ble: EOF]"
bleopt prompt_eol_mark=''
# Disable error exit marker like "[ble: exit %d]"
bleopt exec_errexit_mark=
# Disable elapsed-time marker like "[ble: elapsed 1.203s (CPU 0.4%)]"
bleopt exec_elapsed_mark=
# Disable exit marker like "[ble: exit]"
bleopt exec_exit_mark=
# Disable some other markers like "[ble: ...]"
bleopt edit_marker=
bleopt edit_marker_error=

Most of this works. However, when I open my terminal, I get the following errors:

bleopt: option `exec_exit_mark' not found
bleopt: option `edit_marker' not found
bleopt: option `edit_marker_error' not found

To aid debugging I tried to run the requested "summary" command:

$ ble summary
ble (ble.sh): unrecognized subcommand 'summary'.

This is despite having what seems to be a recent version of ble.sh:

$ ble version
ble.sh, version 0.4.0-devel3+1a5c451c (noarch)

What am I missing?

[akinomyoga]

This is despite having what seems to be a recent version of ble.sh:

$ ble version
ble.sh, version 0.4.0-devel3+1a5c451c (noarch)

This is old. Could you use the latest master branch or the nightly build if you want to use recent options?

[kriswilk]

Thanks for the quick reply! I assumed that the latest tagged release matched the docs. I'm relatively new to Nix/NixOS, so I'll have to figure out how to override the package target to pull in the freshest version.

Any chance you'll be tagging a new release? If you did, it would be very easy to update nixpkgs with the new version number and hash, and everyone using that package could enjoy 2+ years of fixes/features. I'd be happy to put in that PR.

It's too bad that the home-manager implementation stalled. But it looks like it was picked up in a new PR. Hope it gets finished so that home-manager installation is as easy as it already is for NixOS at the system level. That said, it relies on the nixpkgs package, so it'll be just as outdated. 😉

[akinomyoga]

I wanted to tag a new release after reviewing the change, but I am currently extremely busy. In addition, even if I tag a new release, I'm not sure if a corresponding PR submitted to Nixpkgs will be merged soon. Nixpkgs lacks the manpower to review all incoming PRs, and it sometimes takes a very long time for a PR to get a reviewer and be merged.

[kriswilk]

Understood. I heard that nixpkgs is no longer accepting new package requests (without PRs) due to the overload. If it will take a long time to get reviewed, then I'd say it's more reason to get a PR for a version bump in the queue.

I look forward to a new release when you find the time to work on it. Thanks for all your effort!!

Until then, I'll be learning about nix overlays to make this work on my own.

[kriswilk]

It turns out that overriding nixpkgs with a newer build of ble.sh is very easy. I discovered the solution in the usual way: by snooping in public github repos. I searched for "language:nix blesh nightly", and voila!

@akinomyoga, this might be worth adding to the ble.sh docs (maybe in this section), especially if you're busy and the gears of nixpkgs PRs turn slowly.

To save others the searching... add this to your home-manager configuration:

programs.bash = {
  enable = true;
  initExtra = ''
    source "$(blesh-share)/ble.sh"
  '';
};

home.packages = with pkgs; [
  (blesh.overrideAttrs {
    version = "nightly-20251019+2f564e6";
    src = fetchzip {
      url = "https://github.com/akinomyoga/ble.sh/releases/download/nightly/ble-nightly-20251019+2f564e6.tar.xz";
      sha256 = "sha256-fpNorzJcKs1vVhaYKgRz5vcs6jsEvdxe3N4F2L81Rc0=";
    };
  })
];

For a system configuration, just replace home.packages with environment.systemPackages.

Notes:

• If you want a different build, change the URL and version attribute.
• To get the correct sha256, just build the configuration and copy the computed hash from the build error.
• The script "blesh-share" is created by the package. It returns the directory in the nix-store where ble.sh lives.