From: Julien Barnier <julien@no-log.org>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] [babel] Add option to display process buffer when editing R source code blocks
Date: Tue, 13 Apr 2010 11:46:26 +0200 [thread overview]
Message-ID: <874ojfadn1.fsf@z.nozav.org> (raw)
In-Reply-To: 87d3y94ssd.fsf@stats.ox.ac.uk
Hi Dan,
> Could I suggest a slightly different route? We already have the
> functions org-babel-switch-to-session and org-babel-load-session, which
> work for any language. These switch to the process buffer, like your
> patch does. I agree with you about wanting a function that ends up
> displaying the process buffer and the code edit buffer. I have the
> following personal function which achieves that:
>
> (defun dan/org-babel-switch-to-code-with-session (&optional arg)
> "Switch to code edit buffer and display session"
> (interactive "P")
> (save-excursion
> (org-babel-switch-to-session arg nil))
> (org-edit-src-code))
>
> Could you experiment with these functions, and see if they are
> satisfactory, amd let us know if we can improve things? E.g. we could
> include a function like my one above to display both the session with
> the edit-buffer.
Ah, yes, I didn't notice the existence of
org-babel-switch-to-session. It is indeed much cleaner that my patch
:-)
The "features" I would miss compared top my quick and dirty-function
is the fact that the source code buffer is displayed above the session
one (I really don't like having the session above), the fact that when
I quit the source code editing, the session buffer is closed too, and
the ability to keep org file buffer open with the source and the
session ones.
I can reproduce the behavios I was looking for with the following
modifications to your function. But this is another quick and dirty
hack, and I can't say if it cuold meet the needs of others :
(defun dan/org-babel-switch-to-code-with-session (&optional arg keep-org)
"Switch to code edit buffer and display session. If keep-org is
non nil, keep the org file buffer open, too."
(interactive "P")
(let ((info (org-babel-get-src-block-info)))
(org-edit-src-code)
(if keep-org
(split-window-vertically)
(delete-other-windows))
(save-excursion
(org-babel-switch-to-session arg info))
(other-window -1)))
I think I'll stick with this function for the moment.
> Note that o-b-load-session additionally loads the body of the block into
> the session; and that switch-session, if called with a prefix arg,
> assigns variables from the header args in the session[1]. These are
> bound to M-down and M-up when on a code block.
Ah yes, didn't know these ones either...
> Oh, and also... org-babel-switch-to-session and org-babel-load-session
> use the emacs function pop-to-buffer. That means that there's all sorts
> of extra control you can have over how the windows are displayed. See
> the documentation for things like pop-to-buffer, pop-up-windows,
> split-window-sensibly, special-display-buffer-names, etc.
Yes, I feel I have some more customization opportunities lying in
these documentation pages...
Thanks for your detailed answer !
--
Julien
prev parent reply other threads:[~2010-04-13 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 14:41 [PATCH] [babel] Add option to display process buffer when editing R source code blocks Julien Barnier
2010-04-08 20:02 ` Dan Davison
2010-04-13 9:46 ` Julien Barnier [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874ojfadn1.fsf@z.nozav.org \
--to=julien@no-log.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.