emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Jumping between source blocks in a file
Date: Wed, 02 Dec 2015 11:33:30 +0100	[thread overview]
Message-ID: <m2io4huolh.fsf@krugs.de> (raw)
In-Reply-To: <olubna92na9.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Wed, 02 Dec 2015 09:49:18 +0000")

[-- Attachment #1: Type: text/plain, Size: 2497 bytes --]

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> Rainer M Krug <Rainer@krugs.de> writes:
>> Rainer M Krug <Rainer@krugs.de> writes:
>>
>>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>>
>>>> Hi Andrew,
>>>>
>>>> Martin Yrjölä <martin.yrjola@gmail.com> writes:
>>>>> Hi Andrew!
>>>>>
>>>>> Andrew Kirkpatrick writes:
>>>>>
>>>>>> If this is deemed useful, I'm happy to make changes suitable for
>>>>>> inclusion in the project.
>>>>>
>>>>> Thanks for sharing! I would certainly want these functions included in
>>>>> org-mode by default. They streamline at least my literate programming
>>>>> workflow substantially.
>>>>>
>>>>
>>>> Sorry for joining late.  I too find these useful.
>>>
>>> Absolutely - very useful. Please include!
>>>>
>>>> (Also useful would be the possibility to jump to noweb references
>>>> directly from the src buffer...)
>>>
>>> Very nice idea indeed - or possibly even expand them when executing? But
>>> I think this would be a job for the mode in the source buffer...
>>
>> Actually, expand them when opening the Source Buffer (C-c ') and
>> possibly update them when closing?
>>
>
> This might conflict with open Source Buffers for the referenced code
> block.

True - than simply deliminate them with something like

## <<REF>> BEGIN
...
## <<REF>> END

and *don't* update them at the end?

Probably better: language specific - for R one could write the block to
a temporary file and then insert a =source()= to execute it:


## DO NOT EDIT - AUTO INSERTED - BEGIN
source("<<REF>>.R")
## DO NOT EDIT - AUTO INSERTED - END

Would make debugging much easier, if they would be in the source block
where they are used.

And if no language specific behavior is supplied, use the present
behavior.

>
>>>
>>> At the moment, these noweb references are very nice, but not so nice when
>>> debugging a source block where they are used.
>
> Exactly.

Let's do some brainstorming how this could be solved.

Cheers,

Rainer

>
> Regards,
> Andreas
>
>

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

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

  reply	other threads:[~2015-12-02 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 13:59 Jumping between source blocks in a file Andrew Kirkpatrick
2015-12-02  6:50 ` Martin Yrjölä
2015-12-02  9:07   ` Andreas Leha
2015-12-02  9:38     ` Rainer M Krug
2015-12-02  9:40       ` Rainer M Krug
2015-12-02  9:49         ` Andreas Leha
2015-12-02 10:33           ` Rainer M Krug [this message]
2016-06-25  7:34 ` Xebar Saram

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=m2io4huolh.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=andreas.leha@med.uni-goettingen.de \
    --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).