From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Cc: Carsten Hey <carsten@debian.org>
Subject: Re: bracketed paste - chopping trailing newlines
Date: Fri, 28 Aug 2015 22:00:57 -0700 [thread overview]
Message-ID: <150828220057.ZM14497@torch.brasslantern.com> (raw)
In-Reply-To: <20150829012452.GE30848@bosko.stateful.de>
Reordering things a bit for response ...
On Aug 29, 3:24am, Carsten Hey wrote:
}
} The other natural choice to enable distinguishing a running command from
} a paste is using zle_highlight. This could also avoid the need for the
} possibly unexpected newline stripping feature.
}
} An alternative to paste:standout is paste:underline. Given that this
} one does not suffer from similar possible problems as paste:standout,
Hm, standout, boldface, and underline are all used already for different
defaults. Underline is for isearch, though, so I suppose it's quite
unlikely to clash with paste highlighting.
} [...] I think, that a trailing newline should only
} be stripped if it does not immediately follow an other newline
Another way to approach this would be for a trailing newline to actually
be taken as accept-line, provided that RBUFFER is empty. This would be
the least different from previous (unbracketed) paste behavior, and
could be independent of the number of trailing newlines. In contexts
other than PS1, e.g., a here-document, this is identical to keeping
the trailing newline (except that the PS2 prompt is repeated).
Here's a way to try that on for size:
autoload -Uz bracketed-paste-magic
zle -N bracketed-paste bracketed-paste-magic
nl-accept () {
if [[ "$PASTED" = *$'\n' && -z "$RBUFFER" ]]
then
PASTED="${PASTED%?}"
zle -U $'\n'
fi
return 0
}
zstyle :bracketed-paste-magic active-widgets ''
zstyle :bracketed-paste-magic paste-finish nl-accept
next prev parent reply other threads:[~2015-08-29 5:01 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 [this message]
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
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=150828220057.ZM14497@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=carsten@debian.org \
--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).