From: Nicolas Goaziou <email@example.com>
To: Puneeth Chaganti <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: Bug: header-args:C++ doesn't work
Date: Sat, 06 Dec 2014 00:42:25 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CALnw1fTw1ivaUXodHM1wELkaGa+OGq95tM+cWUJsrfrbS5N3qg@mail.gmail.com> (Puneeth Chaganti's message of "Fri, 5 Dec 2014 00:10:54 +0530")
Puneeth Chaganti <email@example.com> writes:
> I was helping out "ablephar`" on IRC and they found that setting a
> file property `header-args:C++` does not work.
> After some edebug magic, I discovered that org has a feature that lets
> you append property values! (Not the best way to discover a great
> feature, I must say! :-)
> The fix could either be a documentation fix. (I would've tried using
> cpp instead of C++, if I knew that was supported). But, this would
> still have some users seeing things broken and then looking up docs or
> trying out the alternative.
> a "hacky" fix, (better for the users ?), could be to consider KEY+ to
> be indicating appending, but KEY++ to not. Thoughts?
I prefer the former. Forbidding to end properties with "+" (unless we
are appending a value) is, IMO, a bearable restriction.
prev parent reply other threads:[~2014-12-05 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 18:40 Bug: header-args:C++ doesn't work Puneeth Chaganti
2014-12-05 23:42 ` Nicolas Goaziou [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).