From: DervishD <zsh@dervishd.net>
To: Andrey Borzenkov <arvidjaar@newmail.ru>
Cc: Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Bug? in complist when filenames are longer than the screen
Date: Mon, 3 Oct 2005 20:48:22 +0200 [thread overview]
Message-ID: <20051003184822.GA3240@DervishD> (raw)
In-Reply-To: <200510032145.07748.arvidjaar@newmail.ru>
Hi Andrey :)
* Andrey Borzenkov <arvidjaar@newmail.ru> dixit:
> On Monday 03 October 2005 18:45, DervishD wrote:
> > Hi all :)
> >
> > I'm not sure if this is a bug or if I'm doing anything wrong, but
> > I can reproduce it even without reading RC's (neither /etc/zshenv
> > nor /etc/zshrc exist, and I run zsh with "-f").
> >
> > $ print $ZSH_VERSION
> > 4.2.5
> > $ touch a b c filename1 filename2 d e
> > $ zmodload zsh/complist
> > $ COLUMNS=3
> > $ ls <TAB><TAB><TAB><TAB><UP><DOWN>
> >
> > The screen messes up and, depending on the filenames, zsh
> > sometimes segfaults or hangs.
> It would be nice to have exact recipe how to reproduce a crash preferably
> starting with zsh -f. I have screen corruption but not (OK I am not sure what
> sensibly can be done on 3 column width :)
The above, when run after "zsh -f" and making sure you don't have
any /etc/zshenv not protected by "[[ -o rcs ]]", causes a hangup (not
a crash) in my system. Unfortunately the crash happens randomly, and
seldom. The common case is a hangup, with zsh eating lots of CPU, but
from time to time it crashes.
With 3 column width you can call "ls" if your PS1 is short enough
XDDDD. BTW, this has happened to me with COLUMNS=100 and a very long
file name, that's why I discovered it. First zsh messed up the
screen, and when I hit <UP> the shell crashed. I haven't been able to
reproduce the crash with that particular example, zsh always hangs
now, but I have had crashes and hangs with the example I provide
above.
> Jokes aside, I do confirm screen corruption during normal completion under
> konsole and linux console. This happens with long filenames
Exactly. Any filename whose name length is greater or equal to
$COLUMNS seems to cause the problem.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...
next prev parent reply other threads:[~2005-10-03 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 14:45 DervishD
2005-10-03 17:45 ` Andrey Borzenkov
2005-10-03 18:48 ` DervishD [this message]
2005-10-04 2:07 ` Bart Schaefer
2005-10-04 4:39 ` PATCH? - " Bart Schaefer
2005-10-04 9:48 ` DervishD
2005-10-04 10:38 ` Peter Stephenson
2005-10-04 10:47 ` DervishD
2005-10-04 11:19 ` Peter Stephenson
2005-10-04 11:31 ` DervishD
2005-10-04 14:32 ` Bart Schaefer
2005-10-04 14:09 ` Bart Schaefer
2005-10-04 16:37 ` DervishD
2005-10-04 16:11 ` Bart Schaefer
2005-10-04 17:13 ` DervishD
2005-10-04 19:24 ` Andrey Borzenkov
2005-10-04 20:41 ` DervishD
2005-10-06 16:01 ` Bart Schaefer
2005-10-06 16:31 ` DervishD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051003184822.GA3240@DervishD \
--to=zsh@dervishd.net \
--cc=arvidjaar@newmail.ru \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).