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
I'm not sure since when this happens, but that part of my prompt hasn't changed for quite a while and this happens for a few weeks now, maybe since the z-sy-h 0.5.0 release or since the zsh 5.3 release, but at least with the combination of z-sy-h 0.5.0 and zsh 5.3.1:
Everytime I press Ctrl-L in my xterm, %N inside my prompt shows _zsh_highlight_call_widget instead of e.g. /usr/bin/zsh or -zsh:
I'm not sure if this is an issue with z-sy-h or if I should just not expect %N to always show zsh (with or without path and or the dash indicating a login shell) and should just use $0 instead of %N.
The text was updated successfully, but these errors were encountered:
I can reproduce this without z-sy-h:
```zsh
$ zsh -f
% clear-screen() { zle .$WIDGET -- "$@" }
% zle -N clear-screen
% PS1='%1N %# '
zsh % <^L>
clear-screen %
```
That's with zsh master; with zsh 5.0.7 from debian stable, the last
prompt says "zsh", …
should just use `$0` instead of `%N`.
… so this is an upstream change. I am not sure whether it's a regression
or a bugfix.
Is a change on z-sy-h's side needed?
(I quickly grepped upstream's git, but haven't found anything yet)
I'm not sure since when this happens, but that part of my prompt hasn't changed for quite a while and this happens for a few weeks now, maybe since the z-sy-h 0.5.0 release or since the zsh 5.3 release, but at least with the combination of z-sy-h 0.5.0 and zsh 5.3.1:
Everytime I press Ctrl-L in my xterm,
%N
inside my prompt shows_zsh_highlight_call_widget
instead of e.g./usr/bin/zsh
or-zsh
:Normal prompt:
After Ctrl-L:
How to reproduce:
I'm not sure if this is an issue with z-sy-h or if I should just not expect
%N
to always showzsh
(with or without path and or the dash indicating a login shell) and should just use$0
instead of%N
.The text was updated successfully, but these errors were encountered: