From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: _netscape
Date: Wed, 24 May 2000 10:05:28 +0200 (MET DST) [thread overview]
Message-ID: <200005240805.KAA29939@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Oliver Kiddle's message of Tue, 23 May 2000 17:07:47 +0100
Oliver Kiddle wrote:
> ...
>
> > > Note that _files can no longer complete subdirectories if you give it a
> > > -S option which is something other than a slash. _files should only add
> > > the suffix after a file (and possible after an empty directory).
>
> > Sometimes you want it, sometimes not...
>
> When might you not want it (the slash)? If you don't want to decend
> directories, it would be easier to use compadd * than _files. I'd have
> thought that in the vast majority of cases, the passed suffix would be
> wanted only after a file or empty directory.
When completing only directories.
> ...
>
> > The way suffixes are handled has mostly historical reasons and, yes,
> > it is a bit simple minded. If someone wants to help to improve it, I'd
> > like to have a short and comprehensive list of things one might want
> > to do, so that we can discuss it easliy and find the (hopefully few)
> > basic things we need for that. With that we could then think about
> > changing the code. Ok? (I don't think I'll have much time to think
> > about this...)
>
> I'll try to come up with such a list but it may be a little while before
> I have time. Does anyone know of any parts of the completion system
> where there is an interesting sitation or currently not very good
> handling of suffixes: it might be useful if I investigate a few
> different instances first.
You have every time you want or need, I don't think we really need to
do this before 3.1.7.
And, no, off the top of my head I can't think of places where
suffix-handling caused that much trouble.
Oh, and, btw, when thinking about suffix handling, we should probably
also re-think the -R stuff (auto-removal in general). Maybe we find
something better, maybe we don't...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-05-24 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-24 8:05 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-23 13:58 Sven Wischnowsky
2000-05-23 13:15 Sven Wischnowsky
2000-05-23 13:50 ` Oliver Kiddle
2000-05-22 8:37 Sven Wischnowsky
2000-05-23 16:07 ` Oliver Kiddle
2000-05-18 11:02 Sven Wischnowsky
2000-05-19 18:39 ` Oliver Kiddle
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=200005240805.KAA29939@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).