From: "Jan Djärv" <jan.h.d@swipnet.se>
To: James Cloos <cloos@jhcloos.com>
Cc: "14044@debbugs.gnu.org" <14044@debbugs.gnu.org>,
"Alexandre Lagüe-Jacques" <alexandre.laguejacques@gmail.com>,
"Andreas Schwab" <schwab@linux-m68k.org>,
"Tassilo Horn" <tsdh@gnu.org>
Subject: bug#14044: 24.2; Emacs 24 and dead keys in Fedora 18
Date: Fri, 26 Apr 2013 23:28:19 +0200 [thread overview]
Message-ID: <20F3A54C-B254-4B0E-B6B0-3E7F5B9ED9F2@swipnet.se> (raw)
In-Reply-To: <m3mwsldo5k.fsf@carbon.jhcloos.org>
Hello.
26 apr 2013 kl. 22:36 skrev James Cloos <cloos@jhcloos.com>:
>>>>>> "AS" == Andreas Schwab <schwab@linux-m68k.org> writes:
>
> AS> Tassilo Horn <tsdh@gnu.org> writes:
>>> I also can't insert ` anymore, except with `M-x ucs-insert GRAVE ACCENT
>>> RET'. Typing ` (which is AltGr+< on my German Dvorak layout) messages
>>> just
>>>
>>> <dead-grave> is undefined
>
> AS> Your keyboard is misconfigured. Your X server should have a compose
> AS> rule that composes the dead_grave keysym
>
> If one uses the gtk compile of Emacs; then it may be Gnome's input
> rules rather than X11's. (I don't use gtk Emacs, but my tests show
> that other gtk apps use the gtk/gnome IMs even when compiled without
> libgnome or other gnome-specific support libs.)
Gtk+ has its own input processing, but Emacs does not use it. Emacs compiled for X11, regardless of toolkit use the same code, raw Xlib or Xim.
Jan D.
prev parent reply other threads:[~2013-04-26 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 19:47 bug#14044: 24.2; Emacs 24 and dead keys in Fedora 18 Alexandre Lagüe-Jacques
2013-03-30 17:25 ` Stefan Monnier
2013-04-24 19:13 ` Stefan Monnier
2013-04-25 18:25 ` Tassilo Horn
2013-04-26 8:58 ` Andreas Schwab
2013-04-26 10:15 ` Tassilo Horn
2013-04-26 10:25 ` Tassilo Horn
2013-04-26 13:53 ` Tassilo Horn
2013-04-26 20:36 ` James Cloos
2013-04-26 21:28 ` Jan Djärv [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
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=20F3A54C-B254-4B0E-B6B0-3E7F5B9ED9F2@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=14044@debbugs.gnu.org \
--cc=alexandre.laguejacques@gmail.com \
--cc=cloos@jhcloos.com \
--cc=schwab@linux-m68k.org \
--cc=tsdh@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).