From: Lars Ingebrigtsen <larsi@gnus.org>
To: Par Kurlberg <kurlberg@math.kth.se>
Cc: 43537@debbugs.gnu.org
Subject: bug#43537: 26.3; "lost" diary entries - mark-diary-entries-in-calendar obsolete
Date: Mon, 21 Sep 2020 14:32:03 +0200 [thread overview]
Message-ID: <87v9g7payk.fsf@gnus.org> (raw)
In-Reply-To: <875z88on9w.fsf@math.kth.se> (Par Kurlberg's message of "Sun, 20 Sep 2020 10:39:07 +0200")
Par Kurlberg <kurlberg@math.kth.se> writes:
> Of course, in theory I've been amply warned - the documentation states
> "mark-diary-entries-in-calendar is obsolete since 23.1". However, given
> that anyone who relies on keeping track of meetings via
> emacs/diary/calender easily might miss a few meetings before noticing
> this, perhaps emacs26+ could warn if mark-diary-entries-in-calendar is
> true whereas calendar-view-diary-initially-flag is unset?
>
> More generally, some sort of mechanisms for "important" upgrade warnings
> on obsolete variables having been removed would be very helpful, but it
> is perhaps hard to figure out / agree on exactly what are "important
> enough" changes.
Yeah, I don't think this is generally possible. The variable in
question was obsoleted about a decade ago, which should be sufficient
time for people to adjust. Adding more code to Emacs to warn people
about things happening that far in the past would not be productive use
of our time.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-21 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:39 bug#43537: 26.3; "lost" diary entries - mark-diary-entries-in-calendar obsolete Par Kurlberg
2020-09-21 12:32 ` Lars Ingebrigtsen [this message]
2020-09-22 3:32 ` Richard Stallman
2020-09-22 15:02 ` Lars Ingebrigtsen
2020-09-23 3:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9g7payk.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43537@debbugs.gnu.org \
--cc=kurlberg@math.kth.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.