emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <r.m.krug@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-babel-tangle-w-comments has no effect in R?
Date: Sat, 3 Jul 2010 20:34:15 +0200	[thread overview]
Message-ID: <AANLkTilFhpzff4MBXZU2KZCEJg6bMuKBlvCLOLS-X1WE@mail.gmail.com> (raw)
In-Reply-To: <87bpapwqaj.fsf@gmail.com>

Hi Eric

On Friday, July 2, 2010, Eric Schulte <schulte.eric@gmail.com> wrote:
> Hi Rainer,
>
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
> [...]
>>>
>>> I think that moving forward it might make sense to remove the
>>> org-babel-tangle-w-comments variable, as it's confusing to have two
>>> points of control for comments during tangling.  Also, it looks like I
>>> need to add the :comments header argument to the babel documentation.
>>>
>>
>> Both points agreed.
>>
>
> Great, I'll put together a patch removing this variable.

Great.

>
>>
>> In addition: is it possible to customize the format for all comments
>> (on a per file basis and / or a per block basis)? i.e. I don't need
>> the file name, as all blocks are coming from one file. I know about
>>
>>   #+srcname: <name>
>>
>> but is there a variable for the line number (I guess that is covered by the
>> request posted in another thread) one could use?
>>
>
> We could very easily introduce a customizable
> `org-babel-tangle-comment-format-string', in fact I think this would be
> a very good idea.

Yes -  that would make the comment feature much more useful.

>
>>
>> Also, would it be possible to include a link in the comment block, so
>> that clicking on that link actually opens the org-file file at the
>> location of the source block? That would make editing the code really
>> easy.
>>
>
> That was the goal of the current comment syntax, unfortunately I don't
> know of a good way to activate Org-mode style links in the comments of
> source code files.  Rest assured once that feature exists (and I know
> about it) we'll have such links.

Sound great. That would actually make it perfect.

Cheers,

Rainer

>
> Best -- Eric
>

-- 
NEW GERMAN FAX NUMBER!!!

Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Cell:           +27 - (0)83 9479 042
Fax:            +27 - (0)86 516 2782
Fax:            +49 - (0)321 2125 2244
email:          Rainer@krugs.de

Skype:          RMkrug
Google:         R.M.Krug@gmail.com

      reply	other threads:[~2010-07-03 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01  7:27 org-babel-tangle-w-comments has no effect in R? Rainer M Krug
2010-07-01 15:41 ` Eric Schulte
2010-07-02  7:22   ` Rainer M Krug
2010-07-02 21:02     ` Eric Schulte
2010-07-03 18:34       ` 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=AANLkTilFhpzff4MBXZU2KZCEJg6bMuKBlvCLOLS-X1WE@mail.gmail.com \
    --to=r.m.krug@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.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).