Re: completion problem with '291' ok with '274'.

[Ray Andrews <rayandrews@eastlink.ca>]

On 02/10/2015 06:35 PM, Bart Schaefer wrote:
> Mind telling us whether this is "zsh -f" and/or if you've run compinit
> and/or what zstyles are in play?

No, just plain 'zsh'.  I'm running my standard setup, not sure what 
details are relevant.  compinit yes, as always.

styles:

--------------------------------------------------------------------------------------------------------

zstyle ':completion:*:default' list-colors ${(s.:.)LS_COLORS}
zstyle ':completion:*:match:*' original only
zstyle ':completion:*:approximate:*' max-errors 1 numeric
zstyle ':completion:*:expand:*' tag-order all-expansions
zstyle ':completion:*' completer _expand _complete
zstyle ':completion:*' auto-description 'specify: %d'
zstyle ':completion:*' format 'Completing %d'
zstyle ':completion:*' group-name ''
zstyle ':completion:*' list-colors ''
zstyle ':completion:*' list-prompt %SAt %p: Hit TAB 'for more', or the 
char to insert%s
zstyle ':completion:*' menu select=2
zstyle ':completion:*' menu select=long
zstyle ':completion:*' select-prompt %SScrolling active: current 
selection at %p%s
zstyle ':completion:*' use-compctl false
zstyle ':completion:*' verbose true
zstyle ':completion:*:cd:*' ignore-parents parent pwd
zstyle ':completion:*:killall:*' command 'ps -u $USER -o cmd'
zstyle ':completion:*:kill:*' force-list always
zstyle ':completion:*:kill:*' command 'ps -u $USER -o 
pid,%cpu,tty,cputime,cmd'
zstyle ':completion:*:*:kill:*' menu yes select
zstyle ':completion:*:*:kill:*:processes' list-colors '=(#b) 
#([0-9]#)*=0=01;31'
zstyle ':completion:*' matcher-list '' 'm:{a-z}={A-Z}' 
'm:{a-zA-Z}={A-Za-z}' 'r:|[._-]=* r:|=* l:|=*'
--------------------------------------------------------------------------------------------------------

> Chances are both of these are because there actually is a binary named
> "zsh" in the current directory, so it's the first possible completion.

Correct, but 291 'newlines' and then crashes, whereas 274 (tho I have to 
press TAB twice to get past the 'zsh' which is just a link to the 
current binary) stays on the same line and then completes without 
trouble. One sees the list of possible completions, and all is as it 
should be.
> FYI "crash the xterm" is not really what happens.  More likely zsh has
> crashed and the xterm simply exited because the only process that it
> was running has exited.

Ok.
> Try using "xterm -hold" so the window stays
> open until explicitly closed, then you'll be able to see any error
> messages that are generated.  If the xterm goes away even with -hold,
> then you actually are somehow killing the xterm rather than zsh and
> the problem isn't ours ...

I'm actually using 'xfce4-terminal' which seems not to have the '-hold' 
ability.  Starting that from within itself the results are the same, the 
terminal evaporates, leaving the calling terminal. With 'xterm -hold' 
any attempt at completion of anything freezes the xterm solid.  I kill 
it by closing the window. No message. Plain 'xterm' does the same as 
xfce4-terminal--it evaporates back to the calling terminal.
>
> } ... no completion problems with '274'. I went back and forth between
> } '291' and '274' and every time '291' was unstable completing, whereas
> } '274' was fine. Most often '291' caused the xterm to crash.
>
> Could be related to workers/34485, but you may not have directory write
> permission to drop a core file in /usr/local/bin so you'll have to run
> from inside gdb to get a stack trace.

That's new territory for me, so I'll need a primer.

> I can't repro with zsh-5.0.7-293-g0209635 but it's doubtful anything in
> between would have fixed a completion crash.
293 is the same as 291.

274 is still perfect.

Everything is fine with 'zsh -f' (with 293). So then this is something 
specific to my configuration?  Should I narrow it down by elimination?
>