From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Martin Carlé" <mc@aiguphonie.com>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>, emacs-orgmode@gnu.org
Subject: Re: Org Babel resolution of `:var` value reference inconsistent
Date: Thu, 05 Nov 2015 15:48:35 +0100 [thread overview]
Message-ID: <87io5go62k.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m1d1vosiyn.fsf@aiguphonie.com> ("Martin \=\?utf-8\?Q\?Carl\=C3\=A9\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Thu, 05 Nov 2015 14:56:32 +0200")
Hello,
Martin Carlé <mc@aiguphonie.com> writes:
> On 2015-11-04 Wed 14:14, Andreas Leha wrote:
>
>> ,---------------------------------------------------------------------------
>> | > I'd say it is a bug if the results from evaluation differ between
>> | > manual evaluation and during export.
>> | >
>> | > And even if it is not explicitely contradicting the manual [1] (which
>> | > does not say anything about finding references), I'd prefer if
>> | > references in COMMENT'ed sections are not found -- neither during export
>> | > nor during evaluation. This would be more inline with my intuition of
>> | > COMMENT is equivalent to # (which is also suggested by the fact that
>> | > COMMENT is described in the section on #).
>> `---------------------------------------------------------------------------
>
> I'd like to strongly support this view.
Fixed, in master (02c78501472fba94f8cf5a3d218b5c8845b28827).
Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-11-05 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 7:40 Org Babel resolution of `:var` value reference inconsistent myq
2015-11-02 9:01 ` Andreas Leha
2015-11-02 13:19 ` Nick Dokos
2015-11-04 12:14 ` Andreas Leha
2015-11-05 12:56 ` Martin Carlé
2015-11-05 14:48 ` Nicolas Goaziou [this message]
2015-11-05 20:53 ` Andreas Leha
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=87io5go62k.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
--cc=mc@aiguphonie.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).