From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-users@sunsite.dk
Cc: Keijiro Ehara <popo@sfc.wide.ad.jp>
Subject: Re: How to complete backquote, etc. using compsys?
Date: Tue, 28 Aug 2001 10:36:00 +0100 [thread overview]
Message-ID: <3B8B6600.54A33D8E@yahoo.co.uk> (raw)
In-Reply-To: <1010823180146.ZM25810@candle.brasslantern.com>
Bart Schaefer wrote:
>
> On Aug 23, 10:49am, Oliver Kiddle wrote:
> }
> } No, you didn't miss an option. The new completion system just doesn't
> } complete the backquote. [...] At the moment, I don't think the shell
> } code can tell if it is in $( .. )
>
> Yes, it can tell that it's in $(...) or `...`.
compstate[quote] and compstate[quoting] indicate if it is in `...` but
how can it tell it's in $(...)? The level of nesting would also be
useful.
> It doesn't complete the
> trailing backtick or closing paren because there's no way to tell when
> you're really at the end of the expression. How is it supposed to know
> whether you mean
> `cat /var/run/inetd.pid`
> or whether you're going to go on with more of the command, as in
> `cat /var/run/inetd.pid /var/run/sshd.pid`
> or the like?
That's true but it would be useful to have the backquote as a removable
suffix because it is quicker to press space than backquote. A style
could always be used to prevent it. Also, without multios the closing
bracket of $(<...) should always be completed.
Oliver
_____________________________________________________________________
This message has been checked for all known viruses by the
MessageLabs Virus Scanning Service. For further information visit
http://www.messagelabs.com/stats.asp
prev parent reply other threads:[~2001-08-28 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 20:41 Keijiro Ehara
2001-08-23 9:49 ` Oliver Kiddle
2001-08-23 18:01 ` Bart Schaefer
2001-08-28 9:36 ` Oliver Kiddle [this message]
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=3B8B6600.54A33D8E@yahoo.co.uk \
--to=okiddle@yahoo.co.uk \
--cc=popo@sfc.wide.ad.jp \
--cc=zsh-users@sunsite.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).