emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Grant Rettke <gcr@wisdomandwonder.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Naming of (indirect?) buffers opened by C-'
Date: Thu, 18 Dec 2014 20:30:00 -0600	[thread overview]
Message-ID: <CAAjq1meb1SOFuXJCs4U+uCAGGuu_pLn8fh2UxOpiQ9pT4KHoyg@mail.gmail.com> (raw)
In-Reply-To: <m2h9wtkysu.fsf@krugs.de>

(defun gcr/org-edit-src-code-plus-name ()
  "Edit the well-described source code block.

Attribution: URL
`https://lists.gnu.org/archive/html/emacs-orgmode/2014-09/msg00778.html'"
  (interactive)
  (let* ((eop  (org-element-at-point))
         (name (or (org-element-property :name (org-element-context eop))
                  "ॐ"))
         (lang (org-element-property :language eop))
         (buff-name (concat "*Org Src " name "[" lang "]*")))
    (org-edit-src-code nil nil buff-name)))

On Thu, Dec 18, 2014 at 5:00 AM, Rainer M Krug <Rainer@krugs.de> wrote:
> Hi
>
> I remember there was a discussion recently about the naming of the
> indirect buffers of source code block opened with C-' but I can't find
> it at the moment. Was there a solution on giving these buffers a
> useful name, i.e. the name of the code block?
>
> If this is included in org, it does not seem to be working for me?
>
> Thanks,
>
> Rainer
>
> --
> Rainer M. Krug
> email: Rainer<at>krugs<dot>de
> PGP: 0x0F52F982



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

  reply	other threads:[~2014-12-19  2:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 11:00 Naming of (indirect?) buffers opened by C-' Rainer M Krug
2014-12-19  2:30 ` Grant Rettke [this message]
2014-12-19  9:53   ` Rainer M Krug
2014-12-19 10:00     ` KEybinding for " 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=CAAjq1meb1SOFuXJCs4U+uCAGGuu_pLn8fh2UxOpiQ9pT4KHoyg@mail.gmail.com \
    --to=gcr@wisdomandwonder.com \
    --cc=Rainer@krugs.de \
    --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).