From: Eli Zaretskii <eliz@gnu.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: egh@e6h.org, 42184@debbugs.gnu.org, kevin.legouguec@gmail.com,
mail@nicolasgoaziou.fr, bzg@gnu.org
Subject: bug#42184: 27.0.91; org-fontify-whole-heading-line does not work in emacs 27
Date: Thu, 06 Aug 2020 16:35:13 +0300 [thread overview]
Message-ID: <83pn8399ta.fsf@gnu.org> (raw)
In-Reply-To: <87zh782z3k.fsf@kyleam.com> (message from Kyle Meyer on Thu, 06 Aug 2020 00:10:55 -0400)
> From: Kyle Meyer <kyle@kyleam.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, egh@e6h.org, 42184@debbugs.gnu.org, mail@nicolasgoaziou.fr, bzg@gnu.org
> Date: Thu, 06 Aug 2020 00:10:55 -0400
>
> Kévin Le Gouguec writes:
>
> > Here is a variant of the previous patch, which correctly resets :extend
> > to nil if the user disables the relevant options (after reverting the
> > current buffer, or for newly opened ones).
> >
> > This ends up looking similar to what Org does for org-hide; IMO this
> > seems like the most straightforward short-term fix. In the long run,
> > these user options would probably deserve :set functions.
>
> Thanks for working on this fix. I of course can't speak for Bastien or
> Nicolas, but this patch looks fine to me. Assuming it's okay with Eli,
> I'd suggest applying it to the emacs-27 branch.
It's too late for Emacs 27.1, and in any case I'd like to hear the
blessing of Org developers before installing this. (I'd expect this
to be first installed in Org and then in Emacs, not the other way
around, but if it's okay with the Org folks to do it otherwise, I
won't object.)
next prev parent reply other threads:[~2020-08-06 13:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 2:29 bug#42184: 27.0.91; org-fontify-whole-heading-line does not work in emacs 27 Erik Hetzner
2020-07-04 17:13 ` Kévin Le Gouguec
2020-07-04 17:18 ` Eli Zaretskii
2020-07-04 17:50 ` Kévin Le Gouguec
2020-07-04 19:52 ` Kévin Le Gouguec
2020-07-05 2:30 ` Eli Zaretskii
2020-07-05 8:57 ` Kévin Le Gouguec
2020-07-05 14:58 ` Eli Zaretskii
2020-07-05 16:02 ` Kévin Le Gouguec
2020-07-05 16:21 ` Eli Zaretskii
2020-07-08 11:50 ` Kévin Le Gouguec
2020-07-09 14:16 ` Kévin Le Gouguec
2020-08-06 4:10 ` Kyle Meyer
2020-08-06 9:32 ` Kévin Le Gouguec
2020-08-06 13:35 ` Eli Zaretskii [this message]
2020-09-06 8:12 ` Bastien
2020-09-06 14:10 ` Kévin Le Gouguec
2020-09-06 15:06 ` Stefan Kangas
2020-09-06 14:19 ` Kyle Meyer
2020-09-06 15:06 ` Stefan Kangas
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=83pn8399ta.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42184@debbugs.gnu.org \
--cc=bzg@gnu.org \
--cc=egh@e6h.org \
--cc=kevin.legouguec@gmail.com \
--cc=kyle@kyleam.com \
--cc=mail@nicolasgoaziou.fr \
/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).