emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Lasse Bombien <lasse@phonetik.uni-muenchen.de>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org, Carson Chittom <carson@wistly.net>
Subject: Re: protect slash - suppress markup
Date: Fri, 6 Jan 2012 12:03:08 +0100	[thread overview]
Message-ID: <83141AE9-9C8F-4A00-9086-E26E51F327E5@phonetik.uni-muenchen.de> (raw)
In-Reply-To: <87mxa22lqg.fsf@norang.ca>

Thanks a lot!

Lasse
Am 05.01.2012 um 16:49 schrieb Bernt Hansen:

> Carson Chittom <carson@wistly.net> writes:
> 
>> Bernt Hansen <bernt@norang.ca> writes:
>> 
>>> Lasse Bombien <lasse@phonetik.uni-muenchen.de> writes:
>>> 
>>>> Hi,
>>>> 
>>>> first of all: thanks for org-mode. I'm still new to it but love it already.
>>>> 
>>>> Now, I need to find a way to produce sentences like "The phonemes /l/
>>>> and /n/ …" in my exported documents. However, org-mode of course
>>>> transforms strings enclosed in slashes to emphasized text. This is
>>>> usually great, but in my area slashes are used as brackets for
>>>> phonological transcripts. Is there a way to locally suppress slashes
>>>> from being interpreted as markup characters (I tried backslashing and
>>>> double slashes…) or an entirely different way to accomplish this (I
>>>> tried: #+MACRO: phonem /$1/ …)?
>>>> 
>>>> I looked in the manual and the list archive but could find
>>>> anything. If I missed something, I apologize.
>>> 
>>> During export you can turn this off
>>> 
>>> #+OPTIONS: *:nil
>> 
>> But wouldn't that turn off, for example, *bolding* also?
> 
> Yes it would.  See Nick's answer about org-emphasis-alist.
> 
> Regards,
> Bernt
> 

next prev parent reply	other threads:[~2012-01-06 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 11:37 protect slash - suppress markup Lasse Bombien
2012-01-05 15:30 ` Bernt Hansen
2012-01-05 15:32   ` Carson Chittom
2012-01-05 15:49     ` Bernt Hansen
2012-01-06 11:03       ` Lasse Bombien [this message]
2012-01-05 15:35 ` Nick Dokos

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=83141AE9-9C8F-4A00-9086-E26E51F327E5@phonetik.uni-muenchen.de \
    --to=lasse@phonetik.uni-muenchen.de \
    --cc=bernt@norang.ca \
    --cc=carson@wistly.net \
    --cc=emacs-orgmode@gnu.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

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