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: Fri, 11 Sep 2015 16:07:02 -0700	[thread overview]
Message-ID: <150911160702.ZM8647@torch.brasslantern.com> (raw)
In-Reply-To: <20150910191143.GG10129@tarsus.local2>

On Sep 10,  7:11pm, Daniel Shahaf wrote:
}
} Yes, I also feel I'm repeating myself.  I've already made my case a few
} times.  I've also suggested fixes and implemented them.  I have been
} trying to reach consensus, but so far haven't succeeded.  As you can
} imagine, by now I'm rather frustrated.

This may be a situation where it's not possible to get consensus.  We
have I think three different approaches (Oliver's, Carsten's, yours)
none of the three agrees with either of the others, and we haven't
tried conducting any sort of poll.

} 1. Don't strip newlines at paste
} 2. Highlight pastes
} 3. Strip newlines at accept-line that immediately follows a paste
} 
} I think all objections to (2) have been addressed, apart from the
} question of whether to use standout or underline.  I think standout is
} easier to spot and doesn't clash with zle_highlight[region]'s default

I'm of two minds here.  One, there is a relationship between paste and
the region -- if the region is active, the paste replaces it.  However,
if there is no active region, the paste does not make it active (even
though it sets MARK/CURSOR to the opposite ends and e.g. kill-region
will kill the pasted text).  So two, making the paste look the same as
an active region may be misleading ... or, maybe it's OK because it's
almost the same thing.

I guess I agree with Oliver about the newline stripping.


  reply	other threads:[~2015-09-11 23:07 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 [this message]
2015-09-12  0:17                     ` Mikael Magnusson
2015-09-12 15:58                       ` Bart Schaefer
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=150911160702.ZM8647@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).