Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bash: bash_execute_unix_command: cannot find keymap for command #45

Open
onknows opened this issue Feb 7, 2018 · 5 comments
Open

bash: bash_execute_unix_command: cannot find keymap for command #45

onknows opened this issue Feb 7, 2018 · 5 comments

Comments

@onknows
Copy link

onknows commented Feb 7, 2018

On Ubuntu 16.04 after installation when I press cntrl space i see

bash: bash_execute_unix_command: cannot find keymap for command

cntrl k for example is working btw, so it seems to be installed correctly

@onknows
Copy link
Author

onknows commented Feb 7, 2018

Workaround for this issue is to replace in bin/marker.sh

bind -x '"'"$marker_key_get"'":_marker_get'

With

bind -x '"\emg1":"_marker_get"'
bind '"'"$marker_key_get"'":"\emg1"'

@intersel
Copy link

intersel commented Mar 1, 2018

had same bug on debian 8.4
solution of @onknows works perfectly

jtaala added a commit to jtaala/marker that referenced this issue Oct 25, 2018
…or Arch/Manjaro and also Ubuntu 16.04

As provided by onknows - see pindexis#45
@fidian
Copy link

fidian commented Oct 25, 2018

In my .bashrc as a workaround, I have these lines. That way I can still keep the original source unmodified. I'd still prefer to have the workaround implemented.

# Fix issue #45
bind -x '"\emg1":"_marker_get"'
bind '"'"${MARKER_KEY_GET:-\C-@}"'":"\emg1"'

@MagnetonBora
Copy link

Is there any chance to have it resolved without workarounds?

@intika
Copy link

intika commented Apr 17, 2019

Quote from #28

Ok so I finally succeeded to reproduce. It seems be related to Ctrl+space binding in Bash 4+.
Switching the key-binding to something other that Ctrl+space will fix the issue.
You can do that by setting the MARKER_KEY_GET env in .bashrc (before sourcing marker):

export MARKER_KEY_GET='\C-l'
[[ -s "$HOME/.local/share/marker/marker.sh" ]] && source "$HOME/.local/share/marker/marker.sh"

It would be good to try this on the latest tip of the master branch

for me rebinding to ctrl+x do the trick
export MARKER_KEY_GET='\C-X'

nickautomatic added a commit to nickautomatic/.dotfiles that referenced this issue Oct 8, 2020
To quote its README [1]:

"Marker is a command palette for the terminal. It lets you bookmark
commands (or commands templates) and easily retreive them with the help
of a real-time fuzzy matcher."

By default the key binding for marker is Ctrl-Space. However, this seems
to cause issues in Ubuntu so I've followed this suggestion [2] and
side-stepped this issue by binding marker to Ctrl-X instead.

[1] https://github.com/pindexis/marker
[2] pindexis/marker#45 (comment)
nickautomatic added a commit to nickautomatic/.dotfiles that referenced this issue Oct 8, 2020
The previous approach (setting MARKER_KEY_GET) worked ok for me on
Ubuntu 16.04/WSL, but doesn't seem to work with Ubuntu 20.04/WSL2.

However, this alternative approach (suggested [here][1]) seems to
work fine, so let's switch to using this.

Rather than `echo` multiple lines to `.bashrc`, let's use HEREDOC syntax
and `tee` to append all of them in one go. This avoids the need for
fiddly escaping of quote characters.

[1] pindexis/marker#45 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants