unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53764@debbugs.gnu.org
Subject: bug#53764: 27.1; shouldn't ~/diary be in diary-mode?
Date: Mon, 07 Feb 2022 05:17:21 +0100	[thread overview]
Message-ID: <87pmnzz4xa.fsf@web.de> (raw)
In-Reply-To: <878runz6e2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 07 Feb 2022 04:45:41 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Perhaps we should just do nothing

Yes, perhaps.

> -- people normally access the diary file via Calendar, which does
> everything it's supposed to.  Loading the diary file with `C-x C-f' is
> probably something most people don't do.

But I would not assume that.  People living "everything is a file" do
it.  I didn't know about the mode until I participated in this
discussion, I thought the highlighting would be some magic the diary
does when diary entries are displayed from the calendar, I didn't know
it's just a simple major mode.

And it's not necessary to use the calendar key interface to use the
diary, e.g. for calendar highlighting stuff or annotations.  It isn't
convenient to add complicated diary expressions or #includes to the
diary file from the calendar.  It's legitimate to edit the file the
normal way.

Maybe we can leave a short remark about the existence of the mode in the
manual?

Michael.





  reply	other threads:[~2022-02-07  4:17 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 [this message]
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             ` bug#53764: 27.1; shouldn't ~/diary be in diary-mode? Phil Sainty
2022-02-07  9:10           ` 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=87pmnzz4xa.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=53764@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).