From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: oub@mat.ucm.es, npostavs@gmail.com, emacs-devel@gnu.org
Subject: Re: git+master: c6e6503900534d939dd94b812563c27f22c49b7d crash when using gnus
Date: Sun, 29 Apr 2018 20:40:54 +0300 [thread overview]
Message-ID: <83r2mxsyft.fsf@gnu.org> (raw)
In-Reply-To: <cc5b600d-785a-60e5-9209-9f7b9ac391a1@cs.ucla.edu> (message from Paul Eggert on Sun, 29 Apr 2018 10:18:59 -0700)
> Cc: npostavs@gmail.com, oub@mat.ucm.es, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 29 Apr 2018 10:18:59 -0700
>
> Eli Zaretskii wrote:
> > Please use one long line, to avoid problems when people naïvely
> > copy/paste the command into the shell prompt.
>
> Users can copy-paste the first example as-is already, since the earlier line
> ends in backslash.
Long lines without any backslashes are safer, so I'd prefer that. But
I won't have another bikeshedding argument over that, so if you don't
feel like changing it, so be it.
> If we're talking about truly naive users, then these commands are too long
> anyway.
I don't see any real problem with that, all supported platforms can
handle much longer commands.
> I'll hold off backporting until we get the important matter of backslashes
> resolved. :-)
It's resolved already, if it's up to me.
next prev parent reply other threads:[~2018-04-29 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 9:06 git+master: c6e6503900534d939dd94b812563c27f22c49b7d crash when using gnus Uwe Brauer
2018-04-28 9:43 ` Eli Zaretskii
2018-04-28 10:11 ` Uwe Brauer
2018-04-28 10:46 ` Eli Zaretskii
2018-04-28 11:56 ` Uwe Brauer
2018-04-28 12:09 ` Eli Zaretskii
2018-04-29 8:46 ` Uwe Brauer
2018-04-29 9:53 ` Eli Zaretskii
2018-04-29 14:54 ` Uwe Brauer
2018-04-29 15:09 ` Eli Zaretskii
2018-04-29 15:26 ` Noam Postavsky
2018-04-29 16:30 ` Paul Eggert
2018-04-29 17:08 ` Eli Zaretskii
2018-04-29 17:18 ` Paul Eggert
2018-04-29 17:40 ` Eli Zaretskii [this message]
2018-04-29 16:31 ` Eli Zaretskii
2018-04-29 15:01 ` Uwe Brauer
2018-04-29 15:33 ` Noam Postavsky
2018-04-29 16:33 ` Eli Zaretskii
2018-04-29 16:39 ` Uwe Brauer
2018-04-29 16:39 ` Uwe Brauer
2018-04-29 17:09 ` Eli Zaretskii
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=83r2mxsyft.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
--cc=oub@mat.ucm.es \
/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).