-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Rebinding key error messages in emacs ansi, term, or multi-term terminals #4188
Comments
This does not happen to me. I'm guessing this is because of macOS' broken "eterm-color" terminfo entries. Try something like tic -o ~/.terminfo $TERMINFO/e/eterm-color.ti
# where $TERMINFO is something like "/usr/local/Cellar/emacs-mac/emacs-24.5-z-mac-5.15/share/emacs/24.5/etc/" Also note that even if you get it working, all emacs terminals are rather limited and won't really give a great experience with fish. I suggest using a more full-featured terminal like iTerm. |
i have done |
What did you use as The idea is that you use the path to your "eterm-color.ti" file from your (hopefully somewhat modern) emacs installation. How did you install emacs?
Yes, something weird is happening. We're silencing errors for all binding functions (in Anyway, we should probably find a different way to signal that a key cannot be bound. These error messages should be silenced in the core |
You read my mind. Redirecting stderr to /dev/null like that can hide errors we want to see. I was thinking we should add a |
Yeah I am on emacs 25. |
I've thought about this some more, and I'm leaning towards removing these warnings entirely. In theory, it sounds nice that we warn people that the
Note that I think this is a manifestation of #1035 - we lose the stderr redirection somewhere along the way. |
I'm changing this from the 2.7.0 milestone to the fish-future milestone. The 2.7.0 milestone is now a bug fix only milestone -- no new features beyond those already included. This change in behavior can be included in the fish 3.0.0 release. |
I'm also experiencing this issue. Is there a way to suppress the output in the meantime? |
This silences binding errors due to keys not found in the current termcap config in the default fish bindings. Closes fish-shell#4188, fish-shell#4431, and obviates the original fix for fish-shell#1155
This silences binding errors due to keys not found in the current termcap config in the default fish bindings. Closes fish-shell#4188, fish-shell#4431, and obviates the original fix for fish-shell#1155 It was necessary to re-implement builtin_bind as a class in order to avoid passing around the options array from function to function and as adding an opts parameter to `get_terminfo_sequence` would require otps to be passed to all other builtin_bind_ functions so they could, in turn, pass it to `get_terminfo_sequence`.
fish 3 will not emit warnings for the default bindings (including vi mode) when keys are not found in the for the current |
I just accidentally solved this myself! There was a |
That’s your configuration file, so you simply worked around the problem by not binding the keys in question any more. |
It had old stuff in it that wasn't in my config.fish file anymore and no amount of refreshing was fixing it. I discovered the problem when I was grepping around because fish was complaining that a dir in my path didn't exist, but as near as I could tell that dir wasn't set it my path anywere. But it was still in the |
Silences failing bind commands when terminfo has no backspace key defined. Related to fish-shell/fish-shell#4188
When opening
shell
,ansi-term
, ormulti-term
, some key rebinding error messages show up.Using fisherman.
Seems related to #1155
version 2.6.0
uname -a:
Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64
Literal output:
The text was updated successfully, but these errors were encountered: