From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: How to elegantly and effectively quote org fragments?
Date: Sat, 23 May 2015 21:59:51 +0200 [thread overview]
Message-ID: <87zj4vdpzc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <21854.45700.397098.880360@frac.u-strasbg.fr> (Alain Cochard's message of "Fri, 22 May 2015 06:37:24 +0200")
Alain.Cochard@unistra.fr writes:
> Ah, thank you. If I understand correctly, though, once one does that
> (in an SRC org block, say) one looses the ability to edit the block as
> org code using org-edit-special (C-c ').
You can, in development version.
> I understand that the indentation is virtual; it is just that I would
> (ideally) expect for the quoted example to visually look the same as
> it does in an org buffer.
That's not possible.
> OK. I had missed this footnote. I will live with this, but am still
> surprised by this fact -- the SRC org block looks ugly to me. When we
> enter [[xx]] (say) the brackets become invisible, so I had assumed
> that a similar mechanism could exist here; I guess there are
> advantages to the present situation that I do not see...
I am not sure about what situation you're talking about, fontification
or escaping mechanism.
About the latter, the idea was to make it as little intrusive as
possible. In most languages, you never need to escape anything. Of
course, Org is an exception since many lines could conflict with
enclosing document.
Regards,
next prev parent reply other threads:[~2015-05-23 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 22:20 How to elegantly and effectively quote org fragments? Alain.Cochard
2015-05-21 22:02 ` Nicolas Goaziou
2015-05-22 4:37 ` Alain.Cochard
2015-05-23 19:59 ` Nicolas Goaziou [this message]
2015-05-25 8:33 ` Alain.Cochard
2015-06-01 17:20 ` Nicolas Goaziou
2015-05-21 23:31 ` org-notify: can't define an org-notify-add Alain.Cochard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj4vdpzc.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Alain.Cochard@unistra.fr \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.