From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <johnw@gnu.org>
Cc: p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26
Date: Fri, 16 Mar 2018 05:41:20 +0200 [thread overview]
Message-ID: <83tvtgptzz.fsf@gnu.org> (raw)
In-Reply-To: <m2woychp2l.fsf@newartisans.com> (message from John Wiegley on Thu, 15 Mar 2018 16:54:58 -0700)
> From: John Wiegley <johnw@gnu.org>
> Cc: p.stephani2@gmail.com, emacs-devel@gnu.org
> Date: Thu, 15 Mar 2018 16:54:58 -0700
>
> >>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I don't think many people use quoted file names. I'm sure Philipp can patch
> > his Emacs, if he needs this badly. There's a reason why we didn't push this
> > to the release branch.
>
> Actually, I constantly use quoted file names, because I have filenames with
> spaces in them all over (for example, "~/Library/Application Support" is a
> somewhat common prefix, or "~/Library/Mobile Documents").
Why do spaces require to quote file names?
You _are_ talking about quoting with prefix "/:", right? Because this
is what this is about.
next prev parent reply other threads:[~2018-03-16 3:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 18:34 Cherrypicking commit e08de2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26 Philipp Stephani
2018-03-15 19:07 ` Eli Zaretskii
2018-03-15 19:37 ` Philipp Stephani
2018-12-25 16:02 ` Philipp Stephani
2018-12-25 17:24 ` Eli Zaretskii
2019-01-02 13:03 ` Philipp Stephani
2018-03-15 19:48 ` Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 " John Wiegley
2018-03-15 20:02 ` Eli Zaretskii
2018-03-15 23:54 ` John Wiegley
2018-03-16 3:41 ` Eli Zaretskii [this message]
2018-03-16 5:07 ` John Wiegley
2018-03-16 8:12 ` Michael Albinus
2018-03-16 14:04 ` Eli Zaretskii
2018-03-16 14:20 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tvtgptzz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=p.stephani2@gmail.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).