From: Glenn Morris <rgm@gnu.org>
To: Samuel Bronson <naesten@gmail.com>
Cc: 17310@debbugs.gnu.org
Subject: bug#17310: 24.3; clarify emacsclient(1) manpage link to "(emacs)Emacs Server"
Date: Tue, 29 Apr 2014 10:15:53 -0400 [thread overview]
Message-ID: <0dvbtskyqu.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8761m2a7ew.fsf@naesten.mooo.com> (Samuel Bronson's message of "Mon, 21 Apr 2014 14:01:27 -0400")
Samuel Bronson wrote:
> It would be helpful if the manpage for emacsclient had a more prominent
> (i.e. bold) and more explicit link to (info "(emacs)Emacs Server"),
> perhaps using something like the included patch.
Thanks for the patch, but IMO it's not worth applying.
It's not the job of every man page to explain how to use info.
> *** /home/naesten/hacking/emacsclient.orig.1 2014-04-21 13:04:31.000000000 -0400
> --- /home/naesten/hacking/emacsclient.1 2014-04-21 13:37:07.000000000 -0400
> ***************
> *** 93,99 ****
> .SH "SEE ALSO"
> The program is documented fully in
> .IR "Using Emacs as a Server"
> ! available via the Info system.
> .SH AUTHOR
> This manual page was written by Stephane Bortzmeyer <bortzmeyer@debian.org>,
> for the Debian GNU/Linux system (but may be used by others).
> --- 93,108 ----
> .SH "SEE ALSO"
> The program is documented fully in
> .IR "Using Emacs as a Server"
> ! available via the Info system. You should be able to reach it using the
> ! shell command
> ! .IP
> ! .B info emacs \(aqEmacs Server\(aq
> ! .PP
> ! or by evaluating
> ! .IP
> ! .B (info \(dq(emacs)Emacs Server\(dq)
> ! .PP
> ! in Emacs.
> .SH AUTHOR
next prev parent reply other threads:[~2014-04-29 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 18:01 bug#17310: 24.3; clarify emacsclient(1) manpage link to "(emacs)Emacs Server" Samuel Bronson
2014-04-29 14:15 ` Glenn Morris [this message]
2014-04-29 15:29 ` Josh
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=0dvbtskyqu.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=17310@debbugs.gnu.org \
--cc=naesten@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 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.