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: Mike Fabian <mfabian@example.com>
- Date: 22 Mar 2001 20:00:41 +0100
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: Christopher SEKIYA's message of "Thu, 22 Mar 2001 13:07:05 +0900"
- 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>
- Reply-To: mfabian@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <ZF6zP.A.8VE.jvku6@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: mfabian@example.com
- User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Channel Islands)
Christopher SEKIYA <wileyc@example.com> writes: > On Wed, Mar 21, 2001 at 12:18:46PM +0100, Mike Fabian wrote: > > > Can you give an example what exactly doesn't work? Does it happen > > in all applications or only in kterm? > > (hell with kterm, it has nasty incestuous knowledge of kinput2) > > Example: > > * set XMODIFIERS to proper value > * start cannaserver > * start kinput2 > * start rxvt in gdb > * set breakpoint at main.c:1238 > * examine value of variable xim > > Neat, huh? rxvt 2.7.5 mfabian@example.com:/sugi/mfabian/cvs/rxvt-cvs/src$ locale LANG=ja_JP LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=POSIX LC_MONETARY= LC_MESSAGES= LC_PAPER="ja_JP" LC_NAME="ja_JP" LC_ADDRESS="ja_JP" LC_TELEPHONE="ja_JP" LC_MEASUREMENT="ja_JP" LC_IDENTIFICATION="ja_JP" LC_ALL= mfabian@example.com:/sugi/mfabian/cvs/rxvt-cvs/src$ echo $XMODIFIERS @example.com=kinput2 mfabian@example.com:/sugi/mfabian/cvs/rxvt-cvs/src$ Breakpoint 2, rxvt_IMInstantiateCallback (display=0x8072a78, client_data=0x0, call_data=0x0) at main.c:1238 (gdb) p xim $1 = 0x0 (gdb) What is so neat about that? void rxvt_IMInstantiateCallback(Display *display, XPointer client_data, XPointer call_data) { char *p, *s, buf[IMBUFSIZ], tmp[1024]; char *end, *next_s; XIM xim = NULL; XIMStyles *xim_styles = NULL; int found; XPoint spot; XRectangle rect, status_rect, needed_rect; unsigned long fg, bg; XVaNestedList preedit_attr = NULL; XVaNestedList status_attr = NULL; XIMCallback ximcallback; rxvt_t *r = _rxvt_vars; if (r->h->Input_Context) return; ximcallback.callback = rxvt_IMDestroyCallback; ximcallback.client_data = call_data; <--- line 1238 What should I expect here? xim is initialized to NULL, and there is no code to change that until line 1238, so of course it is still NULL. Are we talking about the same sources? -- Mike Fabian <mfabian@example.com>
- Follow-Ups:
- Re: ATOK messed up after XF86-4.0.2 upgrade
- From: Christopher SEKIYA <wileyc@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>
Home | Main Index | Thread Index
- Prev by Date: Re: Debian: non-us config
- 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