From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Stig Brautaset <stig@brautaset.org>
Cc: Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Confusing interaction when typing leading * for headings when org-hide-emphasis-markers is on
Date: Sat, 25 Nov 2017 21:29:27 +0100 [thread overview]
Message-ID: <87mv3at848.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m28teu6z13.fsf@brautaset.org> (Stig Brautaset's message of "Sat, 25 Nov 2017 18:36:40 +0100")
Hello,
Stig Brautaset <stig@brautaset.org> writes:
> I've got =(setq org-hide-emphasis-markers t)= in my config, and it's
> mostly great but it does confuse me when I manually start sub-sub
> headings. (Which perhaps is a silly thing to do, but getting over
> muscle memory is hard to change.) After typing the third =*= (and on
> any subsequent ones typed) the first and last asterisks are hidden and
> the remaining appear bolded, until I type a space when what I'm typing
> is suddenly recognised as a heading and snaps back to displaying all
> the typed asterisks as expected.
>
> I couldn't figure out how to post a video, so visually, here is what
> I see. One character typed on each line (comments after =;=):
>
> : *
> : **
> : * ; this is in bold
> : ** ; this is in bold
> : **** ; asterisks no longer bold after typing a space
>
> I tried adding an asterisks to the BORDER characters in
> org-emphasis-regexp-components, but that didn't seem to help.
It is something to be expected with a non-nil
`org-hide-emphasis-markers'. "***" at the beginning of the line is
really a bold asterisk, whereas "*** " is a headline.
I suggest to use M-RET to circumvent the problem. You will quickly get
used to it.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2017-11-25 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 17:36 Confusing interaction when typing leading * for headings when org-hide-emphasis-markers is on Stig Brautaset
2017-11-25 20:29 ` Nicolas Goaziou [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:
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=87mv3at848.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=stig@brautaset.org \
/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).