From: Ian D. Leroux <idleroux@fastmail.fm>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 7380@debbugs.gnu.org
Subject: bug#7380: 23.2; Dead keys misinterpreted in gtk emacs
Date: Sat, 20 Nov 2010 19:31:58 -0500 [thread overview]
Message-ID: <878w0ntt35.wl%idleroux@fastmail.fm> (raw)
In-Reply-To: <jwvd3q5z0qq.fsf-monnier+emacs@gnu.org>
At Tue, 16 Nov 2010 11:57:05 -0500,
Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
> Now, as to why this X11 key composition does not work for you.
> Could you maybe try to rebuild it and show us the output of "configure"?
The full config.log is up at:
http://web.mit.edu/~idleroux/Public/emacsbug7380/config.log
The summary printed at the end of configure was:
Configured for `x86_64--netbsd'.
Where should the build process find the source code? /pkg_comp/obj/pkgsrc/editors/emacs/default/emacs-23.2
What operating system and machine description files should Emacs use?
`s/netbsd.h' and `m/amdx86-64.h'
What compiler should emacs be built with? cc -O2 -pipe -I/usr/pkg/include -I/usr/include -I/usr/X11R7/include -I/usr/X11R7/include/freetype2
Should Emacs use the GNU version of malloc? yes
Should Emacs use a relocating allocator for buffers? yes
Should Emacs use mmap(2) for buffer allocation? no
What window system should Emacs use? x11
What toolkit should Emacs use? GTK
Where do we find X Windows header files? /usr/X11R7/include
Where do we find X Windows libraries? /usr/X11R7/lib
Does Emacs use -lXaw3d? no
Does Emacs use -lXpm? yes
Does Emacs use -ljpeg? yes
Does Emacs use -ltiff? yes
Does Emacs use a gif library? yes -lgif
Does Emacs use -lpng? yes
Does Emacs use -lrsvg-2? yes
Does Emacs use -lgpm? no
Does Emacs use -ldbus? yes
Does Emacs use -lgconf? no
Does Emacs use -lfreetype? yes
Does Emacs use -lm17n-flt? yes
Does Emacs use -lotf? yes
Does Emacs use -lxft? yes
Does Emacs use toolkit scroll bars? yes
D-Bus integration has been tested for GNU/Linux only.
configure: creating ./config.status
config.status: creating Makefile
config.status: creating lib-src/Makefile.c
config.status: creating oldXMenu/Makefile
config.status: creating doc/emacs/Makefile
config.status: creating doc/misc/Makefile
config.status: creating doc/lispintro/Makefile
config.status: creating doc/lispref/Makefile
config.status: creating src/Makefile.c
config.status: creating lwlib/Makefile
config.status: creating lisp/Makefile
config.status: creating leim/Makefile
config.status: creating src/config.h
config.status: executing default commands
creating src/epaths.h
creating lib-src/Makefile
creating src/Makefile
configure: WARNING: Unrecognized options: --without-libiconv-prefix, --without-libintl-prefix
> Not sure it'll help, tho. We'll need either someone to be able to
> reproduce it, or you'll need to dig in the code, play with GDB to try
> and see what's going on there. If you're up to it, you can try and
> place breakpoints near the call to XmbLookupString in xterm.c and single
> step there. Normally, the dead-acute event should not escape from this
> part of the code: instead it should turn into "nothing" (just change
> some state somewhere either in compose_status or in "FRAME_XIC (f)"
> depending on whether that frame uses XIM/XIC),
I had a first crack at this. XmbLookupString is never called because
FRAME_XIC (f) is NULL, so lines 6413--6441 are skipped and
XLookupString is called instead. The result gets categorized as a
NON_ASCII_KEYSTROKE_EVENT.
Where is FRAME_XIC (f) supposed to be set? My first impression is
that that is where the problem is (possibly a configuration problem?)
Any further guidance or tips will be appreciated.
Ian Leroux
next prev parent reply other threads:[~2010-11-21 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 23:18 bug#7380: 23.2; Dead keys misinterpreted in gtk emacs Ian D. Leroux
2010-11-16 16:57 ` Stefan Monnier
2010-11-16 23:56 ` Ian D. Leroux
2010-11-21 0:31 ` Ian D. Leroux [this message]
2011-11-18 18:03 ` Stefan Monnier
2011-11-23 10:13 ` Ian D. Leroux
2012-05-13 16:38 ` Ian D. Leroux
2012-05-14 17:26 ` Glenn Morris
2011-11-14 21:02 ` bug#7380: Dead keys bug, additional info Ian D. Leroux
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=878w0ntt35.wl%idleroux@fastmail.fm \
--to=idleroux@fastmail.fm \
--cc=7380@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).