zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Pier Paolo Grassi <pierpaolog@gmail.com>
Cc: Ray Andrews <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: line continuation with sed
Date: Mon, 17 Oct 2022 09:11:06 -0700	[thread overview]
Message-ID: <CAH+w=7Z1i4-WOmMcEP7N1W-9-Zvo4DBxO=5ys8shVSp6gKDDfQ@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xBgjWhjf5hFQHbZGm2r5e0P5xUKU4=6kJq+VzDcdDK_iw@mail.gmail.com>

On Mon, Oct 17, 2022 at 2:32 AM Pier Paolo Grassi <pierpaolog@gmail.com> wrote:
>
> E \
> cdcd↩
>
> ie the space is on the first line but the eol marker is on the last line of the buffer, is there a POSTDISPLAY equivalent at row level?

There's not.  I toyed with the idea of actually inserting the eol
marker into the buffer, and removing it again in zle-line-finish, but
PREBUFFER is read-only so a bunch of ugly special-cases would be
introduced.


      reply	other threads:[~2022-10-17 16:12 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
2022-10-17  9:31                   ` Pier Paolo Grassi
2022-10-17 16:11                     ` Bart Schaefer [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='CAH+w=7Z1i4-WOmMcEP7N1W-9-Zvo4DBxO=5ys8shVSp6gKDDfQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=pierpaolog@gmail.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).