all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: mvoteiza@udel.edu, 28607@debbugs.gnu.org
Subject: bug#28607: 27.0.50; help-fns unsolicited elisp loading
Date: Thu, 16 May 2019 16:38:24 +0300	[thread overview]
Message-ID: <83sgtecyen.fsf@gnu.org> (raw)
In-Reply-To: <874l5vf8q5.fsf@gmail.com> (message from Noam Postavsky on Wed, 15 May 2019 22:12:34 -0400)

> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Glenn Morris <rgm@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,  28607@debbugs.gnu.org
> Date: Wed, 15 May 2019 22:12:34 -0400
> 
> > At minimum an option to disable it, which is what I'm already doing as
> > a workaround.
> 
> Right, here's patch for that.  I made a new option instead of extending
> help-enable-auto-load because otherwise I would have to think about how
> to dis/enable them each individually, which is annoying to encode in a
> single option.

Thanks, this LGTM.  I wonder whether we should document
definition-prefixes (together with the mechinery it is part of) and
this new option in the ELisp manual.





  reply	other threads:[~2019-05-16 13:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 12:49 bug#28607: 27.0.50; help-fns unsolicited elisp loading Mark Oteiza
2017-09-26 15:40 ` Glenn Morris
2017-09-26 15:51   ` Mark Oteiza
2018-07-02 17:57     ` Eli Zaretskii
2018-07-02 18:05       ` Mark Oteiza
2018-07-02 18:16         ` Eli Zaretskii
2018-07-03  1:29         ` Glenn Morris
2018-07-16 13:03           ` Mark Oteiza
2019-05-16  2:12             ` Noam Postavsky
2019-05-16 13:38               ` Eli Zaretskii [this message]
2019-05-18 16:00                 ` Noam Postavsky
2019-05-18 16:15                   ` Eli Zaretskii
2019-05-20 17:49                     ` Noam Postavsky
2019-05-20 19:01                       ` Eli Zaretskii
2019-05-21 11:45                         ` 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=83sgtecyen.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28607@debbugs.gnu.org \
    --cc=mvoteiza@udel.edu \
    --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.