From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: parameter completion in expansions
Date: Fri, 9 Jul 1999 17:21:32 +0400 [thread overview]
Message-ID: <000701beca0d$f5e8e8a0$21c9ca95@mow.siemens.ru> (raw)
When completing parameter name in parameter expansions zsh automatically adds
blank or '} ' to $par / ${par . This looks like suitable default for scalars -
but I found, that with arrays I mostly want subscription (at least in
interactive shell).
What about adding autoremoved '[' if parameter is array? (The suffix should of
course be removed if I press '}'). At the least, do nothing and leave cursor
immediately after completed name?
As this really depends on personal usage, may be, even some config key is
appropriate.
/andrej
next reply other threads:[~1999-07-09 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-09 13:21 Andrej Borsenkow [this message]
1999-07-09 13:28 Sven Wischnowsky
1999-07-09 13:33 ` Andrej Borsenkow
1999-07-09 13: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='000701beca0d$f5e8e8a0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--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).