From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, 22299@debbugs.gnu.org
Subject: bug#22299: Obsolete selective-display
Date: Fri, 22 Jan 2021 12:55:16 -0500 [thread overview]
Message-ID: <jwvft2suah8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874kj83mz9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 22 Jan 2021 18:22:50 +0100")
>> The second one is a UI functionality and it's sufficiently "not terribly
>> useful" that nobody bothered to write a replacement for it using
>> overlays (instead, all the possible replacements provide a more tailored
>> functionality).
> Right. So if we don't want to obsolete the other form (and Eli says he
> uses it all the time, so it doesn't sound like we want to), then I guess
> there's nothing more to be done here? So I'm closing this bug report.
We could try and re-implement `set-selective-display` using overlays,
of course.
And we could try and provide some other "text hiding" package more
specifically tailored to Eli's uses.
But really, I don't mind the `set-selective-display` feature now how
it's currently implemented, so I don't see a strong need to
replace/obsolete it.
The "selective-display == t" case is the one I care about because it
causes (well, "caused" since we started to drop that kind of
compatibility code) complexity in packages which had to deal with "end
of line can also be \r".
Stefan
next prev parent reply other threads:[~2021-01-22 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7j8u467a11.fsf@fencepost.gnu.org>
2019-03-18 16:09 ` bug#22299: Obsolete selective-display Glenn Morris
2021-01-21 16:56 ` Lars Ingebrigtsen
2021-01-21 17:14 ` Stefan Monnier
2021-01-22 17:22 ` Lars Ingebrigtsen
2021-01-22 17:55 ` Stefan Monnier [this message]
2021-01-21 19:42 ` 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
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=jwvft2suah8.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=22299@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@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).