From: Drew Adams <drew.adams@oracle.com>
To: help-gnu-emacs@gnu.org
Subject: RE: trailing whitespace in calendar
Date: Wed, 1 Feb 2017 08:40:11 -0800 (PST) [thread overview]
Message-ID: <ced926a1-812b-4d25-9434-5aeb2eedeca5@default> (raw)
In-Reply-To: <87y3xqclj7.fsf@gmail.com>
> > (add-hook 'today-visible-calendar-hook ...
>
> That hook got renamed to calendar-today-visible-hook
Actually, it's not the problem that it was renamed. The
problem is that the old name is no longer recognized.
The option was renamed in Emacs 23, but Emacs remained smart
enough and careful enough, through release 24.5, to continue
to respect the old name as well. This respect (support) was
removed in Emacs 25.
Prior to Emacs 25, Emacs did the following just before the
defcustom for the new name, `calendar-today-visible-hook':
(define-obsolete-variable-alias 'today-visible-calendar-hook
'calendar-today-visible-hook "23.1")
As `C-h f define-obsolete-variable-alias' says:
If CURRENT-NAME is a defcustom ... then the
define-obsolete-variable-alias statement should be
evaluated before the defcustom, if user customizations
are to be respected.
IOW, `define-obsolete-variable-alias' is an easy way
to warn users about a name change but also continue to
support the old name.
It was decided in Emacs 25 that this user customization
(and others that were also deprecated in Emacs 23) is no
longer to be respected.
It is _good_ for users to use the new names. Whether it
is good for them to be forced (silently) to use them is
a different question. At any rate, that's the case now.
It might be better perhaps if the warning, which tells
you what the new name is, continued to be issued, even
after support was discontinued.
For example, after desupport the warning message could
perhaps be changed to an error (raised when the old name
is used), to let you know what the problem is. Then
users like Luis would not need to wonder "Do you know
why this is not working now?"
Instead, Emacs just fails to recognize the old name now.
prev parent reply other threads:[~2017-02-01 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 1:16 trailing whitespace in calendar luis o silva
2017-02-01 9:23 ` Robert Pluim
2017-02-01 16:40 ` Drew Adams [this message]
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=ced926a1-812b-4d25-9434-5aeb2eedeca5@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.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.
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).