unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 23648@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#23648: [PATCH] `defun-declarations-alist' can be unintentionally modified
Date: Mon, 18 Jul 2016 22:08:49 +0300	[thread overview]
Message-ID: <83inw2227y.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-92sYy7FouMXMVri5p38b-TkivqgdHu1p-1vwA+PrwWog@mail.gmail.com> (message from Noam Postavsky on Mon, 18 Jul 2016 14:58:20 -0400)

> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Mon, 18 Jul 2016 14:58:20 -0400
> Cc: Paul Pogonyshev <pogonyshev@gmail.com>, 23648@debbugs.gnu.org
> 
> >> Now move point to just after "indent" and type C-M-i (this gives
> >> message "Sole completion"), macroexpanding now gives
> >>
> >> (prog1
> >>     (defalias 'foo
> >>       #'(lambda nil nil))
> >>   "Warning: Unknown defun property `indent' in foo")
> >
> > Sorry, I'm not following: what do you mean by "macroexpanding" in this
> > context?
> 
> Calling macroexpand on the defun form. The most convenient method for
> testing is to put point at the closing bracket of the defun, and then
> `M-x pp-macroexpand-last-sexp'.
> 
> > When you wrote "when performing completion", I expected to
> > see some simple completion gesture that leads to an error, but it
> > sounds like I'm missing something.
> 
> The simple completion gesture would be the C-M-i I mentioned, which
> (silently) destroys the value of defun-declarations-alist. The
> symptoms of the wrong value can be seen when defun is macroexpanded.

Sorry, I guess I'm too stupid to understand this advanced stuff.  Or
maybe it's too late.

Thanks.





  reply	other threads:[~2016-07-18 19:08 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 [this message]
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
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=83inw2227y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23648@debbugs.gnu.org \
    --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).