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 23:18:15 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10007122306210.9316-100000@langec.myip.org> (raw)
In-Reply-To: <1000712185437.ZM18513@candle.brasslantern.com>
On Wed, 12 Jul 2000, Bart Schaefer wrote:
> On Jul 12, 6:38pm, Christoph Lange wrote:
> } Subject: Re: ZLE Widget: Insert last word (except &)
> }
> } There is another bug in your version of smart-insert-last-word: repeated
> } calls to it don't go back in the history.
>
> Oops, I forgot about that behavior.
>
> } Rather than doing the word
> } splitting yourself, you should always call insert-last-word
>
> Nah.
>
> The fiddling with NUMERIC below serves two purposes: One, it passes the
> same value to both up-history and down-history without having to pass an
> argument to each. Two, `zle WIDGET -n NUM' is broken for NUM > 9.
>
> ---- 8< ---- cut ---- 8< ----
> # smart-insert-last-word
>
> [...]
I didn't understand all of it, but now the functions even fails doing
elementar things:
% echo a &
a
% echo
^ [Alt+.] pressed
I found out another interesting thing about my first version. zsh goes up in
the history on subsequent calls of insert-last-word, but from the widget's
point of view, the position in the history remains the same. Either
determining the previous line with `fc -n -l -1' or -- like in your widget
-- going up the history and reading from $BUFFER always returns the previous
line relative from the position where the user started calling
insert-last-word. Just look at the following result:
% echo 1
% echo 1&
% [[Subsequent invocations of insert-last-word:]]
1. `1'
2. `echo'
lastcmd always contains `echo 1&', regardless of the shell going up the
history. Thus, the last but one word is inserted into the command line.
What to do?
Christoph
--
Q: After bootup, a linux machine hangs, showing the error
message `login:'. How can I fix this?
A: This system hang is a big enough problem to justify
replacing Linux with Windows 2000.
Christoph Lange, langec@gmx.de, http://www.cul.de/home/yaph/, ICQ #51191833
next prev parent reply other threads:[~2000-07-12 21:16 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
2000-07-12 18:54 ` Bart Schaefer
2000-07-12 21:18 ` Christoph Lange [this message]
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.10007122306210.9316-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).