From: Sven Wischnowsky <wischnow@berkom.de>
To: zsh-workers@sunsite.dk
Subject: Re: completion in quotes - " vs ' - no suffix added
Date: Tue, 14 May 2002 09:44:11 +0200 [thread overview]
Message-ID: <15584.49227.780505.590251@wischnow.berkom.de> (raw)
In-Reply-To: <1021313089.2926.10.camel@localhost.localdomain>
Borsenkow Andrej wrote:
> ...
>
> so correctly escaped filename is inserted but is not unquoted when
> testing for file type.
That's exactly the point -- the code in compresult.c responsible for
this is *very* old and, ahem, hasn't been updated for this. The patch
I sent is only for the quoting issues Bart described in the mail I
replied to, not for the file-testing code -- it was already hard
enough without that ;-}
> > One oddity is that typing the closing quote after `ls "a\\ d/' does not
> > auto-remove the slash, but I don't think that's strictly a bug.
> >
>
> May be it should; but then it becomes increasingly more complicated with
> nested quotes. Besides, you may want to continue quoted word ...
I think we decided against it exactly for this reason. I'll have more
to say about this when I start talking about what we can do to improve
suffix handling.
So the next steps are to get the file-type testing right. I'd like to
do that more thoroughly to finally be able to implement this other
thing we've been talking about, where a space as a file-type character
(with LIST_TYPES) isn't counted to allow tighter packing of rows in
listings.
That's also the reason why I haven't tried to change the difference in
quoting in listings Andrej pointed out. To repeat: we meant to make it
always be quoted. But with display strings and what not the shell code
is able to defeat this. Personally, I prefer it this way, so we might
want to make this be controlled by a style. But then the shell code
would be responsible to handle different quoting behaviour in some
cases, namely: whenever it uses display strings. If there are no
display strings, the C-code could use them internally for the unquoted
form.
Do others have any opinions on this?
Bye
Sven
--
Sven Wischnowsky wischnow@berkom.de
next prev parent reply other threads:[~2002-05-14 7:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 7:54 Borsenkow Andrej
2002-05-06 15:31 ` Bart Schaefer
2002-05-08 7:37 ` Sven Wischnowsky
2002-05-08 8:49 ` Borsenkow Andrej
2002-05-08 12:39 ` Sven Wischnowsky
2002-05-08 15:38 ` Bart Schaefer
2002-05-13 9:30 ` Sven Wischnowsky
2002-05-13 10:14 ` Borsenkow Andrej
2002-05-13 17:33 ` Bart Schaefer
2002-05-13 18:04 ` Borsenkow Andrej
2002-05-14 7:44 ` Sven Wischnowsky [this message]
2002-05-14 14:23 ` Bart Schaefer
2002-05-14 14:31 ` Bart Schaefer
2002-05-14 15:23 ` Sven Wischnowsky
2002-05-14 15:35 ` Borsenkow Andrej
2002-05-15 7:37 ` Sven Wischnowsky
2002-05-21 8:06 ` PATCH: " 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=15584.49227.780505.590251@wischnow.berkom.de \
--to=wischnow@berkom.de \
--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).