You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lukeworth@Lukes-MBP /tmp> function show_prompt_details --on-event fish_prompt
echo fish_prompt received!
lukeworth@Lukes-MBP /tmp> cd a
lukeworth@Lukes-MBP /t/a> prevd
lukeworth@Lukes-MBP /tmp> cdh
a 1) /tmp/a
Select directory by letter or number:
This is particularly annoying because I was using the fish_prompt event to display a wrappable environment status (c.f. #904 (comment)).
As a workaround I am using the fish_postexec event. (Um, if anyone's using vim and this starts breaking plugins, try :set shell=sh to force POSIX shell instead of fish. TIL)
[I] ➜ echo $version
[I] ➜ uname -a
Darwin Lukes-MBP 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64 i386 MacBookPro11,5 Darwin
[I] ➜ echo $TERM
The text was updated successfully, but these errors were encountered:
I just checked and the only non-prompt related usage of fish_prompt (i.e. would be relevant to read) shipping with fish itself is enabling bracketed paste, which begs the question: is bracketed paste intentionally enabled for interactive reads executed by a command?
If yes, then we would stop firing fish_prompt in read and use a new event handler fish_read with an accompanying function to enable bracketed paste when it's fired.
If no, then we would just stop firing fish_prompt in read altogether.