zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: bracketed paste - chopping trailing newlines
Date: Sat, 12 Sep 2015 08:58:45 -0700	[thread overview]
Message-ID: <150912085845.ZM9504@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3RJg+1kSM6pq1ZirbwEjn0tZKV0pYdnTb8cPO5fC+wKtg@mail.gmail.com>

On Sep 12,  2:17am, Mikael Magnusson wrote:
}
} I personally find it very surprising that pasting would interact with
} the region in any way at all, yanking normally doesn't.

Yes, I was a little surprised that Oliver implemented it that way, as
it doesn't seem to be what Emacs does (well, except possibly Aquamacs
on MacOS, which tries to emulate MacOS cmd-c/cmd-v behavior).

However, that adds yet another thing to the list of disagreements, so
I wasn't going to go there.

} > I guess I agree with Oliver about the newline stripping.
} 
} We have at least two options that decide if and how we print a single
} newline before drawing the prompt, maybe there is room for some here
} as well.

Problems with that are (a) for newlines before the prompt, the initial
state is outside the editor, but with paste we're inside the editor
the whole time so any extra stuff we output (other than highlighting)
could be confused with $BUFFER contents; and (b) we're trying to move
away from having module-specific setopts in the main shell.

Using RPS1 with TRANSIENT_RPROMPT might cover a lot of this, as
the prompt would still be there if the line has not been accepted.
Unfortunately RPS1 stays on the first line and is transient based on
the legth of that first line.  It might be nicer if it acted more
like POSTDISPLAY.


  reply	other threads:[~2015-09-12 15:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29  1:24 Carsten Hey
2015-08-29  5:00 ` Bart Schaefer
2015-08-30 20:25   ` Carsten Hey
2015-08-30 20:32     ` [patch] 5.0.9 vs 5.1 in source code comments (was: bracketed paste - chopping trailing newlines) Axel Beckert
2015-08-30 20:37     ` bracketed paste - chopping trailing newlines Axel Beckert
2015-08-31  5:47     ` Daniel Shahaf
2015-09-01 23:44       ` Bart Schaefer
2015-09-02 15:41         ` Daniel Shahaf
2015-09-01 23:48     ` Bart Schaefer
2015-09-03 23:59       ` Carsten Hey
2015-09-06  9:52         ` Daniel Shahaf
2015-09-06 13:51           ` Oliver Kiddle
2015-09-06 14:21             ` Bart Schaefer
2015-09-08 10:39               ` Oliver Kiddle
2015-09-10 14:45                 ` Bart Schaefer
2015-09-10 19:11                 ` Daniel Shahaf
2015-09-11 23:07                   ` Bart Schaefer
2015-09-12  0:17                     ` Mikael Magnusson
2015-09-12 15:58                       ` Bart Schaefer [this message]
2015-09-14 20:35                     ` Daniel Shahaf
2015-09-14 21:21                       ` Bart Schaefer
2015-09-07  2:11             ` Daniel Shahaf
2015-09-08 23:33             ` Carsten Hey
2015-09-08 23:48               ` Carsten Hey
2015-09-10  8:24                 ` Peter Stephenson
2015-09-07 21:13           ` Daniel Shahaf

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=150912085845.ZM9504@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).