From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: M-TAB already used by KDE
Date: Tue, 17 Dec 2002 10:19:13 +0100 [thread overview]
Message-ID: <84d6o1ove6.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: 3dfe3ea4.1245206@news.cis.dfn.de
marcel-sl@gmx.de (Marcel Schmittfull) writes:
> I use KDE and therefore the keybinding M-<TAB> is already used for
> switching between windows. Unfortunately there are several emacs modes
> which try to use M-<TAB> for completion (f.e. lisp-mode, AUCTeX, ...).
> However, the KDE setting seems to be "stronger" than the emacs setting
> and hence I can only switch between windows with M-<TAB>.
One possibility is to use C-M-i instead of M-TAB. This is not ideal,
I know. The new KDE is supposed to be able to coexist with Emacs
better, but I find it's still not done, in KDE 3.0 at least.
I've written a little patch for Emacs (which will be in 21.4, whenever
that comes out) that allows you to tell Emacs to swap Alt and Meta.
With that patch, I use it as follows. The keys labeled Alt generate
the Alt_L and Alt_R keysyms, the key(s) with a flag on them generate(s)
Meta_L (and Meta_R). Then KDE sees the Alt keys as Alt and the flag
keys as "Win". Then I can configure the KDE keybindings ("shortcuts")
so that Win-Tab can be used instead of Alt-Tab to switch between
windows. (This is new in KDE 3 I think.)
And also, I tell Emacs to swap Alt and Meta.
Then I can use the keys labeled Alt as Meta keys in Emacs.
To find the patch you can look on savannah.gnu.org for the Emacs CVS
code. The file is src/xterm.c and you can find it by scanning the
logs for my name. This patch can be extracted from CVS and applied to
Emacs 21.2 (I've tested it with the 21.2.93 pretest which I'm
currently using, so I presume it works with 21.2 as well).
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-12-17 9:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 21:12 M-TAB already used by KDE Marcel Schmittfull
2002-12-16 21:13 ` David Kastrup
2002-12-16 21:39 ` Marcel Schmittfull
2002-12-16 21:54 ` Benjamin Lewis
[not found] ` <87bs3l2fgk.fsf@kuntu.zangpo.org>
2002-12-17 10:46 ` Kai Großjohann
[not found] ` <87u1hcyseg.fsf@kuntu.zangpo.org>
2002-12-18 17:35 ` Kai Großjohann
2002-12-17 21:53 ` Benjamin Lewis
2002-12-21 1:11 ` Big Bird
2002-12-18 15:23 ` Marcel Schmittfull
2002-12-18 17:12 ` Kai Großjohann
2002-12-18 18:59 ` asoyeur
2002-12-19 11:00 ` Kester Clegg
2002-12-16 21:32 ` Mark Mynsted
2002-12-16 21:43 ` Marcel Schmittfull
2002-12-17 7:42 ` Roman Belenov
2002-12-17 9:19 ` Kai Großjohann [this message]
2002-12-18 18:29 ` Fredrik Staxeng
2002-12-18 20:26 ` Kai Großjohann
2002-12-18 21:46 ` Fredrik Staxeng
2002-12-19 7:32 ` Kai Großjohann
2002-12-19 11:59 ` Fredrik Staxeng
2002-12-19 14:25 ` Kai Großjohann
2002-12-19 15:36 ` Fredrik Staxeng
2002-12-20 18:42 ` Kai Großjohann
2002-12-20 21:24 ` Fredrik Staxeng
2002-12-20 22:04 ` Benjamin Lewis
2002-12-20 23:29 ` yuan
2002-12-21 12:55 ` Kai Großjohann
2002-12-21 13:57 ` Fredrik Staxeng
2002-12-17 18:02 ` Jochem Huhmann
2002-12-19 13:26 ` Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2002-12-17 18:52 Marcel Schmittfull
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=84d6o1ove6.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.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).