all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: lu4nx <lx@shellcodes.org>
Cc: 59961@debbugs.gnu.org
Subject: bug#59961: [PATCH] ; * lib-src/emacsclient.c: Add parameters option information.
Date: Sun, 11 Dec 2022 12:26:16 +0200	[thread overview]
Message-ID: <83a63uuth3.fsf@gnu.org> (raw)
In-Reply-To: <tencent_138785D7074B73DACCCCD54CD528DE89C80A@qq.com> (message from lu4nx on Sun, 11 Dec 2022 17:32:32 +0800)

> Cc: lu4nx <lx@shellcodes.org>
> From: lu4nx <lx@shellcodes.org>
> Date: Sun, 11 Dec 2022 17:32:32 +0800
> 
> ---
>  lib-src/emacsclient.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lib-src/emacsclient.c b/lib-src/emacsclient.c
> index af488128ba..a0c5b84bc5 100644
> --- a/lib-src/emacsclient.c
> +++ b/lib-src/emacsclient.c
> @@ -1669,10 +1669,10 @@ set_socket (bool no_exit_if_error)
>    /* No implicit or explicit socket, and no alternate editor.  */
>    message (true, "%s: No socket or alternate editor.  Please use:\n\n"
>  #ifdef SOCKETS_IN_FILE_SYSTEM
> -"\t--socket-name\n"
> +"\t--socket-name=SOCKET\n"
>  #endif
> -"\t--server-file      (or environment variable EMACS_SERVER_FILE)\n\
> -\t--alternate-editor (or environment variable ALTERNATE_EDITOR)\n",
> +"\t--server-file=SERVER      (or environment variable EMACS_SERVER_FILE)\n\
> +\t--alternate-editor=EDITOR (or environment variable ALTERNATE_EDITOR)\n",
>             progname);
>    exit (EXIT_FAILURE);
>  }

The --help message already says that.  Why do we need that in an error
message as well?





  reply	other threads:[~2022-12-11 10:26 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83a63uuth3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59961@debbugs.gnu.org \
    --cc=lx@shellcodes.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.