From: Aldo Cortesi <aldo@isetroc.com>
To: zsh-workers@sunsite.auc.dk
Subject: Some possible bugs...
Date: Wed, 26 May 1999 14:03:19 +1000 [thread overview]
Message-ID: <19990526140319.A17252@isetroc.com> (raw)
Hi,
I finally got around to test-driving zsh the other day, and
I liked it enough to make it my default shell. I'm looking
forward to getting to know it well enough to contribute to
it's development.
While using it, though, I've run accross a couple of
problems that force me to use bash for certain tasks.
Here they are:
The last line of output from a program run in the
shell gets overwritten if it doesn't end in a
newline. This is very, very bad, and should not be
allowed to happen even intentionally. For example
the following program produces no visible output
when run in zsh as I have it set up:
int main(){
printf("mundungus");
return(0);
}
Running zsh with invalid command-line arguments
causes a coredump. For instance
zsh -asdfas
produces a very nice corefile on my machine.
I think that tab-completion of filenames containing
spaces is not useful. For instance, if you have two
files called:
"one two three"
"one two five"
and you type
ls "one<tab>"
it completes to "one two". If you press tab
repeatedly you get:
ls "one two one two one two..."
I guess this should really cycle between the two
filenames to be consistent with normal
file-completion. Another problem is that if you
type:
ls "one<tab>"
and get:
ls "one two"
and then type the next couple of characters and
press tab again, like so:
ls "one two f<tab>"
no completion is done at all.
Bash does this type of thing quite nicely. It might
be an idea to take a leaf from their book, so to
speak.
I am running the latest development version (3.1.5).
--
Aldo Cortesi
aldo@isetroc.com
Effing the ineffable...
next reply other threads:[~1999-05-26 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-26 4:03 Aldo Cortesi [this message]
1999-05-26 6:20 Sven Wischnowsky
1999-05-27 6:44 Sven Wischnowsky
1999-05-27 9:34 ` Bart Schaefer
1999-05-27 11:10 Sven Wischnowsky
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=19990526140319.A17252@isetroc.com \
--to=aldo@isetroc.com \
--cc=zsh-workers@sunsite.auc.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).