emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: sergio <mailbox@sergio.spb.ru>
Cc: emacs-orgmode@gnu.org
Subject: Re: '=' and highlight
Date: Wed, 04 Jan 2012 00:15:07 +0100	[thread overview]
Message-ID: <87obukwf7o.fsf@gnu.org> (raw)
In-Reply-To: <4F037F4C.6080206@sergio.spb.ru> (sergio's message of "Wed, 04 Jan 2012 02:21:00 +0400")

Hi Sergio,

sergio <mailbox@sergio.spb.ru> writes:

> How org-mode decides, when to use this face?

See the docstring of `org-emphasis-regexp-components':

,----
| Components used to build the regular expression for emphasis.
| This is a list with five entries.  Terminology:  In an emphasis string
| like " *strong word* ", we call the initial space PREMATCH, the final
| space POSTMATCH, the stars MARKERS, "s" and "d" are BORDER characters
| and "trong wor" is the body.  The different components in this variable
| specify what is allowed/forbidden in each part:
| 
| pre          Chars allowed as prematch.  Beginning of line will be allowed too.
| post         Chars allowed as postmatch.  End of line will be allowed too.
| border       The chars *forbidden* as border characters.
| body-regexp  A regexp like "." to match a body character.  Don't use
|              non-shy groups here, and don't allow newline here.
| newline      The maximum number of newlines allowed in an emphasis exp.
| 
| Use customize to modify this, or restart Emacs after changing it.
`----

In your case, I think you want to prevent =...= to emphasize
(i.e. shadow) the text when the "border" character is `{'.

HTH,

-- 
 Bastien

      parent reply	other threads:[~2012-01-03 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 18:24 '=' and highlight sergio
2012-01-03 19:07 ` Nick Dokos
2012-01-03 19:41   ` sergio
2012-01-03 21:42     ` Nick Dokos
2012-01-03 22:21       ` sergio
2012-01-03 22:36         ` Sebastien Vauban
2012-01-03 22:37         ` Nick Dokos
2012-01-03 23:15         ` Bastien [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=87obukwf7o.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mailbox@sergio.spb.ru \
    /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).