From: Phil Sainty <psainty@orcon.net.nz>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 53764@debbugs.gnu.org
Subject: bug#53764: 27.1; shouldn't ~/diary be in diary-mode?
Date: Tue, 08 Feb 2022 14:16:50 +1300 [thread overview]
Message-ID: <74eba74a460c09e725497f4ee26799a6@webmail.orcon.net.nz> (raw)
In-Reply-To: <87zgn35x2u.fsf@web.de>
On 2022-02-07 13:39, Michael Heerdegen wrote:
> We could automatically add a file local variable when Emacs
> creates the (main) diary file for the user.
To me this seems *much* better than the "do nothing" option.
People who don't want it can just delete the file-local var,
or change it to specify a different mode.
It won't directly help people with pre-existing diary files,
but if the change is called out in NEWS then those users can
be alerted to the fact that they might want to make that
change manually.
-Phil
next prev parent reply other threads:[~2022-02-08 1:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 22:12 bug#53764: 27.1; shouldn't ~/diary be in diary-mode? Francesco Potortì
2022-02-05 6:54 ` Lars Ingebrigtsen
2022-02-05 15:02 ` Francesco Potortì
2022-02-05 21:54 ` Lars Ingebrigtsen
2022-02-05 23:11 ` Francesco Potortì
2022-02-06 23:07 ` Lars Ingebrigtsen
2022-02-07 0:39 ` Michael Heerdegen
2022-02-07 3:45 ` Lars Ingebrigtsen
2022-02-07 4:17 ` Michael Heerdegen
2022-02-07 8:25 ` Lars Ingebrigtsen
2022-02-07 23:50 ` Michael Heerdegen
2022-02-09 18:03 ` Francesco Potortì
2022-02-07 19:39 ` Juri Linkov
2022-02-08 6:11 ` Lars Ingebrigtsen
2022-02-08 7:39 ` bug#53870: calendar-exit doesn't kill calendar buffers Juri Linkov
2022-02-09 8:32 ` Lars Ingebrigtsen
2022-02-08 1:16 ` Phil Sainty [this message]
2022-02-07 9:10 ` bug#53764: 27.1; shouldn't ~/diary be in diary-mode? Francesco Potortì
2022-02-07 9:28 ` Lars Ingebrigtsen
2022-02-09 18:21 ` Francesco Potortì
2022-02-09 21:26 ` Andreas Schwab
2022-02-09 21:52 ` Francesco Potortì
2022-02-06 3:54 ` Michael Heerdegen
2022-02-07 5:08 ` Richard Stallman
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=74eba74a460c09e725497f4ee26799a6@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=53764@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).