From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] bracketed-paste: change quoting style
Date: Mon, 17 Aug 2015 21:59:52 +0000 [thread overview]
Message-ID: <20150817215952.GA2283@tarsus.local2> (raw)
In-Reply-To: <150813165709.ZM28957@torch.brasslantern.com>
Bart Schaefer wrote on Thu, Aug 13, 2015 at 16:57:09 -0700:
> On Aug 13, 11:19pm, Daniel Shahaf wrote:
> }
> } I agree that separating the "paste it" and "quote it" to separate steps
> } would be good, but it doesn't seem to work in current git: invoking
> } quote-region quotes the entire command line, not only the pasted part.
> } Does it depend on an uncommitted patch or something?
>
> No, but you have to set the mark before pasting; the action of pasting
> does not make the region active (though it replaces the active region
> if there is one).
I see; so the workflow is <set-mark-command><paste><quote-region>. This is
nice. However, I will keep using <NUMERIC><paste>, because it's fewer
keypresses.
As to changing the default quoting style, I went ahead and pushed it. (Using
single quotes is consistent with quote-region and quote-line.) I saw the
discussion about which values of NUMERIC should cause quoting (36193) but
I think it is orthogonal.
As Oliver said — we can make further changes later if needed.
Cheers,
Daniel
P.S. Someone pointed out on IRC that 'typeset -p IFS' prints a literal
newline character. Perhaps it should use $''-quoting to escape the
newline.
prev parent reply other threads:[~2015-08-17 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 22:09 Daniel Shahaf
2015-08-12 1:08 ` Mikael Magnusson
2015-08-12 2:52 ` Bart Schaefer
2015-08-12 3:13 ` Mikael Magnusson
2015-08-12 6:44 ` Bart Schaefer
2015-08-13 14:49 ` Oliver Kiddle
2015-08-13 16:20 ` Bart Schaefer
2015-08-13 23:19 ` Daniel Shahaf
2015-08-13 23:57 ` Bart Schaefer
2015-08-17 21:59 ` Daniel Shahaf [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=20150817215952.GA2283@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--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).