Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: ATOK messed up after XF86-4.0.2 upgrade
- To: tlug@example.com
- Subject: Re: ATOK messed up after XF86-4.0.2 upgrade
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Sat, 24 Mar 2001 21:35:19 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <20010324103142.A20682@example.com>
- References: <01032005050600.01926@example.com><20010321102733.A24750@example.com><20010321111743.L3408@example.com><20010321114424.C24750@example.com><s3tu24nl695.fsf@example.com><20010322130705.B18516@example.com><s3tsnk5iotn.fsf@example.com><20010323105509.A7869@example.com><20010324103142.A20682@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <m4ri9B.A.rMG.gXJv6@example.com>
- Resent-Sender: tlug-request@example.com
>>>>> "Neil" == Neil Booth <neil@example.com> writes: Neil> I downloaded and tried Xemacs; that gave me an interesting Neil> warning: Neil> (1) (xim-xlib/info) X Input Method open failed. Waiting for Neil> an XIM to be enabled. Neil> This may be related to the null pointer return you Neil> discussed. Or I could have XIM set up wrongly; I've not Neil> investigated further yet. Most likely. Here's the relevant XEmacs code (exactly what you'd think): DEVICE_X_XIM (d) = xim = XOpenIM (dpy, XtDatabase (dpy), name, class); /* much code, including end of one function and beginning of another, elided, but I tell you 3 times, it's OK */ if (!xim) { xim_info ("X Input Method open failed. Waiting for an XIM to be enabled.\n"); return; } (DEVICE_X_XIM is an XEmacs-specific accessor macro for an XEmacs X_XIM object.) -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."
- Follow-Ups:
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Neil Booth <neil@example.com>
- References:
- ATOK messed up after XF86-4.0.2 upgrade
- From: CSD <aim@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Christopher SEKIYA <wileyc@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: "Thomas O'Dowd" <tom@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Christopher SEKIYA <wileyc@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Mike Fabian <mfabian@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Christopher SEKIYA <wileyc@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Mike Fabian <mfabian@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Christopher SEKIYA <wileyc@example.com>
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Neil Booth <neil@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: ATOK messed up after XF86-4.0.2 upgrade
- Next by Date: Re: ATOK messed up after XF86-4.0.2 upgrade
- Prev by thread: Re: ATOK messed up after XF86-4.0.2 upgrade
- Next by thread: Re: ATOK messed up after XF86-4.0.2 upgrade
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links