From: Leo Alekseyev <dnquark@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Org-edit-special and C-x C-s strange behavior
Date: Wed, 11 Jan 2012 00:40:13 -0600 [thread overview]
Message-ID: <CADzxs1=g43H9NsZ=Z-apPuvLDKG0-V781i_0Bt159Y5XFZmJzg@mail.gmail.com> (raw)
I often edit my org-babel code blocks via org-edit-special (C-'), in
part because I find the tabbing behavior within the code blocks to be
somewhat flaky. Inevitably, when editing the code block I will press
C-x C-s (muscle memory). This causes all sorts of annoying
consequences: the buffer with the code block gets buried, window
splitting disappears, and if I go back to the original org buffer,
find the relevant code block and try to edit again via C-', I'm faced
with a rather cryptic message "Return to existing edit buffer? [n]
will revert changes: (y or n) ".
Since C-x C-s is such a basic operation, I think it should do
something more sensible in an edit buffer (for instance, it should
save the original org document and not screw with the window
configuration). Alternatively, it could be configured to save, and
exit the edit buffer (i.e. simulate the effect of pressing C-' and
then C-x C-s in the original org buffer). This would go a long way to
making working with code blocks more pleasant. From my viewpoint /
usage patterns it makes a lot of sense for an edit buffer to behave
like a version of the original org buffer narrowed to the source code
block. If there's a particular reason for the current behavior, I'd be
very curious to know it.
--Leo
next reply other threads:[~2012-01-11 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 6:40 Leo Alekseyev [this message]
2012-01-11 15:16 ` Org-edit-special and C-x C-s strange behavior Eric S Fraga
2012-01-11 20:56 ` Andreas Leha
2012-01-12 1:40 ` Leo Alekseyev
2012-01-12 4:56 ` Leo Alekseyev
2012-01-12 9:03 ` Eric S Fraga
2012-01-12 10:14 ` Andreas Leha
2012-01-12 13:55 ` Leo Alekseyev
[not found] ` <30ae09b29d262e6156ec9818df085441@mail.rickster.com>
2012-01-13 20:58 ` Leo Alekseyev
2012-01-24 15:25 ` Bastien
2012-02-08 21:50 ` Leo Alekseyev
2012-02-14 22:37 ` Andreas Leha
2012-02-14 23:02 ` Andreas Leha
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='CADzxs1=g43H9NsZ=Z-apPuvLDKG0-V781i_0Bt159Y5XFZmJzg@mail.gmail.com' \
--to=dnquark@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).