all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Christoph-Simon Senjak <christoph.senjak@googlemail.com>,
	22617-done@debbugs.gnu.org
Subject: bug#22617: 24.4; AltGr not working after Xmodmap
Date: Thu, 16 Jan 2020 15:20:10 +0100	[thread overview]
Message-ID: <87zhenwkit.fsf@marxist.se> (raw)
In-Reply-To: <87a7ctm4h5.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Thu, 01 Aug 2019 14:53:42 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Christoph-Simon Senjak <christoph.senjak@googlemail.com> writes:
>
>>  I have the following .Xmodmap:
>>
>>     keycode 135 = Alt_L
>>     keycode 167 = Page_Down
>>     keycode 166 = Page_Up
>>     remove mod4 = Super_L
>>     add    mod5 = Super_L
>>
>>  Otherwise, my keymap is
>>
>>     de nodeadkeys compose:caps
>>
>>  Since the .Xmodmap, I cannot type in stuff that requires AltGr
>> anymore (even
>>  though I did not even remap it). Even with the new mod5 key it doesn't
>>  work. (For example, AltGr+q is (at), and AltGr+7,8,9,0 are braces.
>>
>>  In all other applications (including emacs -nw), it works well.
>
> (I'm going through old bug reports that have unfortunately not gotten
> any responses.)
>
> Are you still seeing this problem?  There doesn't seem to be anything
> particular in your .Xmodmap that references AltGr...  unless your
> Mode_switch was on mod5, and this made something confused.
>
> What's the output from "xmodmap" (without any parameters)?

More information was requested, but none was given within 24 weeks, so I'm
closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.

Best regards,
Stefan Kangas





      reply	other threads:[~2020-01-16 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 13:53 bug#22617: 24.4; AltGr not working after Xmodmap Christoph-Simon Senjak
2019-08-01 12:53 ` Lars Ingebrigtsen
2020-01-16 14:20   ` Stefan Kangas [this message]

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

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

  git send-email \
    --in-reply-to=87zhenwkit.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=22617-done@debbugs.gnu.org \
    --cc=christoph.senjak@googlemail.com \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.