Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Japanese Input on CentOS / KDE
- Date: Mon, 15 Aug 2005 22:39:13 +0900
- From: "Stephen J. Turnbull" <stephen@example.com>
- Subject: Re: [tlug] Japanese Input on CentOS / KDE
- References: <20050811112410.GB37998@example.com><42FB653C.1000901@example.com><20050811190821.GA66710@example.com><42FC0260.90505@example.com><20050812022231.GA42997@example.com><42FCD382.6040406@example.com><20050812170719.GF92245@example.com><42FCDAF9.8030702@example.com><20050812183206.GA641@example.com><42FD6EAF.101@example.com><20050813043026.GA79097@example.com>
- Organization: The XEmacs Project
- User-agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b21 (corn, linux)
>>>>> "Scott" == Scott Robbins <scottro@example.com> writes: Scott> I don't use KDE and I don't boot up in a GUI. I think Scott> you'd be better off changing it to boot into text Scott> mode--you'll also find that your machine boots more Scott> quickly. That's like saying you should switch to vi from Emacs because it starts more quickly. If you do most of your work from the GUI, there's only one consideration: which way requires less attention and gives you a longer coffee break? The only good reasons for booting into text mode are - security (if you can operate with a subset of the installed programs, deleting the ones you don't need improves security) - efficiency (if the console is good enough, you save cycles and memory by not starting the GUI) - you're pretty sure you're going to have to reboot before you can do something useful with the GUI (you obviously are an unstable personality, Mr. Robbins, and it's reflected in your preference for text mode) In part this is laziness, in part it's also a belief that people should boot into text mode. (To do that, see my faq for Linux newcomers at http://www.scottro.net/linfaq.html There's a question there about changing bootup from text to GUI or vice versa.) The one thing I would suggest, is rather than even running the script, is simply have the jinput.sh script read Scott> #!/bin/bash Scott> kinput2 -canna & Scott> Then, put the environment variables in .bashrc or Scott> .bash_profile. That is, in .bashrc Scott> XMODIFIERS=@example.com=kinput2 LC_CTYPE=ja_JP.eucJP Scott> I think that would work, though it's untested. This is weak. The interactions among the various startup files are complex, and the user will lose Japanese if he switches to a different file. To be robust, this stuff needs to be established in the GUI startup. (I don't do KDE or GNOME so don't ask me!) -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.
- Follow-Ups:
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Scott Robbins
- References:
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Scott Robbins
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Dave Gutteridge
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Scott Robbins
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Dave Gutteridge
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Scott Robbins
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Dave Gutteridge
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Scott
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Dave Gutteridge
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Scott Robbins
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Dave Gutteridge
- Re: [tlug] Japanese Input on CentOS / KDE
- From: Scott Robbins
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] UIM [was: hajimemashite]
- Next by Date: Re: [tlug] scim doesn't find fonts in Slackware
- Previous by thread: Re: [tlug] Japanese Input on CentOS / KDE
- Next by thread: Re: [tlug] Japanese Input on CentOS / KDE
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links