unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46979@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#46979: Allow setting Man-default-entry via Local Variables
Date: Mon, 08 Mar 2021 16:48:52 +0100	[thread overview]
Message-ID: <m1im61odcr.fsf@yahoo.es> (raw)
In-Reply-To: <83czw9somb.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 08 Mar 2021 16:31:56 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>
> Our solution to this is "C-h S".  Did you try it?  You can extend its
> database if the default lacks something you need.

C-h S only searches Info pages.  I think this feature request is more
about improving the default that M-x man offers, to consider more things
than just the text around point.

I can see its usefulness, as a lot of Unix tools provide special man
pages for its configuration files.  Another potential use case is a user
visiting a .gitconfig file, where M-x man could suggest "git-config(1)"
by default.  Similarly for .gitattributes and "gitattributes(5)".

As it's almost impossible to have all that knowledge in Emacs core, I
see it as a new extensibilty point for users.  What are the downsides
you see in the local variable approach?





  parent reply	other threads:[~2021-03-08 15:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 23:18 bug#46979: Allow setting Man-default-entry via Local Variables 積丹尼 Dan Jacobson
2021-03-07  6:11 ` Eli Zaretskii
2021-03-07 14:09   ` 積丹尼 Dan Jacobson
2021-03-08 11:17     ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-08 13:46       ` 積丹尼 Dan Jacobson
2021-03-08 14:31         ` Eli Zaretskii
2021-03-08 14:48           ` 積丹尼 Dan Jacobson
2021-03-08 15:10             ` Eli Zaretskii
2021-03-08 15:51               ` 積丹尼 Dan Jacobson
2021-03-08 16:33                 ` Eli Zaretskii
2021-03-08 17:06                   ` 積丹尼 Dan Jacobson
2021-03-08 18:15                     ` Eli Zaretskii
2021-03-09 14:24                       ` 積丹尼 Dan Jacobson
2021-03-09 16:57                         ` Eli Zaretskii
2021-03-09 17:16                           ` 積丹尼 Dan Jacobson
2021-03-08 15:48           ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-08 16:32             ` Eli Zaretskii
2021-03-08 19:01               ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-08 20:42                 ` Eli Zaretskii
2021-03-08 21:55               ` Basil L. Contovounesios

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=m1im61odcr.fsf@yahoo.es \
    --to=bug-gnu-emacs@gnu.org \
    --cc=46979@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=mardani29@yahoo.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).