From: Alain.Cochard@unistra.fr
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org, Alain.Cochard@unistra.fr
Subject: Re: How to elegantly and effectively quote org fragments?
Date: Mon, 25 May 2015 10:33:20 +0200 [thread overview]
Message-ID: <21858.56912.830417.984657@frac.u-strasbg.fr> (raw)
In-Reply-To: <87zj4vdpzc.fsf@nicolasgoaziou.fr>
> > 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.
I understand that now. I'll stay disappointed about it :-)
> > 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.
To the extent that I understand the terminology, I was talking about
escaping mechanism: it would be nice if the escaping commas could be
made invisible and not using any space.
Thanks for the explanations.
a.
next prev parent reply other threads:[~2015-05-25 8:33 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
2015-05-25 8:33 ` Alain.Cochard [this message]
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=21858.56912.830417.984657@frac.u-strasbg.fr \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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.