From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Leo Alekseyev <dnquark@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-edit-special and C-x C-s strange behavior
Date: Wed, 11 Jan 2012 15:16:52 +0000 [thread overview]
Message-ID: <87pqeqb76j.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CADzxs1=g43H9NsZ=Z-apPuvLDKG0-V781i_0Bt159Y5XFZmJzg@mail.gmail.com> (Leo Alekseyev's message of "Wed, 11 Jan 2012 00:40:13 -0600")
Leo Alekseyev <dnquark@gmail.com> writes:
> 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
[...]
What version of org are you using? I ask because I used to experience
the annoyance you describe a while back; more recently (since at least a
few months ago), hitting C-x C-s no longer has any negative impact: it
saves the file, or at least appears to.
You still have to C-c ' to get back to the full buffer, mind you, but
that's better, IMO, than changing the behaviour of such a fundamental
key binding as C-x C-s.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.8.03 (release_7.8.03.76.ga9c15)
next prev parent reply other threads:[~2012-01-11 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 6:40 Org-edit-special and C-x C-s strange behavior Leo Alekseyev
2012-01-11 15:16 ` Eric S Fraga [this message]
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=87pqeqb76j.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=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).