From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Ray Andrews <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: line continuation with sed
Date: Mon, 17 Oct 2022 11:24:50 +0200 [thread overview]
Message-ID: <CAP+y1xD72e6a-nk2gxqZ_8qkvEhXMn-FgK_tn5TqVqissnXYUw@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xBM1xab-av-dzSnohju7Fh8M5dPZQLTTcgo8-TmNWKWPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
I answered myself with
autoload -U add-zle-hook-widget
Pier Paolo Grassi
Il giorno lun 17 ott 2022 alle ore 11:19 Pier Paolo Grassi <
pierpaolog@gmail.com> ha scritto:
> add-zle-hook-widget
> zsh: command not found: add-zle-hook-widget
>
> locate add-zle-hook-widget
> /usr/local/share/zsh/5.8/functions/_add-zle-hook-widget
> /usr/local/share/zsh/5.8/functions/_add-zle-hook-widget.zwc
> /usr/local/share/zsh/5.8/functions/add-zle-hook-widget
> /usr/local/share/zsh/5.8/functions/add-zle-hook-widget.zwc
>
> echo $fpath
> /root/scripts//zsh/functions/zle/ /usr/local/share/zsh/5.8/functions/
>
> why the command is not found? Should I do something to load the functions
> from fpath?
> thanks
>
> Pier Paolo Grassi
>
>
> Il giorno lun 17 ott 2022 alle ore 06:22 Bart Schaefer <
> schaefer@brasslantern.com> ha scritto:
>
>> On Sun, Oct 16, 2022 at 8:40 PM Ray Andrews <rayandrews@eastlink.ca>
>> wrote:
>> >
>> > On 2022-10-16 18:07, Bart Schaefer wrote:
>> > > You might find something like this interesting:
>> > That is really elegant.
>>
>> Actually that implementation is kind of ugly. I completely forgot
>> about this much prettier way:
>>
>> show-trailing-space() {
>> if [[ $BUFFER = *(' '|$' \n'*)
>> || $PREBUFFER = *$' \n'* ]]
>> then POSTDISPLAY=$'\u21a9'
>> else unset POSTDISPLAY
>> fi
>> }
>> zle -N show-trailing-space
>> add-zle-hook-widget line-pre-redraw show-trailing-space
>> add-zle-hook-widget history-line-set show-trailing-space
>>
>>
[-- Attachment #2: Type: text/html, Size: 2745 bytes --]
next prev parent reply other threads:[~2022-10-17 9:26 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
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 [this message]
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=CAP+y1xD72e6a-nk2gxqZ_8qkvEhXMn-FgK_tn5TqVqissnXYUw@mail.gmail.com \
--to=pierpaolog@gmail.com \
--cc=rayandrews@eastlink.ca \
--cc=schaefer@brasslantern.com \
--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).