Atuin's keybinds do not work in Ghostty with FISH #6860
-
|
Literally, what the title says. I am not able to use Atuin's keybinds for the Up and Down arrow keys in Ghostty. I either forced to disable Atuin entirely, or switch to another terminal emulator. Can someone please help me? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 17 replies
-
|
Make sure that your atuin keybinds aren't conflicting with either system keybinds or with Ghostty's default keybinds (see |
Beta Was this translation helpful? Give feedback.
-
|
I'm on Linux (Nobara 41) BTW, I do not use macOS. Also, I am using the default config (including keybinds) for Atuin. |
Beta Was this translation helpful? Give feedback.
-
|
What Atuin's keybindings don't work? Just up and down, or do they have some modifier key? Does |
Beta Was this translation helpful? Give feedback.
-
|
I did try using both options, but I wasn't able to get any different results. |
Beta Was this translation helpful? Give feedback.
-
|
Do you happen to know if it's possible to check if Atuin was loaded correctly? I've never used Atuin but that history matching on up arrow that was happening is what Fish's built-in history search looks like, so I think it's possible that Atuin never loaded. |
Beta Was this translation helpful? Give feedback.
-
|
No, that is not Fish's built-in history search. That was Atuin. |
Beta Was this translation helpful? Give feedback.
-
|
@FlawlessCasual17, have you found a solution to this? |
Beta Was this translation helpful? Give feedback.
-
@pablohenriq, No, I have not. Also, I have switched to Wezterm because I don't want to try configuring Ghostty just so I can use Atuin. I still have Ghostty installed, just in case a bug fix for the Atuin problem is solved. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also having problems with atuin, more specifically I can't type in the search with ghostty. Works in other terminal emulators, and also works inside a tmux in ghostty. However just changing TERM does not help. |
Beta Was this translation helpful? Give feedback.
-
I wonder if Atuin perhaps has issues with the Kitty keyboard protocol in that case. I really don't have any other guesses. |
Beta Was this translation helpful? Give feedback.
-
|
I use Atuin and haven't had any issue (on both macOS and Linux), but perhaps I don't use all the binds you do. Can you please help by telling me the US standard physical keys you're pressing that aren't working? (And advise if you're using a non-US logical layout) |
Beta Was this translation helpful? Give feedback.
-
|
I was a fish user previously for many years, I only recently switched off of fish (weeks ago), so I have a fully working fish install. With fish on both macOS and Linux up/down arrows work completely fine. For good measure, I also tried a zero-config fish configuration: And up/down also work. Can you try that yourself as well? If that works, I believe the problem is somewhere within your Fish configuration. This could still be a problem with how Ghostty is encoding up/down for whatever you're configuring, but the way I can reproduce it is somewhere in your fish config. I also know plenty of Ghostty users use Atuin (based on community feedback -- no tracking) and given how quiet this issue is, I suspect this is limited to your configuration as well. |
Beta Was this translation helpful? Give feedback.
-
|
In Wezterm, I opened a new Ghostty instance with Bash using Here is the log from running the ghostty command I used: (I hope it helps) Log |
Beta Was this translation helpful? Give feedback.
-
|
@mitchellh I might have an idea. This could possibly solve the issue with Ghostty and Atuin. Is it currently possible to map a key to a shell command like |
Beta Was this translation helpful? Give feedback.
-
|
Not really, the closest you can get is |
Beta Was this translation helpful? Give feedback.
-
|
I tried binding from FISH, it didn't work either. I used the commands defined from running, # output of `atuin init fish` with no pipeline
set -gx ATUIN_SESSION (atuin uuid)
set --erase ATUIN_HISTORY_ID
function _atuin_preexec --on-event fish_preexec
if not test -n "$fish_private_mode"
set -g ATUIN_HISTORY_ID (atuin history start -- "$argv[1]")
end
end
function _atuin_postexec --on-event fish_postexec
set -l s $status
if test -n "$ATUIN_HISTORY_ID"
ATUIN_LOG=error atuin history end --exit $s -- $ATUIN_HISTORY_ID &>/dev/null &
disown
end
set --erase ATUIN_HISTORY_ID
end
function _atuin_search
set -l keymap_mode
switch $fish_key_bindings
case fish_vi_key_bindings
switch $fish_bind_mode
case default
set keymap_mode vim-normal
case insert
set keymap_mode vim-insert
end
case '*'
set keymap_mode emacs
end
# In fish 3.4 and above we can use `"$(some command)"` to keep multiple lines separate;
# but to support fish 3.3 we need to use `(some command | string collect)`.
# https://fishshell.com/docs/current/relnotes.html#id24 (fish 3.4 "Notable improvements and fixes")
set -l ATUIN_H (ATUIN_SHELL_FISH=t ATUIN_LOG=error ATUIN_QUERY=(commandline -b) atuin search --keymap-mode=$keymap_mode $argv -i 3>&1 1>&2 2>&3 | string collect)
if test -n "$ATUIN_H"
if string match --quiet '__atuin_accept__:*' "$ATUIN_H"
set -l ATUIN_HIST (string replace "__atuin_accept__:" "" -- "$ATUIN_H" | string collect)
commandline -r "$ATUIN_HIST"
commandline -f repaint
commandline -f execute
return
else
commandline -r "$ATUIN_H"
end
end
commandline -f repaint
end
function _atuin_bind_up
# Fallback to fish's builtin up-or-search if we're in search or paging mode
if commandline --search-mode; or commandline --paging-mode
up-or-search
return
end
# Only invoke atuin if we're on the top line of the command
set -l lineno (commandline --line)
switch $lineno
case 1
_atuin_search --shell-up-key-binding
case '*'
up-or-search
end
end
bind \cr _atuin_search
bind \eOA _atuin_bind_up
bind \e\[A _atuin_bind_up
if bind -M insert > /dev/null 2>&1
bind -M insert \cr _atuin_search
bind -M insert -k up _atuin_bind_up
bind -M insert \eOA _atuin_bind_up
bind -M insert \e\[A _atuin_bind_up
end
|
Beta Was this translation helpful? Give feedback.
-
|
I do have the same problem, I'm using the french traditional layout AZERTY (not the new one). fish --no-config
atuin search -iBut it's not working when you want to open the history view from atuin, it works with crtl+r, but not with the up and down keys. if status is-interactive
# Commands to run in interactive sessions can go here
atuin init fish | source
endWith the default terminal and fish on fedora, the shortcut is working. Additional info, the shortcut is working, when launching tmux with fish as default shell in ghostty. Any workaround or fix ? |
Beta Was this translation helpful? Give feedback.
-
|
Hey Everyone, I have an update: For whatever reason, Atuin is working just fine in the Ghostty terminal now. I installed the variant from the |
Beta Was this translation helpful? Give feedback.
Hey Everyone, I have an update:
For whatever reason, Atuin is working just fine in the Ghostty terminal now. I installed the variant from the
nobara-updatesRPM repository, and it seems to be working just fine. Maybe the variant from theTerraRPM repository is buggy?