From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 60399-done@debbugs.gnu.org, juri@linkov.net
Subject: bug#60399: 30.0.50; Usage of `isearch-open-invisible-temporary' is not documented
Date: Sun, 01 Jan 2023 13:00:04 +0200 [thread overview]
Message-ID: <83wn6634gb.fsf@gnu.org> (raw)
In-Reply-To: <87edse8vu1.fsf@localhost> (message from Ihor Radchenko on Sun, 01 Jan 2023 09:09:42 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: juri@linkov.net, 60399-done@debbugs.gnu.org
> Date: Sun, 01 Jan 2023 09:09:42 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Manual provides no more information.
> >>
> >> Would it make sense to mention that overlays passed as an argument of
> >> 'isearch-open-invisible-temporary function must not be destroyed?
> >
> > I've now added a warning to this effect to the comments in
> > isearch-open-overlay-temporary, and I'm therefore closing this bug.
>
> What about the manual?
> (elisp) 41.6 Invisible Text
I don't think this obscure issue needs to be mentioned in the manual.
It is quite clear to me that the overlay in question cannot be
deleted, I actually raised a brow when you asked for this to be
explicitly mentioned.
next prev parent reply other threads:[~2023-01-01 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 10:10 bug#60399: 30.0.50; Usage of `isearch-open-invisible-temporary' is not documented Ihor Radchenko
2022-12-29 17:33 ` Juri Linkov
2022-12-31 13:03 ` Ihor Radchenko
2023-01-01 9:05 ` Eli Zaretskii
2023-01-01 9:09 ` Ihor Radchenko
2023-01-01 11:00 ` Eli Zaretskii [this message]
2023-01-01 12:51 ` Ihor Radchenko
2023-01-01 13:55 ` Eli Zaretskii
2023-01-02 8:57 ` Ihor Radchenko
2023-01-02 12:29 ` Eli Zaretskii
2023-01-02 15:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 9:02 ` Ihor Radchenko
2023-01-03 14:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83wn6634gb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60399-done@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=yantar92@posteo.net \
/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).