unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Sebastian Tennant <sdt@sebyte.me>
Cc: 61552@debbugs.gnu.org
Subject: bug#61552: Feature request: Add variable Man-prefer-synchronous-call
Date: Tue, 21 Feb 2023 15:47:11 +0100	[thread overview]
Message-ID: <87a617m5xs.fsf@gmail.com> (raw)
In-Reply-To: <87lekr9km4.fsf@sebyte.me> (Sebastian Tennant's message of "Tue,  21 Feb 2023 14:08:35 +0000")

>>>>> On Tue, 21 Feb 2023 14:08:35 +0000, Sebastian Tennant <sdt@sebyte.me> said:

    >> (and add a description to the manual, if that makes sense)

    Sebastian> Sure.  I didn't think reading manpages would have an entry in the
    Sebastian> manual but, sure enough, it does:

Everything in Emacs should be in the manual :-)

    Sebastian>  (info "(emacs) Man Page")

    Sebastian> I shall edit doc/emacs/programs.texi accordingly.

    >> […]
    >>> (defcustom Man-prefer-synchronous-call nil
    >>> "Non-nil means always call the Un*x man command synchronously,
    >>> rather than asynchronously, which is the default behaviour."
    >> 
    >> The first line should be a complete sentence. Something like
    >> 
    >> "Whether to call the Un*x 'manʼ command synchronously."

    Sebastian> How about this:

    Sebastian>  "Control whether the Un*x 'man' command is called synchronously or
    Sebastian>   asynchronously.  (Asynchronous is the default)."

Sorry, I meant "a complete sentence, and only taking up one screen
line, not exceeding `emacs-lisp-docstring-fill-column'", ie

    Whether to call the Un*x 'man' command synchronously.
    When this is non-nil call 'man' synchronously instead of the default
    asynchronous behaviour.

since `apropos' displays only the first line

Robert
-- 





  reply	other threads:[~2023-02-21 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 16:12 bug#61552: Feature request: Add variable Man-prefer-synchronous-call Sebastian Tennant
2023-02-16 17:09 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 18:11   ` Sebastian Tennant
2023-02-21 10:44     ` Robert Pluim
2023-02-21 14:08       ` Sebastian Tennant
2023-02-21 14:47         ` Robert Pluim [this message]
2023-02-22 17:16           ` Sebastian Tennant
2023-03-02 11:30             ` Eli Zaretskii
2023-03-03  8:51               ` Sebastian Tennant
2023-03-03 11:23                 ` Eli Zaretskii
2023-02-21  9:53 ` Stefan Kangas
2023-02-21 12:16   ` Sebastian Tennant
2023-02-21 12:28   ` Sebastian Tennant

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=87a617m5xs.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=61552@debbugs.gnu.org \
    --cc=sdt@sebyte.me \
    /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).