Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Kinput2 and Wnn6
- To: tlug@example.com
- Subject: Re: tlug: Kinput2 and Wnn6
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Sat, 10 Oct 1998 09:32:53 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <m3btnm848p.fsf@example.com>
- References: <Pine.LNX.3.96LJ1.1b7.981009160844.2090E-100000@example.com><19981009171557O.hhasebe@example.com><m3btnm848p.fsf@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Frank" == Frank Bennett <bennett@example.com> writes: Frank> Hmm. That's a thought. But why would Emacs and Kinput2 Frank> behave differently (in both instances Emacs and Applixware Frank> respectively were running solo, by themselves)? The interfaces are different, so they'll behave differently. One possibility is that kinput2 is a server, and therefore running as a specific user, especially if it's in xinitrc or similar. I don't know how kinput2 passes private dictionary information to Wnn. But if it just passes its effective ID, then wnn thinks that kinput2 is user kinput, while Emacs is almost certainly running as your personal user. This would result in the dictionaries getting decoupled. Take a look at ps aux and see what userid kinput2 is using. Frank> The server certainly _claims_ to be willing to speak with Frank> anyone, without conditions: I don't trust such messages to mean what I think they mean. The person who wrote those messages knows altogether too much about how the program works to write meaningful messages to naive (ie, haven't read the source) users. Frank> Is this due to some limitation in Kinput2 --- maybe the Frank> patch for Wnn6 is missing something? Could be. Gotta love proprietary softo. But more likely it's pilot error, ahem, it's that Wnn is just too bloody complicated for anyone to set up correctly. Works out of the box for most people, but one reason I have avoided Wnn for the last five years is that during the three years previous I was an Wnn user, and my Wnn privileges would suddenly get revoked by the remote server, for no reason anyone here could explain. They would have to restart the server to fix it. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +1 (298) 53-5091 --------------------------------------------------------------- Next Meeting: 10 October, 12:30 Tokyo Station Yaesu central gate Featuring the IMASY Eng. Team on "IPv6 - The Next Generation IP" Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691 --------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- Re: tlug: Kinput2 and Wnn6
- From: Frank Bennett <bennett@example.com>
- References:
- Re: tlug: Kinput2 and Wnn6
- From: Scott Stone <sstone@example.com>
- Re: tlug: Kinput2 and Wnn6
- From: Hiroshi Hasebe <hhasebe@example.com>
- Re: tlug: Kinput2 and Wnn6
- From: Frank Bennett <bennett@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: parallel-port IDE
- Next by Date: Re: tlug: parallel-port IDE
- Prev by thread: Re: tlug: Kinput2 and Wnn6
- Next by thread: Re: tlug: Kinput2 and Wnn6
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links