zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: Re: Shuld it be so? and Re: _tar
Date: Fri, 5 Mar 1999 14:40:27 +0300	[thread overview]
Message-ID: <002201be66fc$f74923f0$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <199903051102.MAA03885@beta.informatik.hu-berlin.de>

>
> > bor@itsrm2:~%> l /u/l/m<TAB>
> > bor@itsrm2:~%> l /u1/lager-db/minileit.dbs/
> > u1/   usr/
> > ^^^^^^^^^^ Somewhat strange. We really have /usr/lib/macros
> (and more), but
> > this list is a bit unexpected (well, at least I would expect
> then to first
> > menu complete ``/u1'' and ``/usr'' and then go on respectively)
>
> It now keeps the original suffix if menucompletion is used. With
> normal completion it still tries to build as long a suffix as
> possible.

Well, now it cycles through /u1 and /usr, leaving the tail unmodified. And?
I have no way to say "go ahead, and complete the next path component". And
inserted string is unusable as is.

I'd expect, that in case of menucompletion the whole list (after common
prefix) would simply be spit out. Yes, it is ugly if no common prefix
exists. But then you get what you asked for.

> [Again, I had forgotten menucompletion (I just can't imagine how one
> would like to use it... a matter of being used to, I think).]
>

Now I am inclined to not use it as well. But there may be some users who do
...

> Anyway, if you try it, you will notice, that the cursor is left at the
> end of the whole string, even though only the beginning is cycled
> through. Since I don't like menucompletion I have to ask: would you
> like to have the cursor after the changed/listed component? (I'm not
> sure if I can manage to implement that, though.)
>

Me not. See above. Until we come to a clean solution how to implement
partial, incremental completion (I had some weird idea today morning) - give
a user the whole list. We do it in most cases anyway.

>
> This is now allowed if `globcomplete' is set. Otherwise the pattern
> characters will still be quoted (which is a good thing, I think).
>

Not sure. It is now O.K. with globcomplete set. But without globcomplete I
get ``/home/bor/s\*'' - what is it good for? Better would be to leave meta
as is. Cf

grep xxx /u/i/s/*.h<TAB>

I'd expect it to complete path and leave star in place.

cheers

/andrej


  parent reply	other threads:[~1999-03-05 11:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-05 11:02 Sven Wischnowsky
1999-03-05 11:05 ` Peter Stephenson
1999-03-05 11:40 ` Andrej Borsenkow [this message]
1999-03-05 12:05 ` Andrej Borsenkow
1999-03-05 13:06 Sven Wischnowsky
1999-03-05 13:08 ` Peter Stephenson

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='002201be66fc$f74923f0$21c9ca95@mowp.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --cc=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).