unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: barbier@linuxfr.org (Denis Barbier)
Subject: Re: Xfree86 and the Meta key (+patch)
Date: Tue, 5 Oct 2004 07:53:35 +0200	[thread overview]
Message-ID: <20041005055334.GA1138@linuxfr.org> (raw)
In-Reply-To: <94C3F12E-1658-11D9-84C1-000D93505B76@swipnet.se>

On Tue, Oct 05, 2004 at 12:56:09AM +0200, Jan D. wrote:
> >As shortcuts cannot work if a modifier is bound to different symbols,
> >another solution is to let emacs handle this case in a smarter way.
> >This is the purpose of the patch sent by Jerome; when a modifier is
> >bound to different symbols, only one is taken into account.  There is 
> >no
> >change for working configurations, and many configurations which are
> >currently broken will work out of the box without having to run 
> >xmodmap.
> 
> I am testing the patch and something like it will be checked in.  But
> it would be nicer if Emacs could determine that Hyper and Super
> is bound to fake keys and just ignore them.  I'm currently using XKB
> to get geometry info to determine that, but I wonder if there is a 
> better way.  The reason I want this is that with the proposed patch
> the logo key becomes Super on my system, which is not really helpful
> either.

Can you please tell me what your configuration is?  I am quite surprised
that it does not work as expected, doesn't xev also report that your
logo key is Super_{L,R}?

> If we could determine that Super is a fake key it would become Meta
> which is so much better.

Fake keys have no symbol at level 0, so before the
  for (code_col = 0; code_col < syms_per_code; code_col++)
loop, you can test whether
  syms[((code - min_code) * syms_per_code)] == NoSymbol
and skip this key in this case.
I did not want to go this way because it is XFree86-centric, the other
solution is more generic.

Denis

  reply	other threads:[~2004-10-05  5:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 21:30 Xfree86 and the Meta key (+patch) Denis Barbier
2004-10-04 22:56 ` Jan D.
2004-10-05  5:53   ` Denis Barbier [this message]
2004-10-05 10:43     ` Jan D.
2004-10-05 19:50       ` Denis Barbier
  -- strict thread matches above, loose matches on Subject: below --
2004-10-04  0:08 Jan D.
     [not found] <20041003233940.JVGC27821.mxfep02.bredband.com@coolsville.localdomain>
2004-10-03 23:52 ` Andreas Schwab
2004-10-01 21:00 Jérôme Marant
2004-10-02 23:06 ` Kim F. Storm
2004-10-03  7:34   ` Jérôme Marant
2004-10-04 15:18     ` Richard Stallman
2004-10-04 15:55       ` Jérôme Marant
2004-10-05 18:05         ` Richard Stallman
2004-10-05 21:07           ` Jérôme Marant
2004-10-05 21:15             ` Jan D.
2004-10-03  8:11   ` Frank Schmitt
2004-10-03 12:00     ` Jan D.
2004-10-03 17:54       ` Andreas Schwab
2004-10-03 19:10         ` Jérôme Marant
2004-10-03 21:07           ` Andreas Schwab
2004-10-03 21:52           ` Jan D.
2004-10-03 22:48             ` Andreas Schwab

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=20041005055334.GA1138@linuxfr.org \
    --to=barbier@linuxfr.org \
    --cc=emacs-devel@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.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).