From: Tom Gillespie <tgbugs@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-src: Add option to restore window configuration after edit
Date: Sun, 16 Feb 2020 21:27:56 -0800 [thread overview]
Message-ID: <CA+G3_PNLUzV9vugGv5ozW547fwNv14E3Ly5YuPR7nqynTR3HtQ@mail.gmail.com> (raw)
In-Reply-To: <87blpxq26b.fsf@kyleam.com>
Hi Kyle,
Thank you for the pointer. That does indeed solve my issue. I must
have missed it because it wasn't merged into maint. The conversation
in that thread seems to indicate that the old behavior is the correct
default. I imagine that there might be a few other folks with Matt's
use case, but I guess that can wait. Thus, definitely ok to ignore
this patch. Best!
Tom
On Sun, Feb 16, 2020 at 8:16 PM Kyle Meyer <kyle@kyleam.com> wrote:
>
> Hi Tom,
>
> Tom Gillespie <tgbugs@gmail.com> writes:
>
> > Hi all,
> > After hours of frustration ending in a realization that I should really
> > just read the change logs, I tracked down the reason why editing
> > source blocks was now destroying my window layout. I restored the
> > old behavior hidden behind a custom variable. Let me know if it looks
> > ok, or if more work is needed. Thanks!
>
> I haven't looked at your proposed change closely, but I think this is
> the same issue that was reported recently [0] and fixed by d833920de
> (org-src: restore windows for some values of org-src-window-setup,
> 2019-12-23). If you have a chance, please check whether that commit
> resolves the issue for you.
>
> [0]: https://lists.gnu.org/archive/html/emacs-orgmode/2019-12/msg00263.html
prev parent reply other threads:[~2020-02-17 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 3:50 [PATCH] org-src: Add option to restore window configuration after edit Tom Gillespie
2020-02-17 4:15 ` Kyle Meyer
2020-02-17 5:27 ` Tom Gillespie [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
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=CA+G3_PNLUzV9vugGv5ozW547fwNv14E3Ly5YuPR7nqynTR3HtQ@mail.gmail.com \
--to=tgbugs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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).