From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Thien-Thi Nguyen <ttn@gnu.org>
Subject: Obsolescence warnings (was: [Emacs-diffs] master 9227b5c: last-chance: new utility lib for dangling deterrence)
Date: Sat, 24 Dec 2016 00:02:03 -0500 [thread overview]
Message-ID: <jwv1swydj50.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <20161224023808.9EE8D2201BC@vcs.savannah.gnu.org> (Thien-Thi Nguyen's message of "Sat, 24 Dec 2016 02:38:08 +0000 (UTC)")
> +;; [Insert "nobody reads ChangeLog files" lament, here. --ttn]
I think the problem is older, since it was made obsolete a long
time ago. IOW, the problem really is that there's no warning ever given
when we use an obsolete face.
In general, I think we're currently not proactive enough in warning
about uses of obsolete thingies: for functions and variables, we handle
that during byte-compilation, so those are mostly covered, but not so
for:
- faces (as evidenced here).
- user-variables or hooks (since the users most likely don't
byte-compile their ~/.emacs file).
- more generally code that isn't byte-compiled (it's very common for
users to use Elisp code without ever byte-compiling it).
- text-properties.
- I'm sure there are more cases.
I think it would be good to introduce a mechanism to tell the user
about uses of obsolete features. And by "user" here I mean "end user",
not because I prefer warning the end-user than the developer, but
because in many of those cases they're one and the same, and because in
other cases that's the best we can do.
To the extent that it affects the end-user and is caught during
execution, this mechanism needs to be very careful not to get in the
way, although it should be visible enough that we can reasonably expect
that the user will likely see those messages.
Stefan
next parent reply other threads:[~2016-12-24 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161224023808.12868.71069@vcs.savannah.gnu.org>
[not found] ` <20161224023808.9EE8D2201BC@vcs.savannah.gnu.org>
2016-12-24 5:02 ` Stefan Monnier [this message]
2017-01-11 14:25 ` Obsolescence warnings Thien-Thi Nguyen
2017-01-11 14:33 ` Stefan Monnier
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=jwv1swydj50.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ttn@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.
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.