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: Neil Booth <neil@example.com>
- Date: Mon, 19 Mar 2001 22:23:46 +0000
- Content-Disposition: inline
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <01032005050600.01926@example.com>; from aim@example.com on Tue, Mar 20, 2001 at 05:05:06AM +0900
- References: <01032005050600.01926@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <_2zop.A.s-H.5bot6@example.com>
- Resent-Sender: tlug-request@example.com
- User-Agent: Mutt/1.3.15i
CSD wrote:- > I've recently upgraded to hte new version of X, which is wonderful, because > I'm finally off the framebuffer! But I can no longer get ATOKX (or any other > henkan system) to work now. Has anyone else had problems with henkan > after upgrading X? What did you do? > > Any help would be VERY much appreciated. Hmm, interesting. It works in GNU emacs for me, but not in kterm. It used to work in kterm too, and now you mention it I upgraded X in between. But that's about all I can report :-) Neil.
- References:
- ATOK messed up after XF86-4.0.2 upgrade
- From: CSD <aim@example.com>
Home | Main Index | Thread Index
- Prev by Date: ATOK messed up after XF86-4.0.2 upgrade
- Next by Date: Re: ATOK messed up after XF86-4 upgreade - a new problem
- Prev by thread: 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