emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Henrik Frisk <frisk.h@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
	 org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: org-fontify-emphasized-text
Date: Tue, 18 Jul 2023 06:29:09 +0100	[thread overview]
Message-ID: <878rbdg53u.fsf@yandex.com> (raw)
In-Reply-To: <CAO0LSb5V+swAzpDBdb=bHEkWPP858uXy0JpVbiGdE1jdzMBsXg@mail.gmail.com> (Henrik Frisk's message of "Mon, 17 Jul 2023 22:54:32 +0200")

>>>>> Henrik Frisk <frisk.h@gmail.com> writes:

    > On Mon, Jul 17, 2023, 1:23 PM Ihor Radchenko <yantar92@posteo.net> wrote:
    >> Henrik Frisk <frisk.h@gmail.com> writes:
    >> 
    >>> For the first time I tried to enable the fontification of
    >>> emphasized text but quickly decided I didn't want it. But I
    >>> can't seem to get rid of it.  For example, any part of a
    >>> filename that is after an underscore is still printed as subtext
    >>> (expected if fontification is on). Is there anything else than
    >>> the above variable that controls this? emacs -Q works of course
    >>> fine.
    >> 
    >> Can't get rid even after re-starting Emacs?
    >> 

    > Exactly, I've had it for weeks annoyingly.

Indeed, it is VERY annoying. Setting

(setq org-use-sub-superscripts nil)

(the default is t) seems to ensure that it does not come on even if some
library puts `org-pretty-entities' to t.

Best wishes,

Colin Baxter.


  reply	other threads:[~2023-07-18  5:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 11:18 org-fontify-emphasized-text Henrik Frisk
2023-07-17 11:23 ` org-fontify-emphasized-text Ihor Radchenko
2023-07-17 20:54   ` org-fontify-emphasized-text Henrik Frisk
2023-07-18  5:29     ` Colin Baxter [this message]
2023-07-18  8:19     ` org-fontify-emphasized-text Ihor Radchenko

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.orgmode.org/

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

  git send-email \
    --in-reply-to=878rbdg53u.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=frisk.h@gmail.com \
    --cc=yantar92@posteo.net \
    /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/org-mode.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).