From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: A tweak to magic-space
Date: Mon, 28 May 2001 05:23:58 +0000 [thread overview]
Message-ID: <1010528052358.ZM1986@candle.brasslantern.com> (raw)
I believe I mentioned this in a previous posting ...
I've been using this function:
magic-space() {
[[ "$LBUFFER" = (|*[^\\])!\"* ]] && zle .self-insert || zle .magic-space
}
zle -N magic-space
This means that if the current input line contains !" to the left of the
insertion point, history is not expanded upon typing a space.
This is all very well and good, but it makes using `set -x' an incredible
pain, because the trace of the above function keeps popping out in place of
every space I type. (Maybe we need an inverse of `typeset -ft' ... though,
oddly, execution tracing set only with `typeset -ft' does NOT happen when
widgets are called directly by ZLE, which is probably a bug.)
The following patch puts the equivalent of the above into the C code. I
won't commit it until after 4.0.1 is released, unless enough somebodies
say I should. However, if any of you try it, I could use some feedback
on whether it's better to test for !" only in LBUFFER, or whether to test
all of $BUFFER (that is, drop the `bangq + 2 > line + cs' test in the C
version). I go back and forth ...
--- zsh-forge/current/Src/Zle/zle_tricky.c Thu May 17 08:48:46 2001
+++ zsh-4.0/Src/Zle/zle_tricky.c Thu May 24 01:15:32 2001
@@ -2239,9 +2239,13 @@
int
magicspace(char **args)
{
+ char *bangq;
int ret;
c = ' ';
- if (!(ret = selfinsert(args)))
+ for (bangq = (char *)line; (bangq = strchr(bangq, bangchar)); bangq += 2)
+ if (bangq[1] == '"' && (bangq == (char *)line || bangq[-1] != '\\'))
+ break;
+ if (!(ret = selfinsert(args)) && (!bangq || bangq + 2 > (char *)line + cs))
doexpandhist();
return ret;
}
--
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
reply other threads:[~2001-05-28 5:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1010528052358.ZM1986@candle.brasslantern.com \
--to=schaefer@candle.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).