Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: jvim
- To: <tlug@example.com>
- Subject: Re: jvim
- From: "SN_Diamond" <Norman.Diamond@example.com>
- Date: Tue, 3 Apr 2001 08:34:32 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain;charset="iso-8859-1"
- References: <20010401135950.A3859@example.com> <00c201c0baf8$e85675d0$0f01a8c0@example.com> <20010402142747.B9670@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <tsO0pC.A.EPF.xyQy6@example.com>
- Resent-Sender: tlug-request@example.com
Tobias Diedrich wrote: > On Mon, Apr 02, 2001 at 07:12:20AM +0900, SN_Diamond wrote: [about vim 6.0z beta] > > bugs. Support for XIM is built-in, if you set options correctly in the > > Makefile. In either insert mode or the colon's command prompt mode, > > shift-space turns XIM on and off. In visual command mode (i.e. when > > What about vim without X ? > I like sticking to the console... ^_^ I haven't checked recently, but I think there will be no exception then. I think that the console will retain control over whether XIM is active. However, you're unlikely to make a mistake in visual command mode (i.e. beep mode) because XIM will still keep its indicator on the screen, reminding you of your input mode, until you hit shift-space. The gnome console has trouble with hankaku katakana but kterm doesn't. If there's any chance that you'll be editing a file containing hankaku katakana, you'll either want to use vim 6.0 under kterm, or gvim 6.0. Mike Fabian reminded us that Ctrl-O should also turn XIM on and off. I haven't tested it under vim 6.0z beta. Yours sincerely, Norman Diamond
- Follow-Ups:
- Re: jvim
- From: "Stephen J. Turnbull" <turnbull@example.com>
- References:
Home | Main Index | Thread Index
- Prev by Date: Re: jvim
- Next by Date: Re: jvim
- Prev by thread: Re: jvim
- Next by thread: Re: jvim
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links