emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: [org] different key binding between GUI emacs and emacs -nw
Date: Wed, 31 May 2017 11:01:26 +0100	[thread overview]
Message-ID: <87y3tdny4p.fsf@t3610> (raw)
In-Reply-To: <08b74f516e674173b7489d0e2e813e83@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Tim Cross's message of "Wed, 31 May 2017 02:38:28 +0000")

[-- Attachment #1: Type: text/plain, Size: 418 bytes --]

On Wednesday, 31 May 2017 at 02:38, Tim Cross wrote:
> I'm sure this has been checked, but make sure it isn't the window
> manager/OS 'stealing' the keys. When I install emacs on any system,

My own experience over the years is that this is indeed usually the
culprit, especially for keys such as M-arrows which are often bound to
functions like changing workspace views.

-- 
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2017-05-31 10:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  6:20 different key binding between GUI emacs and emacs -nw Jean-Christophe Helary
2017-05-30  6:51 ` Nicolas Goaziou
2017-05-30  7:37   ` Jean-Christophe Helary
2017-05-30 12:21     ` Tim Visher
2017-05-30 12:29       ` [org] " Jean-Christophe Helary
2017-05-30 13:29         ` Scott Randby
2017-05-30 16:49           ` Charles C. Berry
2017-05-30 22:28             ` Tim Cross
2017-05-30 22:44               ` Jean-Christophe Helary
2017-05-31  2:38                 ` Tim Cross
2017-05-31  3:51                   ` Jean-Christophe Helary
2017-05-31  6:20                     ` Jean-Christophe Helary
     [not found]                 ` <08b74f516e674173b7489d0e2e813e83@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-05-31 10:01                   ` Eric S Fraga [this message]
2017-05-31 10:19                     ` Jean-Christophe Helary
2017-05-30 13:50         ` Tim Visher

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=87y3tdny4p.fsf@t3610 \
    --to=e.fraga@ucl.ac.uk \
    --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).