emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Greg Minshall <minshall@umich.edu>, emacs-orgmode@gnu.org
Subject: Re: buffer name of Org Src...
Date: Mon, 12 Oct 2020 20:52:41 +0200	[thread overview]
Message-ID: <871ri31dl2.fsf@web.de> (raw)
In-Reply-To: <87362jqtgm.fsf@ucl.ac.uk>

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


Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Monday, 12 Oct 2020 at 18:33, Dr. Arne Babenhauserheide wrote:
>> That’s also when I tangle — but I often don’t move the code back into
>> org afterwards, because once I needed this support once, I know I’ll
>> need it again.
>
> Interesting.  I guess my needs are different: I need these support tools
> when doing the initial code development but not much after
> that.  Subsequently, most of my time is spent with documentation,
> dissemination, and bug fixes.  Doing most of this is easier in org mode.

Do you use org-mode to document stuff after you wrote it?

I often use it to start small tools that I need right now — for example
some data extraction — and I would prefer to keep them in org, because I
then have one single reference. And I often write the code while I’m
writing the text around it. When then something does not work, I need
debugging and exploration to find out how to fix it.

> But whatever works best for you is what you should do!

There are a lot of great ways to use org-mode :-)

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

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

  reply	other threads:[~2020-10-12 18:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 12:44 buffer name of Org Src Greg Minshall
2020-10-12 13:18 ` Eric S Fraga
2020-10-12 14:17   ` Greg Minshall
2020-10-12 14:31     ` Eric S Fraga
2020-10-13  6:27       ` Greg Minshall
2020-10-13  7:52         ` Eric S Fraga
2020-10-13  9:01           ` Dr. Arne Babenhauserheide
2020-10-13 10:40             ` Eric S Fraga
2020-10-12 13:39 ` Dr. Arne Babenhauserheide
2020-10-12 14:04   ` Greg Minshall
2020-10-12 14:11   ` Eric S Fraga
2020-10-12 16:33     ` Dr. Arne Babenhauserheide
2020-10-12 16:50       ` Eric S Fraga
2020-10-12 18:52         ` Dr. Arne Babenhauserheide [this message]
2020-10-13  7:51           ` Eric S Fraga

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=871ri31dl2.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \
    /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).