emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: C-S-up and C-S-down throws an error
Date: Wed, 16 Oct 2013 14:01:26 +0200	[thread overview]
Message-ID: <87bo2pctm1.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: CAA01p3pTou3j8ZkOvnwEmgzm4yVdmWApEcXkD6xokTqeNzhj7w@mail.gmail.com

Hi Oleh,

really great timing!  I was just hit by this as well and along comes
your message.

Oleh <ohwoeowho@gmail.com> writes:

> Hi all,
>
> Pressing these key-chords just gives:
>
> user-error: To use shift-selection with Org-mode, customize
> `org-support-shift-select'
>
> I don't think that it's very productive to occupy a key binding with a
> function that 
> just says to me that I made an error. Or is it an advertisement for
> shift-selection:)?

I agree here.

>
> I've got global windmove bindings on C- arrows, and buffer-move on
> C-S- arrows,
> so now I have to set specifically:
>
> (define-key org-mode-map [(control shift right)] nil)
> (define-key org-mode-map [(control shift left)] nil)
> (define-key org-mode-map [(control shift up)] nil)
> (define-key org-mode-map [(control shift down)] nil)
>

Thanks for sharing that.  I am using that right now as well.

> I don't feel bad about the other two bindings, because they were
> actually doing something
> useful, but these two...
>
> I think a way out of this is either enabling
> `org-support-shift-select' by default,
> or not to bind these key chords. But that's just my opinion.

Since it can be circumvented quiet easily I do not have a (too) strong
aversion against these binding any more.   But I agree that these
binding are useless and, thus, should not be set by default.

Regards,
Andreas

next prev parent reply	other threads:[~2013-10-16 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 15:19 C-S-up and C-S-down throws an error Oleh
2013-10-16 12:01 ` Andreas Leha [this message]
2013-11-05 17:22 ` 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=87bo2pctm1.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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

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).