From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51016@debbugs.gnu.org, larsi@gnus.org, orontee@gmail.com,
juri@linkov.net
Subject: bug#51016: 28.0.50; 'diff-font-lock-prettify' breaks display of outline headers
Date: Sun, 19 Dec 2021 00:30:52 +0100 [thread overview]
Message-ID: <87bl1dmqxf.fsf@gmail.com> (raw)
In-Reply-To: <83ilvladfc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Dec 2021 22:03:19 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
>> Cc: Juri Linkov <juri@linkov.net>, 51016@debbugs.gnu.org, larsi@gnus.org,
>> orontee@gmail.com
>> Date: Sat, 18 Dec 2021 20:43:18 +0100
>>
>> I guess the assumption Juri and I are working with (and maybe Lars too,
>> since IIUC he added these buttons to act as visual cues to indicate
>> places which can be expanded or collapsed) is that the purpose of
>> outline-regexp is to capture "heading" lines, by which we mean titles
>> and subtitles which define a hierarchy of things to show and hide.
>
> You are treating NEWS as if it were an Org document. It isn't.
I don't see where Org enters the picture from my description? AFAICT
this "assumption" I described is just paraphrasing outline-mode's
docstring:
> Set major mode for editing outlines with selective display.
> Headings are lines which start with asterisks: one for major headings,
> two for subheadings, etc. Lines not starting with asterisks are body lines.
>
> Body text or subheadings under a heading can be made temporarily
> invisible, or visible again.
>> These form feeds do not contribute to the document's hierarchy. They do
>> not have subsections to expand or collapse. Despite this, they are
>> treated as level-1 headings.
>>
>> That leads to what Juri and I consider "absurd" results:
>>
>> - outline-forward-same-level pauses on them: why? There's nothing for
>> a user to expand or collapse there;
>>
>> - outline-minor-mode-use-buttons adds these clickable buttons: why?
>> There's nothing for a user to expand or collapse there.
>
> These are _page_ delimiters. They are conceptually _above_ level-1
> headings.
Right; unfortunately, in addition to this *conceptual* understanding of
form feeds, *functionally* they are treated as level-1 headings, with
the unfortunate consequences we highlighted.
As you point out, they are page delimiters; if we were to take them out
of outline-regexp, page commands (navigation, marking, narrowing) would
keep working just fine!
next prev parent reply other threads:[~2021-12-18 23:30 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
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 [this message]
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=87bl1dmqxf.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=51016@debbugs.gnu.org \
--cc=eliz@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).