zsh-workers
 help / color / mirror / code / Atom feed
From: Alexandre Duret-Lutz <duret_g@epita.fr>
To: zsh-workers@sunsite.auc.dk
Cc: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Subject: Re: PATCH: Re: Questions/comments on completion code that arise from PWS's zsh guide
Date: 25 Feb 2000 16:23:55 +0100	[thread overview]
Message-ID: <mvb4sax1f1w.fsf@phobos.lrde.epita.fr> (raw)
In-Reply-To: Sven Wischnowsky's message of "Fri, 25 Feb 2000 09:32:33 +0100 (MET)"

>>> "Sven" == Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:

[please forgive this if I totaly miss the point, but I
have just read all zsh mails for the last two weeks and
may have missed some important things]

 Sven> Bart Schaefer wrote:

[...]

 >> Why don't we have _dd expand the tilde when magicequalsubst is not set,
 >> and leave _path_files alone?

 Sven> But this is, of course, better.

 Sven> The patch adds _tilde_files which completes files and expands tildes
 Sven> if there are any. And makes _dd use it. 

But this will *always* expand tildes.  Since I am using magicequalsubst, 
I don't want tildes to be expanded 'on the line' in places where
it would be done by magicequalsubst.

Shouldn't there be a option to _tilde_files saying that _tilde_files is
called in a context where magicequalsubst will expand the tilde (in which
case _tilde_files should care whether the magicequalsubst is set or not) ?
Or it may be the default.

 Sven> Does anyone know of other places where this might be useful?

What happens with _arguments's equal-ended options ?
Should they use _tilde_files instead of _files ?
It may be good that `--prefix=~/usr' get expanded to
`--prefix=/myhomedir/usr' when magicequalsubst is unset, 
but I would find strange that `--prefix ~/usr' expands 
to `--prefix /myhomedir/usr' too...

-- 
Alexandre Duret-Lutz


  reply	other threads:[~2000-02-25 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-25  8:32 Sven Wischnowsky
2000-02-25 15:23 ` Alexandre Duret-Lutz [this message]
2000-02-25 15:39 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=mvb4sax1f1w.fsf@phobos.lrde.epita.fr \
    --to=duret_g@epita.fr \
    --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).