emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Markup (=, ~) in word?
Date: Thu, 29 Oct 2015 17:04:59 +0300	[thread overview]
Message-ID: <87h9l9ojn8.fsf@gkayaalp.com> (raw)
In-Reply-To: <m2bnbhc442.fsf@krugs.de> (Rainer M. Krug's message of "Thu, 29 Oct 2015 12:21:17 +0100")

On Thu, Oct 29 2015 at  2:21:17 pm EEST, Rainer M Krug <Rainer@krugs.de> wrote:
> Matt Price <moptop99@gmail.com> writes:
>
>> #+BEGIN_VERBATIM
>> simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID=
>> #+END_VERBATIM
>
> The other way round:
>
> I want the text, e.g. =SITE= as the markup, and not the whole text as
> verbatim - sorry for not being clear about what I want.
>
> Rainer
>

AFAIK that is  impossible out of the box, Org  does not allow inter-word
markup,  as there  is no  escaping in  the syntax.   In the  thread with
subject  *Some  projects* on  this  list  they  talk also  about  adding
escaping.  You can still add some inline LaTeX for that though, I think,
or  maybe you  can  tweak  `org-emphasis-regexp-components', (also,  see
[1]):

,----[ C-h v org-emphasis-regexp-components RET ]
| org-emphasis-regexp-components is a variable defined in `org.el'.
| Its value is (" 	('\"{" "- 	.,:!?;'\")}\\" " 	
| ,\"'" "." 1)
| 
| Documentation:
| 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.
| 
| You need to reload Org or to restart Emacs after customizing this.
| 
| [back]
`----

> [...]

[1] http://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers

Regards,
-gk

-- 
İ. Göktuğ Kayaalp.
http://gkayaalp.com/

  reply	other threads:[~2015-10-29 13:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 11:06 Markup (=, ~) in word? Rainer M Krug
2015-10-29 11:11 ` Matt Price
2015-10-29 11:21   ` Rainer M Krug
2015-10-29 14:04     ` Göktuğ Kayaalp [this message]
2015-10-29 14:07       ` Rainer M Krug
2015-10-29 14:23         ` Göktuğ Kayaalp
2015-10-29 17:08     ` Charles C. Berry
2015-10-29 18:26       ` Rainer M Krug
2015-10-29 20:40 ` Rasmus
2015-10-30  9:24   ` Rainer M Krug

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=87h9l9ojn8.fsf@gkayaalp.com \
    --to=self@gkayaalp.com \
    --cc=Rainer@krugs.de \
    --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
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).