unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "\"Peter Valdemar Mørch (Lists)\"" <4ux6as402@sneakemail.com>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: C-Home, C-End doesn't work in gnome-terminal - any idea why?
Date: Sat, 24 Oct 2009 12:33:19 +0200	[thread overview]
Message-ID: <4AE2D7EF.3030003@sneakemail.com> (raw)
In-Reply-To: <20091024060033.GA1534@tomas>

tomas-at-tuxteam.de |Lists| wrote:
> I'd guess it's gnome-terminal eating the keystrokes. Try the following
> experiment (on a shell on a Gnome terminal, that is :)
> 
>   hexdump -C
> 
> Then type away at it. You should see a hexdump of your input. Then type
> CTRL-Home. Does hexdump "see" it?

hexdump -C produces output showing the same hex values that my perl 
snippet did in the OP:

gnome-terminal:
^[OH00000000  1b 4f 48                                          |.OH|
00000003
xterm:
^[[1;5H00000000  1b 5b 31 3b 35 48                                 |.[1;5H|
00000006

It doesn't seem that gnome-terminal "eats" the keystrokes, it just 
produces other keystrokes than xterm does.

> Now go to the terminal's menu "Edit->Keyboard Shortcuts". On mine theere
> is a "Disable all menu access keys". This one fixed it for me.

On mine (current ubuntu jaunty - gnome-terminal v. 2.26.0) there are two 
settings under Edit / Keyboard Shortcuts: "Enable menu access keys" and 
"Enable the menu shortcut key". Whether or not they are enabled makes no 
difference.

Thanks for taking the time to post, Thomas.

Peter

-- 
Peter Valdemar Mørch
http://www.morch.com




  reply	other threads:[~2009-10-24 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23  7:31 C-Home, C-End doesn't work in gnome-terminal - any idea why? Peter Valdemar Mørch
2009-10-23 15:21 ` Peter Dyballa
2009-10-23 19:39   ` "Peter Valdemar Mørch (Lists)"
2009-10-24  6:00 ` tomas
2009-10-24 10:33   ` "Peter Valdemar Mørch (Lists)" [this message]
2009-10-26 13:36     ` tomas
     [not found]     ` <mailman.9494.1256563986.2239.help-gnu-emacs@gnu.org>
2009-10-26 21:09       ` dickey
     [not found] <mailman.9325.1256309732.2239.help-gnu-emacs@gnu.org>
2016-08-17  6:40 ` pmorch
  -- strict thread matches above, loose matches on Subject: below --
2009-10-22  9:59 "Peter Valdemar Mørch (Lists)"
2009-10-26  9:47 ` "Peter Valdemar Mørch (Lists)"

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AE2D7EF.3030003@sneakemail.com \
    --to=4ux6as402@sneakemail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tomas@tuxteam.de \
    /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.
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).