From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: michael_heerdegen@web.de, 23648@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#23648: [PATCH] `defun-declarations-alist' can be unintentionally modified
Date: Thu, 21 Jul 2016 17:22:59 +0300 [thread overview]
Message-ID: <83d1m7yssc.fsf@gnu.org> (raw)
In-Reply-To: <87a8hbdcfd.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Cc: Michael Heerdegen <michael_heerdegen@web.de>, 23648@debbugs.gnu.org, pogonyshev@gmail.com
> Date: Wed, 20 Jul 2016 21:09:42 -0400
>
> > Thanks, but I'm still none the wiser about the questions I asked.
>
> Hmm, maybe it will be clearer like this:
>
> Evaluate:
>
> (macroexpand '(defun foo ()
> (declare (indent 1))
> nil)) ;=> (prog1 (defalias (quote foo) (function (lambda nil
> nil))) (function-put (quote foo) (quote lisp-indent-function) (quote 1)))
>
> This gives the correct result (the (function-put...) part comes from the
> (declare (indent 1))).
>
> Now perform a completion on a declare clause, e.g., put cursor after
> "ind" and hit C-M-i: (declare (ind)) completes to (declare (indent)).
>
> Now evaluate the same expression as before:
>
> (macroexpand '(defun foo ()
> (declare (indent 1))
> nil)) ;=> (prog1 (defalias (quote foo) (function (lambda nil
> nil))) "Warning: Unknown defun property ‘indent’ in foo")
>
> This give the wrong result, the (declare (indent 1)) is giving the
> "Warning:...". Emacs has unlearned the indent declaration. In fact it
> unlearned all the declarations for defun except for gv-setter, you can
> see this by looking at defun-declarations-alist's value.
Thanks, but I think we are mis-communicating. What I need is not a
demonstration of the bug in action; I already got that. What I asked
for is different:
> How probable is the situation where this problem pops up? And when
> was the bug introduced?
You already answered the second question. For the first, I expected
to see something done frequently by either users or Lisp programs,
which bumps into this bug. Evaluating macroexpand, twice, with
completion in-between, doesn't qualify in my book as a frequent user
action, I hope you will agree (even if you personally happen to use it
quite a lot).
So I'm still looking for the answer to the "how probable" question. I
need that to make up my mind about the urgency of the fix.
Thanks.
next prev parent reply other threads:[~2016-07-21 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 14:11 bug#23648: [PATCH] `defun-declarations-alist' can be unintentionally modified Paul Pogonyshev
2016-07-18 3:00 ` npostavs
2016-07-18 14:33 ` Eli Zaretskii
2016-07-18 15:53 ` Noam Postavsky
2016-07-18 18:16 ` Eli Zaretskii
2016-07-18 18:58 ` Noam Postavsky
2016-07-18 19:08 ` Eli Zaretskii
2016-07-18 21:28 ` Michael Heerdegen
2016-07-19 2:40 ` Eli Zaretskii
2016-07-21 1:09 ` npostavs
2016-07-21 14:22 ` Eli Zaretskii [this message]
2016-07-21 21:27 ` Noam Postavsky
2016-07-23 8:54 ` Eli Zaretskii
2016-07-23 14:18 ` npostavs
2016-07-24 17:07 ` Paul Pogonyshev
2016-07-24 17:31 ` Eli Zaretskii
2016-07-18 19:17 ` Dmitry Gutov
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=83d1m7yssc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23648@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
--cc=pogonyshev@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).