From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: Re: meaningfull names for org-src buffers
Date: Thu, 25 Sep 2014 19:55:45 +0000 (UTC) [thread overview]
Message-ID: <loom.20140925T214649-80@post.gmane.org> (raw)
In-Reply-To: olud2akufye.fsf@med.uni-goettingen.de
Andreas Leha <andreas.leha <at> med.uni-goettingen.de> writes:
>
> Hi,
>
> Grant Rettke <gcr <at> wisdomandwonder.com> writes:
> > On Thu, Sep 11, 2014 at 5:05 PM, Adriaan Sticker
> > <adriaan.sticker <at> gmail.com> wrote:
> >> I was wondering if it's somehow possible to give named org src buffer the
> >> name they were give in their #+NAME tag? Now there are just called
> >> something like:
> >> *Org Src test.org[ R ]*
> >>
> >> But if you have multiple org-src buffers opened at the same time, its
> >> hard to find the correct one back.
> >
> > Excellent idea. I've got so many small source blocks that it is too
> > difficult to make sense of
> > keeping multiple source block edit buffers open and limit them to one
> > at a time eg
> >
> > ,----
> > | (setq org-src-window-setup 'current-window)
> > `----
> >
> > How have you come upon your workflow of keeping multiple open and what
> > are some of the pros and
> > cons that you've found with it?
>
> I'd be interested in this as well.
>
> Regards,
> Andreas
>
>
Maybe I am answering the wrong question, but org-edit-src-code allows
you to specify the buffer name:
,----[ C-h f org-edit-src-code RET ]
| org-edit-src-code is an interactive compiled Lisp function in
| `org-src.el'.
|
| (org-edit-src-code &optional CONTEXT CODE EDIT-BUFFER-NAME)
|
| ...
`----
So you can do something like this:
#+BEGIN_SRC emacs-lisp
(defun org-edit-src-code-plus-name ()
(interactive)
(let* ((eop (org-element-at-point))
(name (or (org-element-property :name (org-element-context eop))
"unnamed"))
(lang (org-element-property :language eop))
(buff-name (concat "*Org Src " name "[ " lang " ] *")))
(org-edit-src-code nil nil buff-name)))
#+END_SRC
which leads to a buffer named like "*Org Src My-block[ R ] *", where
'My-block' is the name of the src block.
HTH,
Chuck
next prev parent reply other threads:[~2014-09-25 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 22:05 meaningfull names for org-src buffers Adriaan Sticker
2014-09-21 13:49 ` Grant Rettke
2014-09-21 15:07 ` Adriaan Sticker
2014-09-21 15:51 ` Grant Rettke
2014-09-25 10:54 ` Andreas Leha
2014-09-25 10:55 ` Andreas Leha
2014-09-25 19:55 ` Charles Berry [this message]
2014-09-25 20:22 ` Andreas Leha
2014-09-26 6:33 ` Rainer M Krug
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=loom.20140925T214649-80@post.gmane.org \
--to=ccberry@ucsd.edu \
--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).