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: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 46979@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#46979: Allow setting Man-default-entry via Local Variables
Date: Mon, 08 Mar 2021 12:17:39 +0100	[thread overview]
Message-ID: <m1r1kpvqr0.fsf@yahoo.es> (raw)
In-Reply-To: <87pn0b12f0.5.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Sun, 07 Mar 2021 22:09:07 +0800")

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
>
> EZ> IMO, it would make much more sense to derive that from the current
> EZ> major-mode (in Man-default-man-entry).  Patches welcome.
>
> OK, sounds good. But sometimes e.g., crontab mode is not in emacs
> officially yet, so supplementing that should still be an option.

The major mode approach would work great for Bash configuration files,
for example, but, as you mention, it may not work so well for Cron files
or other .rc/.conf files that share Fundamental or Conf mode, in the
abscence of a more specific mode.  The local variable would require
users to add them to existing files, only for Emacs.

Do you have a more complete list of potential use cases, ie. common
program configuration files with corresponding man pages? I don't know
if there are plenty of them, and with that information we could think of
the best and simplest way to implement the feature, if it's worth it.
Thanks.





  reply	other threads:[~2021-03-08 11:17 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 [this message]
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
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=m1r1kpvqr0.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).