From: Grant Rettke <gcr@wisdomandwonder.com>
To: Adriaan Sticker <adriaan.sticker@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: meaningfull names for org-src buffers
Date: Sun, 21 Sep 2014 08:49:04 -0500 [thread overview]
Message-ID: <CAAjq1mezbQ_cOm11nQwo6xVHsTcc9cC0sMj56nZyLSaRJU=-Pw@mail.gmail.com> (raw)
In-Reply-To: <CAOrF+NyjMws6uQRWfVweGV8RigPHcLEVd7=m7_rjsxYbniAO-w@mail.gmail.com>
On Thu, Sep 11, 2014 at 5:05 PM, Adriaan Sticker
<adriaan.sticker@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?
--
Grant Rettke
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
next prev parent reply other threads:[~2014-09-21 13:49 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 [this message]
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
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='CAAjq1mezbQ_cOm11nQwo6xVHsTcc9cC0sMj56nZyLSaRJU=-Pw@mail.gmail.com' \
--to=gcr@wisdomandwonder.com \
--cc=adriaan.sticker@gmail.com \
--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).