From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: line continuation with sed
Date: Sun, 16 Oct 2022 18:07:04 -0700 [thread overview]
Message-ID: <CAH+w=7Zmb8hO6WifZTO827O09Oq25dNKmq+2gNmUQW-xBvGvjA@mail.gmail.com> (raw)
In-Reply-To: <4e4d53a2-226e-a0ae-a1f7-87619eaff155@eastlink.ca>
You might find something like this interesting:
show-trailing-space() {
zle .$WIDGET &&
if [[ $BUFFER = *(' '|$' \n'*)
|| $PREBUFFER = *$' \n'* ]]
then POSTDISPLAY=$'\u21a9'
else unset POSTDISPLAY
fi
}
zle -N magic-space show-trailing-space
zle -N self-insert show-trailing-space
zle -N kill-whole-line show-trailing-space
zle -N kill-line show-trailing-space
zle -N kill-word show-trailing-space
zle -N backward-kill-word show-trailing-space
zle -N backward-delete-char show-trailing-space
Integrating this with other plugins etc. that may have rebound those
widgets or appropriated POSTDISPLAY is left as an exercise. Other
improvements (bind to history motions etc.) are possible.
next prev parent reply other threads:[~2022-10-17 1:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:25 Ray Andrews
2022-10-14 6:35 ` Lawrence Velázquez
2022-10-14 11:20 ` Dominik Vogt
2022-10-14 15:44 ` Ray Andrews
2022-10-14 17:10 ` Dominik Vogt
2022-10-14 20:38 ` Lawrence Velázquez
2022-10-14 22:26 ` Ray Andrews
2022-10-14 10:57 ` Marc Chantreux
2022-10-14 11:19 ` Peter Stephenson
2022-10-14 17:15 ` Dominik Vogt
2022-10-14 22:21 ` Ray Andrews
2022-10-15 2:34 ` Aaron Schrab
2022-10-15 2:57 ` Ray Andrews
2022-10-15 5:08 ` Bart Schaefer
2022-10-15 16:53 ` Ray Andrews
2022-10-17 1:07 ` Bart Schaefer [this message]
2022-10-17 3:40 ` Ray Andrews
2022-10-17 4:20 ` Bart Schaefer
2022-10-17 9:19 ` Pier Paolo Grassi
2022-10-17 9:24 ` Pier Paolo Grassi
2022-10-17 9:31 ` Pier Paolo Grassi
2022-10-17 16:11 ` 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='CAH+w=7Zmb8hO6WifZTO827O09Oq25dNKmq+2gNmUQW-xBvGvjA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).