From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: lx@shellcodes.org, 59961@debbugs.gnu.org
Subject: bug#59961: [PATCH] ; * lib-src/emacsclient.c: Add parameters option information.
Date: Thu, 11 Jan 2024 12:28:36 +0200 [thread overview]
Message-ID: <83zfxckvu3.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnJ=AKdhP_tj7Ya_J-r-Vbq+48JRjnnKv2VDHy=q8NbSg@mail.gmail.com> (message from Stefan Kangas on Wed, 10 Jan 2024 14:35:00 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 10 Jan 2024 14:35:00 -0800
> Cc: lux <lx@shellcodes.org>, 59961@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: lux <lx@shellcodes.org>
> >> Cc: 59961@debbugs.gnu.org
> >> Date: Sun, 15 Jan 2023 18:16:43 +0800
> >>
> >> lux <lx@shellcodes.org> writes:
> >>
> >> > On Sun, 11 Dec 2022 12:26:16 +0200
> >> > Eli Zaretskii <eliz@gnu.org> wrote:
> >> >
> >> >> The --help message already says that. Why do we need that in an error
> >> >> message as well?
> >> >
> >> > Because when I forgot `server-start`, the information given was not
> >> > intuitive enough, and I needed to use `--help` again. And these three
> >> > parameters themselves need to provide value, so adding them will be
> >> > more intuitive. Thanks.
> >>
> >> Hi, this question seems to be forgotten?
> >
> > No, not forgotten. I just don't think we should make this change, as
> > the text says which features/options to use, not how to use them.
>
> What's the drawback to being a bit more helpful though?
The message becomes longer. And it only added the info to the
command-line options, but not to the corresponding environment
variables. Finally, the meaning of SOCKET and SERVER are never
explained.
So it simply sounded to me like a personal issue that is not
necessarily relevant to everyone else.
next prev parent reply other threads:[~2024-01-11 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 9:32 bug#59961: [PATCH] ; * lib-src/emacsclient.c: Add parameters option information lu4nx
2022-12-11 10:26 ` Eli Zaretskii
2022-12-11 10:51 ` lux
2023-01-15 10:16 ` lux
2023-01-15 10:40 ` Eli Zaretskii
2024-01-10 22:35 ` Stefan Kangas
2024-01-11 10:28 ` Eli Zaretskii [this message]
2024-01-11 20:21 ` Stefan Kangas
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=83zfxckvu3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59961@debbugs.gnu.org \
--cc=lx@shellcodes.org \
--cc=stefankangas@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).