From: Eli Zaretskii <eliz@gnu.org>
To: monnier@iro.umontreal.ca
Cc: 72616@debbugs.gnu.org, gerard.vermeulen@posteo.net, joaotavora@gmail.com
Subject: bug#72616: 30.0.60; M-x apropos-library eglot fails
Date: Sat, 17 Aug 2024 12:46:45 +0300 [thread overview]
Message-ID: <86r0an32ii.fsf@gnu.org> (raw)
In-Reply-To: <86o75v8bnk.fsf@gnu.org> (message from Eli Zaretskii on Wed, 14 Aug 2024 16:41:19 +0300)
> Cc: 72616@debbugs.gnu.org, gerard.vermeulen@posteo.net, joaotavora@gmail.com
> Date: Wed, 14 Aug 2024 16:41:19 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Cc: gerard.vermeulen@posteo.net, joaotavora@gmail.com, 72616@debbugs.gnu.org
> > Date: Wed, 14 Aug 2024 08:47:40 -0400
> >
> > >> This doesn't look right: the meaning of `define-symbol-props` in
> > >> `load-history` should be defined in a more modular way, near
> > >> `define-symbol-prop` rather than by hardcoding something in
> > >> `apropos.el`.
> > >
> > > Is it better to leave us where we are now: that apropos-library
> > > signals an error instead of displaying the information about the
> > > library?
> >
> > In the mean time we could just sanitize the data we use heuristically,
> > as in the patch below.
>
> Thanks, will install soon unless someone has a better suggestion.
Now done.
prev parent reply other threads:[~2024-08-17 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 8:04 bug#72616: 30.0.60; M-x apropos-library eglot fails Gerard Vermeulen
2024-08-14 9:09 ` Eli Zaretskii
2024-08-14 11:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 12:14 ` Eli Zaretskii
2024-08-14 12:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 13:41 ` Eli Zaretskii
2024-08-17 9:46 ` Eli Zaretskii [this message]
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=86r0an32ii.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72616@debbugs.gnu.org \
--cc=gerard.vermeulen@posteo.net \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.