From: Christoph Lange <langec@gmx.de>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-users@sunsite.auc.dk
Subject: Re: ZLE Widget: Insert last word (except &)
Date: Wed, 12 Jul 2000 18:38:58 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10007121828230.6434-100000@langec.myip.org> (raw)
In-Reply-To: <1000712082636.ZM9329@candle.brasslantern.com>
> I wrote:
> } If we don't accept the shell syntax definition of a "word", how can we
> } choose a single definition of what constitutes a "word" that everyone
> } will agree on?
>
> The answer is, we don't, we use a style. Which isn't (presently) ever done
> with the builtin widgets, so you aren't going to see this as the default
> behavior of insert-last-word any time soon.
>
> ---- 8< ---- cut ---- 8< ----
> # smart-insert-last-word
>
> [...]
>
> Note that this presently doesn't work right when the previous command line
> contains a [[ ... ]] expression that uses one of the (#x) forms of extended
> pattern matching, e.g. (#i) to ignore case. That's a bug in ${(z)...} (it
> takes the # to be a comment introducer), so it should be fixed soon. If
> this really bothers you in the meantime, try adding
>
> local +h histchars=''
>
> somewhere before the assignment to lastcmd -- but then it's broken for the
> case of `setopt interactive_comments`, so choose your poison ...
There is another bug in your version of smart-insert-last-word: repeated
calls to it don't go back in the history. Rather than doing the word
splitting yourself, you should always call insert-last-word -- with an
argument of 2 or greater, when necessary.
The solution might be a synthesis of my first version and yours -- a widget
that is smarter than mine when determining the last word, but nevertheless
calls insert-last-word, so that the shell can go back the history on
subsequent calls.
Christoph
--
Descartes enters a pub. "Evening, Descartes. Same as usual?"
Descartes says: "No, I think not." -- and disappears.
Christoph Lange, langec@gmx.de, http://www.cul.de/home/yaph/, ICQ #51191833
next prev parent reply other threads:[~2000-07-12 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000711140506.5143gmx1@mx14.gmx.net>
2000-07-11 17:29 ` Christoph Lange
2000-07-11 22:05 ` Vincent Lefevre
2000-07-11 23:04 ` Bart Schaefer
2000-07-12 8:26 ` Bart Schaefer
2000-07-12 16:38 ` Christoph Lange [this message]
2000-07-12 18:54 ` Bart Schaefer
2000-07-12 21:18 ` Christoph Lange
2000-07-12 22:33 ` 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=Pine.LNX.4.10.10007121828230.6434-100000@langec.myip.org \
--to=langec@gmx.de \
--cc=duke@cyberspaces.de \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-users@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).