all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Allen Li <darkfeline@felesatra.moe>
Cc: 32395@debbugs.gnu.org
Subject: bug#32395: 26.1; generated autoloads includes string properties if buffer is open
Date: Sat, 11 Aug 2018 12:18:16 +0300	[thread overview]
Message-ID: <838t5dmfc7.fsf@gnu.org> (raw)
In-Reply-To: <CADbSrJza9wZ8prPmD005-RvnwTry-Oq9LRYVTDCcOE4srxL1qA@mail.gmail.com> (message from Allen Li on Wed, 8 Aug 2018 00:09:22 -0700)

> From: Allen Li <darkfeline@felesatra.moe>
> Date: Wed, 8 Aug 2018 00:09:22 -0700
> 
> The autoload generation code inserts a form with a string that may or
> may not have text properties, depending on if the buffer is already
> open.
> 
> (if (fboundp 'register-definition-prefixes)
>              (register-definition-prefixes "foo"
>                                            '(#("foo-" 0 4 (fontified nil)))))
> 
> (if (fboundp 'register-definition-prefixes)
>              (register-definition-prefixes "foo" '("foo-")))
> 
> This makes autoload generation depend on the odd condition of whether
> the file under consideration is already open and fontified.

Can you tell more about the use case where you see this?  Does this
happen when the autoload files in the Emacs tree are generated?





  parent reply	other threads:[~2018-08-11  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  7:09 bug#32395: 26.1; generated autoloads includes string properties if buffer is open Allen Li
2018-08-08  7:13 ` bug#32395: [PATCH] Don't include text properties when making autoloads Allen Li
2018-08-11  9:18 ` Eli Zaretskii [this message]
2018-08-11  9:49   ` bug#32395: 26.1; generated autoloads includes string properties if buffer is open Allen Li
2018-08-17 14:10     ` Eli Zaretskii

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=838t5dmfc7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32395@debbugs.gnu.org \
    --cc=darkfeline@felesatra.moe \
    /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.