all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23648@debbugs.gnu.org, pogonyshev@gmail.com,
	Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#23648: [PATCH] `defun-declarations-alist' can be unintentionally modified
Date: Mon, 18 Jul 2016 23:28:55 +0200	[thread overview]
Message-ID: <87r3aqbppk.fsf@web.de> (raw)
In-Reply-To: <83inw2227y.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 18 Jul 2016 22:08:49 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

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

I think the example uses macroexpand only to demonstrate what (obviously
ill) code you will get when you compile the mentioned form after
performing the completion as mentioned.

Michael.





  reply	other threads:[~2016-07-18 21:28 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r3aqbppk.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=23648@debbugs.gnu.org \
    --cc=eliz@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 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.