From: Mark Oteiza <mvoteiza@udel.edu>
To: emacs-devel@gnu.org
Subject: help-fns unsolicited elisp loading (was Re: bug#28048: 26.0.50; behaviour of C-h f semantic-mode)
Date: Fri, 22 Sep 2017 00:09:09 -0400 [thread overview]
Message-ID: <20170922040909.5vcbffvvyn7hoexr@logos.localdomain> (raw)
In-Reply-To: <87k2291rru.fsf@users.sourceforge.net>
On 12/08/17 at 01:47am, npostavs@users.sourceforge.net wrote:
> Mark Oteiza <mvoteiza@udel.edu> writes:
>
> > Is there a bug associated with the new C-h f behaviour?
>
> No, it was introduced on emacs-devel, see [1] and followups.
>
> [1]: http://lists.gnu.org/archive/html/emacs-devel/2016-05/msg00441.html
Now I know why I'd get seemingly random messages about MH-E not being
present on my system.
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=fd8084aaf9
Why are we loading (effectively) arbitrary elisp without the user asking
for it? Any elisp in Emacs--including installed 3rdp packages--can get
loaded when looking for function or variable help. Further, loading
elisp can do anything, so a PoC is trivial. Not even considering the
security part of it, I'm going to end up with way more stuff loaded,
potentially having more crap to sift through in apropos. Please at the
very least disable this by default before it goes into a release.
For the record, the following init.el shim restores the previous
behavior:
(with-eval-after-load "help-fns"
(defun my-obarray (string pred action)
(complete-with-action action obarray string pred))
(fset 'help--symbol-completion-table 'my-obarray))
next parent reply other threads:[~2017-09-22 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87poc22mjg.fsf@holos>
[not found] ` <2mlgmq14t5.fsf@fencepost.gnu.org>
[not found] ` <87poc2qdlj.fsf@holos>
[not found] ` <87k2291rru.fsf@users.sourceforge.net>
2017-09-22 4:09 ` Mark Oteiza [this message]
2017-09-22 4:28 ` help-fns unsolicited elisp loading (was Re: bug#28048: 26.0.50; behaviour of C-h f semantic-mode) Noam Postavsky
2017-09-23 14:50 ` Mark Oteiza
2017-09-23 15:38 ` 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
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=20170922040909.5vcbffvvyn7hoexr@logos.localdomain \
--to=mvoteiza@udel.edu \
--cc=emacs-devel@gnu.org \
/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).