From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jack Kamm <jackkamm@gmail.com>
Cc: emacs-orgmode@gnu.org, Richard Kim <Richard.Kim1@synopsys.com>
Subject: Re: restore window configuration after org-edit-src-exit
Date: Sun, 22 Dec 2019 15:45:22 +0100 [thread overview]
Message-ID: <87lfr45shp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87mubrf2mm.fsf@gmail.com> (Jack Kamm's message of "Tue, 17 Dec 2019 06:28:01 -0800")
Hello,
Jack Kamm <jackkamm@gmail.com> writes:
> Rather than adding a new option, how about we make the behavior
> dependent on the value of org-src-window-setup?
>
> Basically, when org-src-window-setup is current-window, it never makes
> sense to restore the original layout. But when org-src-window-setup is
> reorganize-frame (the default), it always makes sense to restore the
> original layout.
>
> I'm not sure what the "correct" behavior would be for the other options
> however.
I think any value that modifies the current layout ought to restore it:
- `split-window-below'
- `split-window-right'
- `reorganize-frame'
OTOH, values that use the current layout should not restore it
afterwards:
- `current-window'
- `other-window'
- `other-frame'
This should be mentioned in the docstring.
WDYT?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-12-22 14:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 19:06 restore window configuration after org-edit-src-exit Richard Kim
2019-12-16 16:30 ` Nicolas Goaziou
2019-12-17 1:51 ` Kyle Meyer
2019-12-17 14:11 ` Jack Kamm
2019-12-17 14:28 ` Jack Kamm
2019-12-17 15:16 ` Fraga, Eric
2019-12-22 14:45 ` Nicolas Goaziou [this message]
2019-12-23 1:46 ` Jack Kamm
2019-12-23 8:17 ` Nicolas Goaziou
2019-12-23 17:15 ` Jack Kamm
2019-12-23 17:20 ` Nicolas Goaziou
2019-12-23 18:18 ` [PATCH] " Jack Kamm
2020-01-07 8:49 ` Nicolas Goaziou
2020-01-09 15:03 ` Matt Price
2020-01-09 17:43 ` Jack Kamm
2020-01-14 23:10 ` Jack Kamm
-- strict thread matches above, loose matches on Subject: below --
2020-05-17 19:08 edgar
2020-09-05 7:38 ` Bastien
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=87lfr45shp.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Richard.Kim1@synopsys.com \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@gmail.com \
/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).