From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: IRIE Shinsuke <irieshinsuke@yahoo.co.jp>,
5950@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#5950: defvaralias after defvar should be warned in runtime
Date: Thu, 2 Aug 2018 09:08:30 -0400 [thread overview]
Message-ID: <8e11e15a-a806-777e-1b18-3db9000c77de@gmail.com> (raw)
In-Reply-To: <jwvlg9pkbip.fsf-monnier+emacs@gnu.org>
On 2018-08-01 17:46, Stefan Monnier wrote:
>> Warning (defvaralias): Overwriting value of
>> ‘flycheck-python-pylint-executable’ by aliasing to
>> ‘python-shell-interpreter’
>
> This warning tells you that the variable
> `flycheck-python-pylint-executable` already had a value before the call
> to `defvaralias`, and that this value is lost at this point.
>
> Usually the warning is due to the defvaralias call being performed after
> the corresponding `defvar`s.
Right. But why is that a problem?
next prev parent reply other threads:[~2018-08-02 13:08 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
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 [this message]
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=8e11e15a-a806-777e-1b18-3db9000c77de@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=5950@debbugs.gnu.org \
--cc=irieshinsuke@yahoo.co.jp \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@gmail.com \
/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.