From: Noam Postavsky <npostavs@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: IRIE Shinsuke <irieshinsuke@yahoo.co.jp>, 5950@debbugs.gnu.org
Subject: bug#5950: defvaralias after defvar should be warned in runtime
Date: Sat, 26 May 2018 19:54:34 -0400 [thread overview]
Message-ID: <871sdyezwl.fsf@gmail.com> (raw)
In-Reply-To: <874liufjfj.fsf@gmail.com> (Noam Postavsky's message of "Sat, 26 May 2018 12:52:48 -0400")
>> The bootstrap warnings were about cl-custom-print-functions,
>> mail-dont-reply-to-names,
Oh, it's because the definition gets into loaddefs.el, but the alias
doesn't.
>> and several flymake-proc-* variables all of
>> which correctly have the alias before the definition.
Not 100% sure about the flymake ones, but I guess it's some double
loading during bootstrap.
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> I'd make it just a `message` rather than a `display-warning`.
Hmm, I think it's too easy to overlook that, I prefer the in-your-face
nature of display-warning.
next prev parent reply other threads:[~2018-05-26 23:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 5:13 bug#5950: defvaralias after defvar should be warned in runtime IRIE Shinsuke
2010-09-15 20:16 ` Glenn Morris
2010-09-16 0:44 ` IRIE Shinsuke
2010-09-16 3:51 ` Glenn Morris
2010-09-16 9:27 ` Stefan Monnier
2018-05-26 16:52 ` Noam Postavsky
2018-05-26 19:46 ` Stefan Monnier
2018-05-26 23:54 ` Noam Postavsky [this message]
2018-06-12 11:48 ` Noam Postavsky
[not found] ` <cb864996-c592-5507-f0c6-be07d17f13ee@gmail.com>
[not found] ` <jwvlg9pkbip.fsf-monnier+emacs@gnu.org>
2018-08-02 13:08 ` Clément Pit-Claudel
2018-08-02 13:28 ` Noam Postavsky
2018-08-02 14:37 ` Clément Pit-Claudel
2018-08-02 17:03 ` Stefan Monnier
2018-08-03 3:33 ` Clément Pit-Claudel
2018-08-03 20:23 ` Noam Postavsky
2018-08-03 21:00 ` Clément Pit-Claudel
2018-08-03 22:09 ` Noam Postavsky
2018-08-03 22:24 ` Clément Pit-Claudel
2018-08-03 21:58 ` Stefan Monnier
2018-08-02 2:14 ` Noam Postavsky
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=871sdyezwl.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=5950@debbugs.gnu.org \
--cc=irieshinsuke@yahoo.co.jp \
--cc=monnier@IRO.UMontreal.CA \
/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.