From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 51016@debbugs.gnu.org, larsi@gnus.org, orontee@gmail.com
Subject: bug#51016: 28.0.50; 'diff-font-lock-prettify' breaks display of outline headers
Date: Thu, 16 Dec 2021 22:06:55 +0200 [thread overview]
Message-ID: <83ee6cfh5s.fsf@gnu.org> (raw)
In-Reply-To: <86fsqs4bi2.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 16 Dec 2021 21:04:37 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: larsi@gnus.org, 51016@debbugs.gnu.org, orontee@gmail.com
> Date: Thu, 16 Dec 2021 21:04:37 +0200
>
> > Why are you talking about Org, when the proposed change is in
> > outline.el?
>
> Because most people use Org that has more reasonable defaults.
You are free to use Org if that fits your workflows better. That
doesn't mean we need to ignore users of Outline that don't use Org.
> > Please don't change the behavior of outline.el in
> > backward-incompatible ways. This is used for NEWS and similar files,
> > and those do have ^L separators in them.
>
> The proposed change is to improve NEWS and similar files to make
> their views more compact by fitting more lines on the screen.
What does this have to do with removing support for ^L?
next prev parent reply other threads:[~2021-12-16 20:06 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 21:05 bug#51016: 28.0.50; 'diff-font-lock-prettify' breaks display of outline headers Matthias Meulien
2021-10-09 0:26 ` bug#51016: Status: " Matthias Meulien
2021-10-09 0:37 ` Matthias Meulien
2021-10-13 20:30 ` bug#51016: " Matthias Meulien
2021-11-05 2:51 ` Lars Ingebrigtsen
2021-11-06 16:40 ` Juri Linkov
2021-11-06 18:30 ` Lars Ingebrigtsen
2021-11-08 22:38 ` Matthias Meulien
2021-11-09 3:47 ` Lars Ingebrigtsen
2021-11-09 8:19 ` Juri Linkov
2021-11-18 18:06 ` Juri Linkov
2021-11-19 7:22 ` Lars Ingebrigtsen
2021-11-19 8:31 ` Juri Linkov
2021-11-20 8:37 ` Lars Ingebrigtsen
2021-11-20 19:17 ` Juri Linkov
2021-11-21 17:02 ` Lars Ingebrigtsen
2021-11-21 17:26 ` Matthias Meulien
2021-11-21 17:41 ` Juri Linkov
2021-11-21 17:54 ` Matthias Meulien
2021-11-22 22:11 ` Matthias Meulien
2021-11-22 23:03 ` Matthias Meulien
2021-11-24 6:54 ` Lars Ingebrigtsen
2021-11-24 18:48 ` Juri Linkov
2021-12-15 17:08 ` Juri Linkov
2021-12-16 5:50 ` Lars Ingebrigtsen
2021-12-16 17:22 ` Juri Linkov
2021-12-16 17:48 ` Eli Zaretskii
2021-12-16 19:04 ` Juri Linkov
2021-12-16 20:06 ` Eli Zaretskii [this message]
2021-12-16 21:02 ` Kévin Le Gouguec
2021-12-17 6:36 ` Eli Zaretskii
2021-12-17 7:07 ` Kévin Le Gouguec
2021-12-17 7:55 ` Eli Zaretskii
2021-12-17 21:27 ` Kévin Le Gouguec
2021-12-18 6:23 ` Eli Zaretskii
2021-12-18 9:18 ` Kévin Le Gouguec
2021-12-18 17:05 ` Juri Linkov
2021-12-18 17:52 ` Eli Zaretskii
2021-12-18 19:43 ` Kévin Le Gouguec
2021-12-18 20:03 ` Eli Zaretskii
2021-12-18 23:30 ` Kévin Le Gouguec
2021-12-19 11:00 ` Lars Ingebrigtsen
2021-12-19 11:27 ` Eli Zaretskii
2021-12-17 4:25 ` Richard Stallman
2021-11-21 17:49 ` Juri Linkov
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=83ee6cfh5s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51016@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=orontee@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 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).