zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Questions/comments on completion code that arise from PWS's zsh guide
Date: Wed, 23 Feb 2000 16:17:08 +0000	[thread overview]
Message-ID: <1000223161708.ZM11921@candle.brasslantern.com> (raw)

These are mostly things I've been wondering about for a while, but
reading their descriptions all in one place has set me off.

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.

No one has ever explained adequately why accept-and-infer-next-history
is overloaded in menu-selection, rather than accept-and-menu-complete.
If it's to preserve accept-and-menu-complete's semantics of starting
a new completion at the current level, then what about preserving the
semantics of accept-and-infer-next-history? Why preempt an existing
widget at all? Just to keep somebody from binding the new one in the
wrong keymap? (The "history" in there bugs me, it has nothing to do
with history.) At least choose one that no one would reasonably want to
invoke in the middle of menu-selection, perhaps even "menu-complete"
itself!

Why doesn't _multi_parts accept and pass through the -f option of
compadd?

Why does the users-hosts style want `user:host'? Is there a problem with
the @ sign that I fail to see?

I'm sure I'll have more of these ... I haven't started section 6.7 yet.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


             reply	other threads:[~2000-02-23 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-23 16:17 Bart Schaefer [this message]
2000-02-24  8:51 Sven Wischnowsky
2000-02-24 17:45 ` Bart Schaefer
2000-02-25 13:16 Sven Wischnowsky
2000-02-25 16:55 ` Bart Schaefer
2000-02-28  9:36 Sven Wischnowsky
2000-02-28  9:47 ` Andrej Borsenkow
2000-02-28 10:16 ` Tanaka Akira

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=1000223161708.ZM11921@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).