From: Rainer M Krug <Rainer@krugs.de>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH]: Add header-args property to source block info
Date: Tue, 10 Feb 2015 21:54:25 +0100 [thread overview]
Message-ID: <m261b9ebcu.fsf@krugs.de> (raw)
In-Reply-To: <alpine.OSX.2.00.1502100943290.583@charles-berrys-macbook.local> (Charles C. Berry's message of "Tue, 10 Feb 2015 09:58:28 -0800")
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
"Charles C. Berry" <ccberry@ucsd.edu> writes:
> On Tue, 10 Feb 2015, Rainer M Krug wrote:
>
>> Hi
>>
>> Following a recent discussion (based on me forgetting a ":" when setting
>> the property :header-args), I added the output of the property
>> header-args to the output of org-babel-get-src-block-info to make
>> debugging easier.
> [snip]
>>
>> Using the patched version, one gets the following:
>>
>> ,----
>> | Lang: R
>> | Properties:
>> | :header-args :exports both :results output exports code
>> | :header-args:R :session somename
>> | Header Arguments:
>> | :cache no
>> | :exports both
>> | :hlines no
>> | :noweb no
>> | :results code exports output replace
>> | :session somename
>> | :tangle no
>> `----
>>
>
> This is handy!
>
> Just a thought:
>
> Perhaps allow an `(interactive "P)' type `arg' to determine whether to
> present the properties?
>
> i.e. C-u C-c C-v C-i reveals both Properties: and Header Arguments:, while
> C-c C-v C-i just the latter.
Apart from having no idea how I can do this, I think it would add just
another layer of complexity which is actually not needed as this is just
an information to be assessed visually and not to be parsed by some
code - so I do not assume there are any backward compatibility issues.
Also, as the information presented is only relative small (20 lines
max?) it is still quite easy to see the original information.
If the patch would strip away information or add a huge amount of it, I
would completely agree with your suggestion, but as it stands, I see no
harm in leaving it as it is in the patch.
Cheers,
Rainer
>
> Best,
>
> Chuck
>
>
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
prev parent reply other threads:[~2015-02-10 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 9:09 [PATCH]: Add header-args property to source block info Rainer M Krug
2015-02-10 13:39 ` [PATCH]: BUG fix and " Rainer M Krug
2015-02-10 21:36 ` Nicolas Goaziou
2015-02-10 21:58 ` Rainer M Krug
2015-02-11 12:10 ` Alan Schmitt
2015-02-12 9:34 ` Rainer M Krug
2015-02-12 9:36 ` Rainer M Krug
2015-02-12 18:27 ` Charles C. Berry
2015-02-12 23:45 ` Nicolas Goaziou
2015-02-13 9:21 ` Rainer M Krug
2015-02-13 9:36 ` Sebastien Vauban
2015-02-13 9:51 ` Rainer M Krug
2015-02-10 17:58 ` [PATCH]: " Charles C. Berry
2015-02-10 20:54 ` Rainer M Krug [this message]
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=m261b9ebcu.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=ccberry@ucsd.edu \
--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).