From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: prepopulate BUFFER
Date: Fri, 29 Apr 2022 16:18:21 +0200 [thread overview]
Message-ID: <CAP+y1xBns9MVzdpFajTfc2QzeDUWAiniNgpFxi2_OG=mF-WJ_w@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xA95=Ohy_kqznbo5T5QRiQGbLrJiV8A-e-K6_V93wUJfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
actually I have another question, is there a similar way of setting the
initial cursor position like I would do setting the CURSOR var in zle
widgets?
Pier Paolo Grassi
Il giorno ven 29 apr 2022 alle ore 16:16 Pier Paolo Grassi <
pierpaolog@gmail.com> ha scritto:
> perfect, thanks!
>
> Pier Paolo Grassi
>
>
> Il giorno ven 29 apr 2022 alle ore 15:29 Peter Stephenson <
> p.w.stephenson@ntlworld.com> ha scritto:
>
>> > On 29 April 2022 at 14:21 Pier Paolo Grassi <pierpaolog@gmail.com>
>> wrote:
>> > hello, I was wondering if it is possible to prepopulate $BUFFER before
>> > rendering the prompt.
>> > I tried doing so in preexec, but it didn't work. Is there some other
>> > function I can override to do this?
>>
>> You need "print -z" --- it has all the usual options of print but the
>> result
>> ends up in the line buffer when the line editor starts.
>>
>> pws
>>
>>
[-- Attachment #2: Type: text/html, Size: 1904 bytes --]
next prev parent reply other threads:[~2022-04-29 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 13:21 Pier Paolo Grassi
2022-04-29 13:28 ` Peter Stephenson
2022-04-29 14:16 ` Pier Paolo Grassi
2022-04-29 14:18 ` Pier Paolo Grassi [this message]
2022-04-29 14:25 ` Peter Stephenson
2022-04-29 14:53 ` Pier Paolo Grassi
2022-04-29 15:25 ` Mikael Magnusson
2022-04-29 15:56 ` Pier Paolo Grassi
2022-04-29 16:20 ` Bart Schaefer
2022-04-29 19:34 ` Pier Paolo Grassi
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+y1xBns9MVzdpFajTfc2QzeDUWAiniNgpFxi2_OG=mF-WJ_w@mail.gmail.com' \
--to=pierpaolog@gmail.com \
--cc=p.w.stephenson@ntlworld.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).