From: Oleh Krehel <ohwoeowho@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Conditional link export?
Date: Sun, 08 Nov 2015 15:56:33 +0100 [thread overview]
Message-ID: <87h9kwbkv2.fsf@gmail.com> (raw)
In-Reply-To: <87h9kw8t1t.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 08 Nov 2015 15:27:58 +0100")
Hi Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> There is already inline syntax for any language, including elisp:
>
> src_emacs-lisp{(foo)}
>
> and, if you use the library of Babel,
>
> call_foo{}
>
> I don't see the need to add yet another way to call inline code from an
> Org document.
Is that a new feature? First time I've heard about it, and I did google
for inline code block evaluation before.
In any case, the HTML export result of e.g. this:
The current time is: src_emacs-lisp{(format "<a href=%S>%s</a>" "http://google.com" (format-time-string "%H:%M"))}.
is:
The current time is: <code><a href</code>"<a href="http://google.com/">http://google.com/</a>">15:50</a>=.
which is far from what I want.
And I still think that Elisp could benefit from privileged call
syntax. Compare:
!(foo)
to
src_emacs-lisp{(foo)}
No one would quickly forget the first call syntax after using it once,
while the second one is highly forgettable and clumsy.
Additionally `org-edit-src-code' doesn't work for these blocks.
regards,
Oleh
next prev parent reply other threads:[~2015-11-08 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 13:02 Conditional link export? Oleh Krehel
2015-11-06 13:24 ` Aaron Ecay
2015-11-06 13:26 ` Aaron Ecay
2015-11-07 13:05 ` Oleh Krehel
2015-11-07 14:21 ` Aaron Ecay
2015-11-07 16:23 ` Achim Gratz
2015-11-08 14:09 ` Oleh Krehel
2015-11-08 14:27 ` Nicolas Goaziou
2015-11-08 14:56 ` Oleh Krehel [this message]
2015-11-08 15:04 ` Nicolas Goaziou
2015-11-08 15:35 ` Oleh Krehel
2015-11-08 16:06 ` Nicolas Goaziou
[not found] ` <m2k2ps9x9o.fsf@andrew.cmu.edu>
[not found] ` <8737wg6zi3.fsf@nicolasgoaziou.fr>
[not found] ` <m2ziy6vsw2.fsf@andrew.cmu.edu>
[not found] ` <87io4tpsu2.fsf@nicolasgoaziou.fr>
2015-11-22 23:08 ` John Kitchin
2015-11-08 18:03 ` Aaron Ecay
2015-11-06 13:28 ` John Kitchin
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=87h9kwbkv2.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--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).