unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: boris <boris@iis.sinica.edu.tw>
Cc: 11234@debbugs.gnu.org
Subject: bug#11234: 23.4; Compose key does not work well in current Debian testing (wheezy).
Date: Fri, 13 Apr 2012 15:31:41 -0400	[thread overview]
Message-ID: <jwvpqbb1lrp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20120413144711.de4a33d94904e1afc2839f71@iis.sinica.edu.tw> (boris@iis.sinica.edu.tw's message of "Fri, 13 Apr 2012 14:47:11 +0800")

> After running emacs under Debian mentioned above, fully updated,
> general compose key shortcuts do not work. The only compose key
> shorcuts that work in emacs under the described conditions are
> those, that are defined in ~/.XCompose file (I defined three shortcuts
> there, ☺, →, ← to test what I say, and they work. The shortcuts defined
> in /usr/share/X11/locale/... do not work. Compose key works OK in other
> X programs, such as Libre Office, Iceweasel, terminator. Eg. xterm seems
> to have similar problem as emacs, but that might be due to its inept
> font. I posted it on stackoverflow, and was told to send a bug report.

Do the usual compose sequences work if you remove the ~/.XCompose file?
Can you show us the content of that ~/.XCompose file?
Do your hand-made .XCompose sequences work in LibreOffice/Iceweasel/...?

IOW my crystal ball tells me that your .XCompose file is lacking
a `include "%L"' so it overrides the default rather than extends it.
And you don't notice it in Iceweasel because you haven't set the envvar
GTK_IM_MODULE=xim, so those apps don't actually use your .XCompose
file anyway.


        Stefan





  reply	other threads:[~2012-04-13 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13  6:47 bug#11234: 23.4; Compose key does not work well in current Debian testing (wheezy) boris
2012-04-13 19:31 ` Stefan Monnier [this message]
2019-11-01 19:50   ` Stefan Kangas

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=jwvpqbb1lrp.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=11234@debbugs.gnu.org \
    --cc=boris@iis.sinica.edu.tw \
    /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).