zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: expansion
Date: Fri, 09 Jun 2000 11:45:34 +0100	[thread overview]
Message-ID: <3940CACE.2C1C7CC9@u.genie.co.uk> (raw)
In-Reply-To: <200006090732.JAA22264@beta.informatik.hu-berlin.de>

Sven Wischnowsky wrote:
> 
> Hm, do you want it to ever expand tildes at all? 

Not particularly. I wouldn't mind if it only did straight after the
tilde reference like expand-or-complete does for parameters but it would
have to be intelligent enough to see if it could be a partial reference
to a longer named directory. Whatever the completion does, it would also
be useful to be able to bind ^X~ to expand tildes.

> We could add more fine-grained control over the kinds of substitutions tried.

I think we should add fine-grained control though I fear it isn't easy
to do. It's a pity that the nearest I can get the the behaviour I want
is not by using _expand.

> Does anyone have other ideas for conditions when to expand or not?
> Let's collect them.

The only thing I can think of at the moment is the same thing I was
saying about tilde expansions with parameter substitutions: if I had a
$MAIL and $MAILPATH parameter, $MAIL<tab> should do completion and not
expansion. To a certain extent, this is what you might get if you had
the _expand completer after _complete if it wasn't for the fact that
completion would generally not give expansion a chance.

Oliver


  reply	other threads:[~2000-06-09 10:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-09  7:32 Sven Wischnowsky
2000-06-09 10:45 ` Oliver Kiddle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-14  6:21 Sven Wischnowsky
2000-06-13 11:24 Sven Wischnowsky
2000-06-13 16:41 ` Bart Schaefer
     [not found] <0FVU001OT0DZC6@la-la.cambridgesiliconradio.com>
2000-06-08 16:50 ` Oliver Kiddle
2000-06-07  6:46 PATCH: expansion (was: Re: PATCH: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)) Sven Wischnowsky
2000-06-07 22:21 ` PATCH: expansion Wayne Davison
2000-06-08 10:03   ` 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=3940CACE.2C1C7CC9@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --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).