From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: Questions/comments on completion code that arise from PWS's zsh guide
Date: Thu, 24 Feb 2000 17:45:32 +0000 [thread overview]
Message-ID: <1000224174533.ZM22021@candle.brasslantern.com> (raw)
In-Reply-To: <200002240851.JAA15340@beta.informatik.hu-berlin.de>
On Feb 24, 9:51am, Sven Wischnowsky wrote:
} Subject: Re: Questions/comments on completion code that arise from PWS's z
}
} Bart Schaefer wrote:
}
} > Completing files after `=' is enabled for `dd' even if `magicequalsubst'
} > is not set -- but of course tilde-expansion doesn't happen when the
} > command is finally executed unless `magicequalsubst' IS set.
}
} Hm, right. One solution would be to add a new option to _path_files
} [...] But a better solution might to just make _path_files check [...]
} Hrm, just make _path_files add a warning to the list?
This isn't really a _path_files problem, is it? It's the caller that
has put the `=' into IPREFIX. I suppose it could produce a warning as
a courtesy, but it's really not _path_files job to figure out what that
equal sign means. For all it knows, the command to which the x=y arg
is being passed is one that is able to expand the tilde internally.
Why don't we have _dd expand the tilde when magicequalsubst is not set,
and leave _path_files alone?
} > No one has ever explained adequately why accept-and-infer-next-history
} > is overloaded in menu-selection, rather than accept-and-menu-complete.
}
} I once had this idea of adding dummy widgets in the complist module,
} like menu-select-{up,down,...,accept} and so on. The problem is that I
} would also like to automatically allow users to continue using their
} bindkeys if, for example, they happen to have reverse-menu-complete on
} some key.
Hmmm ... so the issue really is that the entire notions of both "accept"
and "history" have been overloaded when menu-selection is active. OK, I
drop the complaint for now ....
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-02-24 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-24 8:51 Sven Wischnowsky
2000-02-24 17:45 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-28 9:36 Sven Wischnowsky
2000-02-28 9:47 ` Andrej Borsenkow
2000-02-28 10:16 ` Tanaka Akira
2000-02-25 13:16 Sven Wischnowsky
2000-02-25 16:55 ` Bart Schaefer
2000-02-23 16:17 Bart Schaefer
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=1000224174533.ZM22021@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).