zsh-users
 help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Mikael Magnusson <mikachu@gmail.com>,
	Peter Stephenson <p.w.stephenson@ntlworld.com>,
	 Zsh-Users List <zsh-users@zsh.org>
Subject: Re: prepopulate BUFFER
Date: Fri, 29 Apr 2022 21:34:50 +0200	[thread overview]
Message-ID: <CAP+y1xCZfrpBM-Lj3a74fD-aFMBZtrf-GWBRavWrNQbq139_kg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7b1N6-tqFuhwa1EvxzvojaUXVwU52BLF2LDEW2rZEnPRA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

push-line (^Q ESC-Q ESC-q) (unbound) (unbound)
              Push the current buffer onto the buffer stack and clear the
buffer.  Next time  the
              editor  starts  up,  the  buffer will be popped off the top
of the buffer stack and
              loaded into the editing buffer.

the difference is in the fact that the stack will return a pushed line just
once, not for each subsequent prompt, and it will not save cursor position.

Pier Paolo Grassi


Il giorno ven 29 apr 2022 alle ore 18:21 Bart Schaefer <
schaefer@brasslantern.com> ha scritto:

> On Fri, Apr 29, 2022 at 8:57 AM Pier Paolo Grassi <pierpaolog@gmail.com>
> wrote:
> >
> > This use case is a bit different, since I return always to the original
> (incomplete) version of the command line, and I have only to complete it
> instead of deleting what I don't need anymore and fill the blanks
>
> How does that differ from push-line ?
>

[-- Attachment #2: Type: text/html, Size: 1543 bytes --]

      reply	other threads:[~2022-04-29 19:36 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
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 [this message]

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+y1xCZfrpBM-Lj3a74fD-aFMBZtrf-GWBRavWrNQbq139_kg@mail.gmail.com \
    --to=pierpaolog@gmail.com \
    --cc=mikachu@gmail.com \
    --cc=p.w.stephenson@ntlworld.com \
    --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).