zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Some possible bugs...
Date: Wed, 26 May 1999 08:20:53 +0200 (MET DST)	[thread overview]
Message-ID: <199905260620.IAA07416@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Aldo Cortesi's message of Wed, 26 May 1999 14:03:19 +1000


Aldo Cortesi wrote:

> While using it, though, I've run accross a couple of
> problems that force me to use bash for certain tasks. 
> Here they are:

Please try the newest development version which you can get at:

http://www.ifh.de/~pws/computing/
-rw-r--r--   1 pws  quadrics  759988 May 19 13:48 zsh-3.1.5-pws-19.tar.bz2
-rw-r--r--   1 pws  quadrics  368884 May 19 13:48 zsh-3.1.5-pws-19.doc.tar.gz
-rw-r--r--   1 pws  quadrics  249242 May 19 13:48 zsh-3.1.5-pws-19.doc.tar.bz2
-rw-r--r--   1 pws  quadrics  937267 May 19 13:48 zsh-3.1.5-pws-19.tar.gz

...and then we had some patches after that -- see the mailing list
archive at http://www.zsh.org/mla.

> 	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);
> 		}

`setopt nopromtcr' -- which has only recently be added to the FAQ.

> 	Running zsh with invalid command-line arguments
> 	causes a coredump. For instance
> 		zsh -asdfas
> 	produces a very nice corefile on my machine. 

This is still there... no doubt someone will have a look at it.

> 	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. 

We have this discussion again and again... Completion in quotes is
different in zsh because some time ago it was decided to let it work
there (almost) as without the quotes. So if you do ls "one t<TAB>
zsh doesn't think that the quotes are intended to just quote the
filename because for that you simply don't need the quotes. If you do
ls one<TAB> zsh will give you ls one\ two\ , quoting the string as
needed.
However, the behavior shown in your mail looks really weird, I might
have a look at it (but quoting and completion is a terribly
complicated issue).

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-05-26  6:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-26  6:20 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-05-27 11:10 Sven Wischnowsky
1999-05-27  6:44 Sven Wischnowsky
1999-05-27  9:34 ` Bart Schaefer
1999-05-26  4:03 Aldo Cortesi

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=199905260620.IAA07416@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).