emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Minshall <minshall@umich.edu>
To: emacs-orgmode@gnu.org
Subject: buffer name of Org Src...
Date: Mon, 12 Oct 2020 15:44:41 +0300	[thread overview]
Message-ID: <1419444.1602506681@apollo2.minshall.org> (raw)

hi, all.

i often write my version of (il)literate programs using one .org file,
from which four or five (typically) files are tangled.  and, generally,
i'm very happy with this.

but, when i have multiple Org Src ... buffers open, all from the same
language, i am at a loss on how to determine to which buffer i should
'C-x b', as the only distinguishing characteristic is a (possible)
trailing '<N>', for some small integer N.

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.

is there a way to customize the buffer name?  or, an easy hack?  (given
a choice, i'd probably have some function of [src block name; language;
tangled-to file name], prefixed, clearly, by Org Src... and optionally
suffixed with "<N>".)

cheers, Greg

ps -- in case it's of interest: possibly i'm frustrated now, and wasn't
so much in the past, as i recently got annoyed by having to go back to
the base file to save and tangle (part of my work flow, to test whatever
i'm working on), and, so, wrote a few lines of emacs lisp so that a 'C-x
s' save from the Org Src ... file causes a save of the base file
followed by a tangle.  so, i can basically live long periods of time
just in the Org Src ... buffers; if only i could find my way around.

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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 12:44 Greg Minshall [this message]
2020-10-12 13:18 ` buffer name of Org Src 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
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:

  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=1419444.1602506681@apollo2.minshall.org \
    --to=minshall@umich.edu \
    --cc=emacs-orgmode@gnu.org \


* 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


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).