From: 'Ihor Radchenko' <yantar92@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: org-babel-execute:emacs-lisp does not allow changing window configuration from within code block [9.3 (release_9.3 @ /home/yantar92/.emacs.d/straight/build/org/)]
Date: Fri, 20 Dec 2019 22:59:38 +0800 [thread overview]
Message-ID: <87tv5vt545.fsf@gmail.com> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
Recipe:
1. emacs -Q
2. Create the following org file
#+begin_src emacs-lisp
(split-window-below)
#+end_src
3. Execute the source block
Observed behaviour:
The block returns, but the window is not splitted
Expected behaviour:
The window is splitted
The reason of the observed behaviour is that
org-babel-execute:emacs-lisp wraps the code block evaluation into
save-window-excursion. Thus window manipulation is impossible from
within babel blocks.
The real case scenario when one would need to change window layout from
within babel block is a window setup for a project development.
If certain project requires working with specific window configuration,
this can be defined by adding all the setup into a babel block somewhere
in the project. Then, the layout could be applied just by hitting C-c
C-c on the code block once one need to work on the project. However, it
is not possible with the current org-babel-execute:emacs-lisp
implementation.
Best regards,
Ihor
Emacs : GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.16.0)
of 2019-12-17
Package: Org mode version 9.3 (release_9.3 @ /home/yantar92/.emacs.d/straight/build/org/)
--
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg
next reply other threads:[~2019-12-20 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 14:59 'Ihor Radchenko' [this message]
2020-02-05 8:21 ` Bug: org-babel-execute:emacs-lisp does not allow changing window configuration from within code block [9.3 (release_9.3 @ /home/yantar92/.emacs.d/straight/build/org/)] Bastien
2020-04-08 5:30 ` Ihor Radchenko
2020-09-07 5:38 ` Bastien
2020-09-07 13:11 ` Ihor Radchenko
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=87tv5vt545.fsf@gmail.com \
--to=yantar92@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).