From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: org-forward-element looses selection on code blocks
Date: Wed, 24 Jul 2013 17:35:54 +0200 [thread overview]
Message-ID: <8738r455t1.fsf@gmail.com> (raw)
In-Reply-To: <86y58wvx4y.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 24 Jul 2013 16:41:01 +0200")
Hello,
"Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:
> Up to quite recently, I could select ("region") code blocks or multiple
> consecutive paragraphs by pressing <C-down> which ran `forward-paragraph'.
>
> Now that <C-down> is mapped to `org-forward-element':
>
> - I can't select any code block anymore via <C-down> (well line by line with
> <down>).
> - I can't select consecutive paragraphs from following subtrees.
This second item is inherent to the structure of the document. You can
use `org-down-element' to move into the next subtree.
> Is there a plan to fix it in `org-forward-element' (IOW, do we consider that
> as a bug or a feature, or not at all?), or must I remap <C-down> back to its
> old command?
I don't think the bug comes from `org-forward-element'.
If you use C-space in the middle of the block and then M-x
org-forward-element, the block will be marked. If you do the same with
C-<down> instead of M-x org-forward-element, it will not be marked.
There is a similar problem with `org-end-of-line' (it will lose region
if called through C-e, but not with M-x org-end-of-line), also on source
blocks.
I don't know the root of this evil.
Anyhow, you can remap <C-down> to whatever suits you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2013-07-24 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 14:41 org-forward-element looses selection on code blocks Sebastien Vauban
2013-07-24 15:35 ` Nicolas Goaziou [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=8738r455t1.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.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).