From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 46979@debbugs.gnu.org, mardani29@yahoo.es
Subject: bug#46979: Allow setting Man-default-entry via Local Variables
Date: Tue, 09 Mar 2021 18:57:19 +0200 [thread overview]
Message-ID: <83tupkp8nk.fsf@gnu.org> (raw)
In-Reply-To: <87pn08e76z.5.fsf@jidanni.org> (message from 積丹尼 Dan Jacobson on Tue, 09 Mar 2021 22:24:20 +0800)
> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: mardani29@yahoo.es, 46979@debbugs.gnu.org
> Date: Tue, 09 Mar 2021 22:24:20 +0800
>
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>
> EZ> OK, but why do you insist on doing this via file-local variables?
>
> Because certainly the people who make the alists will probably think
> that crontab(1) is the man page people editing crontabs want to see,
> but individual programmer Williams wants to see crontab(5) usually.
> But wait! Not always. For his other cron page he more often wants to see
> cron(8), and even crontab(1posix). So you never know.
But Mr Williams does know! And the alist can be modified exactly like
the local-vars section in a file.
With your suggestion, by default Emacs will be none the wiser, because
wizard jidanni didn't visit every Mr Williams out there and offered
them his services of adding the local-vars section to every obscure
file they might have on their disk. Including flippant(1),
fartsburg(7) and whatnot.
A good tool shines when it does DWIM without any tinkering. The
"alist solution" has much higher chances of doing a large part of the
job, so insisting on not doing anything and leaving everything to the
user's tinkering makes little sense to me.
next prev parent reply other threads:[~2021-03-09 16:57 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 [this message]
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=83tupkp8nk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46979@debbugs.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).