emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Yasushi SHOJI <yashi@atmark-techno.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: limitation for macro expansion
Date: Mon, 06 Mar 2017 17:41:34 +0100	[thread overview]
Message-ID: <87k2824atd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAKntEQ6aeM=-z55v5eYHL4qNzqiOzvCum9=oYav6r5sFgcEvvA@mail.gmail.com> (Yasushi SHOJI's message of "Mon, 6 Mar 2017 18:28:19 +0900")

Yasushi SHOJI <yashi@atmark-techno.com> writes:

> I assume that the key phrase is "anywhere Org markup is recognized".
> Link format doesn't allow Org markup, right?

Not in the first part indeed. You can, however, use a macro in the
description part of the link.

> # I use file_name_with_underscore.txt more than subscripts
> # I'd be nice, at least for me, to have '\sub' and '\super' special keywords
> # but leave the underscores alone.

I don't understand where you need this. At the export level, you can use
`org-export-with-sub-superscripts' to `{}'. At display level, you can do
the same with `org-use-sub-superscripts'.

> hmm.  just checked the source.  org-use-sub-superscripts is only for display.
> org-export-with-sub-superscripts is just for exports.

See above.

> I was gonna just by-pass or disable subscript parser all together when
> org-use-sub-superscripts is nil but it doesn't seems to be a good
> idea, does it?

This is exactly what a nil `org-export-with-sub-superscripts' does.

Regards,

  reply	other threads:[~2017-03-06 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04  9:58 limitation for macro expansion Yasushi SHOJI
2017-03-05 10:58 ` Nicolas Goaziou
2017-03-06  1:56   ` Yasushi SHOJI
2017-03-06  8:22     ` Nicolas Goaziou
2017-03-06  9:28       ` Yasushi SHOJI
2017-03-06 16:41         ` Nicolas Goaziou [this message]
2017-03-07  6:18           ` Yasushi SHOJI
2017-03-08 11:30             ` Nicolas Goaziou

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=87k2824atd.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=yashi@atmark-techno.com \
    /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).