From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: jet@gyve.org, emacs-devel@gnu.org
Subject: Re: New dumping problem...
Date: Fri, 24 Jun 2005 16:09:47 +0900 [thread overview]
Message-ID: <b9yekasdydg.fsf@jpl.org> (raw)
In-Reply-To: E1Dlgr1-0001RH-9Y@fencepost.gnu.org
>>>>> In <E1Dlgr1-0001RH-9Y@fencepost.gnu.org> Richard M. Stallman wrote:
>> * Nonprivileged Emacs users can avoid the C-SPC problem by building
>> Emacs with `--without-xim'.
> She or he will be able to run Emacs built in the home directory.
> That is good news. Could someone write an item for etc/PROBLEMS?
I wrote it, but it will probably be necessary to be corrected by
someone since I'm not a native writer. ;-)
It was reported that there is a problem that the Redhat Fedora Core 4
steals the C-SPC key by default for the `iiimx' program which is the
input method for some languages. It blocks Emacs users from using the
C-SPC key for `set-mark-command'. Currently, two ways to solve it are
known. One is to remove the `<Ctrl>space' from the Iiimx file which
can be found in the /usr/lib/X11/app-defaults directory. The other is
to rebuild Emacs using the `--without-xim' configure option.
next prev parent reply other threads:[~2005-06-24 7:09 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 23:59 New dumping problem David Kastrup
2005-03-29 19:41 ` Jan D.
2005-03-30 10:02 ` Thien-Thi Nguyen
2005-03-30 16:20 ` Richard Stallman
2005-03-30 19:17 ` Jan D.
2005-04-01 4:11 ` Richard Stallman
2005-04-01 9:54 ` Nick Roberts
2005-04-02 4:19 ` Richard Stallman
2005-03-30 0:03 ` Richard Stallman
2005-06-17 5:27 ` Katsumi Yamaoka
2005-06-17 7:07 ` Masatake YAMATO
2005-06-17 17:07 ` Masatake YAMATO
2005-06-18 1:17 ` Katsumi Yamaoka
2005-06-18 3:28 ` Masatake YAMATO
2005-06-20 0:42 ` Katsumi Yamaoka
2005-06-20 1:54 ` Masatake YAMATO
2005-06-20 17:51 ` Richard Stallman
2005-06-26 16:01 ` Masatake YAMATO
2005-06-26 17:39 ` Jason Rumney
2005-06-27 0:10 ` Masatake YAMATO
2005-06-27 5:38 ` Richard M. Stallman
2005-06-27 15:49 ` Masatake YAMATO
2005-06-30 16:26 ` Masatake YAMATO
2005-07-01 0:43 ` Katsumi Yamaoka
2005-07-01 4:02 ` Richard M. Stallman
2005-07-01 9:54 ` jhd
2005-07-01 10:29 ` Masatake YAMATO
2005-07-01 22:45 ` Richard M. Stallman
2005-07-01 22:48 ` Masatake YAMATO
2005-07-03 15:48 ` Richard M. Stallman
2005-07-01 22:45 ` Richard M. Stallman
2005-07-02 7:46 ` jhd
2005-07-03 15:48 ` Richard M. Stallman
2005-07-03 21:52 ` Jan D.
2005-06-20 17:51 ` Richard Stallman
2005-06-22 2:00 ` Katsumi Yamaoka
2005-06-22 8:20 ` Katsumi Yamaoka
2005-06-23 0:54 ` Richard M. Stallman
2005-06-23 1:08 ` Katsumi Yamaoka
2005-06-23 7:50 ` Kim F. Storm
2005-06-23 8:19 ` Katsumi Yamaoka
2005-06-23 14:28 ` Kim F. Storm
2005-06-24 0:39 ` Katsumi Yamaoka
2005-06-24 0:43 ` Katsumi Yamaoka
2005-06-24 14:18 ` Stefan Monnier
2005-06-24 16:37 ` Richard M. Stallman
2005-06-24 5:35 ` Richard M. Stallman
2005-06-24 7:09 ` Katsumi Yamaoka [this message]
2005-06-25 13:35 ` Richard M. Stallman
2005-06-17 18:45 ` Richard Stallman
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=b9yekasdydg.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.org \
--cc=jet@gyve.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).