emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Stanton <rhstanton@berkeley.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Parentheses in section titles interfere with on-screen font choice
Date: Mon, 27 Apr 2020 03:42:33 -0700	[thread overview]
Message-ID: <4A4DEF55-85A4-43AD-BD4E-76437834CD62@berkeley.edu> (raw)
In-Reply-To: <878sihw8mf.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

Much dissection of init.el later, it seems the problem was caused by an interaction with (an outdated version of) another package, rainbow-delimiters. Updating this seems to solve the problem.



> On Apr 27, 2020, at 3:00 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
> Richard Stanton <rhstanton@berkeley.edu <mailto:rhstanton@berkeley.edu>> writes:
>> When using org mode (9.3.6), I’ve noticed that putting parentheses
>> into a section title seems to change the font used to display the
>> title on the screen. So, for example, on my machine
>> * Heading
>> displays in a red font.
>> If I add something in parentheses, e.g.,
>> * Heading (with parentheses)
>> the title now displays in grey. As I’m typing, the font change occurs the moment I type the first character after the open parenthesis.
>> The behavior is similar for lower level headers too. Is this
>> deliberate? And if so, is there a way to put parentheses into section
>> titles without interfering with the display font?
> I cannot reproduce it. Is there something in your config?
> Regards,
> -- 
> Nicolas Goaziou

[-- Attachment #2: Type: text/html, Size: 8666 bytes --]

      parent reply	other threads:[~2020-04-27 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  9:48 Parentheses in section titles interfere with on-screen font choice Richard Stanton
2020-04-27 10:00 ` Nicolas Goaziou
2020-04-27 10:14   ` Richard Stanton
2020-04-27 10:42   ` Richard Stanton [this message]

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A4DEF55-85A4-43AD-BD4E-76437834CD62@berkeley.edu \
    --to=rhstanton@berkeley.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \


* 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


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).