From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: buffer name of Org Src...
Date: Mon, 12 Oct 2020 14:18:46 +0100 [thread overview]
Message-ID: <87k0vvr39l.fsf@ucl.ac.uk> (raw)
In-Reply-To: <1419444.1602506681@apollo2.minshall.org> (Greg Minshall's message of "Mon, 12 Oct 2020 15:44:41 +0300")
On Monday, 12 Oct 2020 at 15:44, Greg Minshall wrote:
> in *my* case (with the project i'm currently working on), each source
> block in the .org file is a separately tangled file, and each source
> block could be tagged with a distinct '#+name:' value.
Using the name of the src block would be a nice enhancement.
> ps -- in case it's of interest: possibly i'm frustrated now, and wasn't
I understand your frustration but I've found the solution that works in
my case, when tangling a large number of blocks all to the same code
file. The solution is to work on the code file directly, having tangled
with :comments on, and then detangle (org-bable-detangle) to get the src
blocks back in the original org file. I do this particularly in the
early stages of code development when I'm continually running and
editing the code.
HTH,
eric
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4-57-g8402c4
next prev parent reply other threads:[~2020-10-12 13:19 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 [this message]
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
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=87k0vvr39l.fsf@ucl.ac.uk \
--to=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).