From: DervishD <zsh@dervishd.net>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH? - Re: Bug? in complist when filenames are longer than the screen
Date: Tue, 4 Oct 2005 12:47:40 +0200 [thread overview]
Message-ID: <20051004104740.GA19231@DervishD> (raw)
In-Reply-To: <20051004113817.4abc3e35.pws@csr.com>
Hi Peter :)
* Peter Stephenson <pws@csr.com> dixit:
> I haven't been able to see any problem with long prompts, even doing some
> fairly hairy things, so I may be using different options. Are there still
> bugs with long prompts or long file names after the patch?
After the patch, long file names causes screen mess and crashes,
but not infinite loops. Long prompts doesn't seem to be affected,
I've been able to reproduce the problem with and without a very long
PS1. The options doesn't seem to be the culprit, because I've tested
with "zsh -f" and *without* /etc/zshenv.
> Also, does the long-prompt patch need to be applied to 4.2?
I first hit the bug in my 4.2.5, so...
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-04 10:47 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
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 [this message]
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=20051004104740.GA19231@DervishD \
--to=zsh@dervishd.net \
--cc=pws@csr.com \
--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).