From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: How to complete backquote, etc. using compsys?
Date: Tue, 28 Aug 2001 15:50:58 +0000 [thread overview]
Message-ID: <1010828155058.ZM2724@candle.brasslantern.com> (raw)
In-Reply-To: <3B8B6600.54A33D8E@yahoo.co.uk>
[Redirected to -workers]
On Aug 28, 10:36am, Oliver Kiddle wrote:
} Subject: Re: How to complete backquote, etc. using compsys?
}
} 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 $(...)?
Hmm, at the moment perhaps it doesn't, but it could look at $LBUFFER to
find out.
} The level of nesting would also be useful.
It should be easy to add a special parameter that gives the same info
as the %_ prompt expansion. I tried ${(%):-%_} but (not surprisingly)
the parser stack isn't "live" during the execution of the completion
function.
} [...] it would be useful to have the backquote as a removable
} suffix because it is quicker to press space than backquote.
The problem is that you end up with too many layers of autoremovable
suffixes. When completing a path name within backticks, you can't
get both the trailing / on a directory name and the trailing backtick.
} Also, without multios the closing
} bracket of $(<...) should always be completed.
It would have to be an autoremovable suffix, too; `echo $(<file wc)' is
a silly example of why.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next parent reply other threads:[~2001-08-28 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010821204255.64C6417403@puel.sfc.wide.ad.jp>
[not found] ` <3B84D18C.19BA712@yahoo.co.uk>
[not found] ` <1010823180146.ZM25810@candle.brasslantern.com>
[not found] ` <3B8B6600.54A33D8E@yahoo.co.uk>
2001-08-28 15:50 ` Bart Schaefer [this message]
2001-08-29 17:31 ` Oliver Kiddle
2001-08-29 17:52 ` Bart Schaefer
2001-08-29 21:06 ` Zefram
2001-08-30 0:07 ` 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=1010828155058.ZM2724@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).