Gene Kwiecinski wrote:
Otherwise, do a '0' and ride the 'j' key a the way down a
file. If the cursor doesn't budge, how would you be able to
tell if it was a space or multiple spaces there, or a tab
character?
Well, if that information is truely useful and what you want to
know, you can a
>Try ':help listchars'
Tnx. Kinda figured there was some option to do that, but never bothered
to look up what it might be. Complacency and all...
Good to know, but I still just like the cursor jiggling back'n'forth
between col0 and col7 when I ride the down/'j' key. It's so much
easier... :D
Try ':help listchars'
"Gene Kwiecinski" <[EMAIL PROTECTED]>
16/04/2007 16:36
To: "Tim Chase" <[EMAIL PROTECTED]>,
cc:
Subject: RE: Troubles configuring vim (multi-questions)
>>Otherwise, do a '0&#
Well, if that information is truely useful and what you want to
know, you can always
:set list
Displays "^I" just fine, but trashes actual indentation, at least for me
(dunno if there's any magical 'vim' setting, like ":set keepindent" or
something). Iow, I wanna be able to see
* Gene Kwiecinski [2007.04.16 11:45]:
> Displays "^I" just fine, but trashes actual
> indentation, at least for me (dunno if there's
> any magical 'vim' setting, like ":set
> keepindent" or something).
set listchars+=tab:>-
--
JR
>>Otherwise, do a '0' and ride the 'j' key a the way down a
>>file. If the cursor doesn't budge, how would you be able to
>>tell if it was a space or multiple spaces there, or a tab
>>character?
>Well, if that information is truely useful and what you want to
>know, you can always
> :s
Otherwise, do a '0' and ride the 'j' key a the way down a
file. If the cursor doesn't budge, how would you be able to
tell if it was a space or multiple spaces there, or a tab
character?
Well, if that information is truely useful and what you want to
know, you can always
:set lis
>By default Vim (and vi) has always put the cursor on the end of a
>character that occupies multiple spaces on the screen. I don't know
>why this decision was taken, unless it was to make it easier to spot
>the difference between lines indented with tabs and those indented
>with spaces, but the cur
OnionKnight schrieb:
I think I understand the difference now and my function is pretty neat now.
function! HomeKey ()
let c = col(".")
if c == 1
normal ^
else
normal ^
if col(".") >= c
normal 0
On Fri, 13 Apr 2007 08:44:26 -0700 (PDT), OnionKnight
<[EMAIL PROTECTED]> wrote:
> No it didn't make a difference. When you put the cursor in normal mode over
> a tab character, which spans several characters, the cursor will be
> displayed at the end of that area whereas insert mode will put the
>I'm not entirely sure what you want here; does having
> set nosol
>in your <.vimrc> help?
No it didn't make a difference. When you put the cursor in normal mode over
a tab character, which spans several characters, the cursor will be
displayed at the end of that area whereas insert mode will put
OnionKnight wrote:
* Is it possible to make the cursor stay at it's position even after
scrolling it out of view?
Not at the current time.
* At the beginning of an indented line, why does normal mode put the cursor
at the end of the first tab whereas insert mode is position at the beginning
On 4/13/07, OnionKnight <[EMAIL PROTECTED]> wrote:
Couldn't find anything about command-mode. How is it different from normal
mode?
Dont confuse 'commandline mode' with 'command mode'.
'comand mode' is same as 'normal mode', they are synonyms [1].
'commandline mode' is a mode which you enter
Easwy Yang wrote:
>
> If you use Vim in windows, see here:
> http://www.vim.org/tips/tip.php?tip_id=1440
> http://www.vim.org/tips/tip.php?tip_id=1314
>
> In Unix, you can use
> gvim --remote-tab-silent filename
>
But there's no way to do that for just the drag-and-drop operation in gvim?
--
OnionKnight wrote:
inside a script you're in "command-mode", and the command "w" you've meant
to should be in "normal-mode", the correct way might be :normal w, :normal
g0w, etc...
Couldn't find anything about command-mode. How is it different from normal
mode? Is each line treated as one comman
From: OnionKnight <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Troubles configuring vim (multi-questions)
Date: Thu, 12 Apr 2007 17:22:06 -0700 (PDT)
[deleted]
* I wanted the Home-button to act so that it first jumps to the first
non-whitespace character of the current line (i.e. skip th
OnionKnight <[EMAIL PROTECTED]> 写于 2007-04-13 10:05:10:
> Couldn't find anything about command-mode. How is it different from
normal
> mode? Is each line treated as one command? Like g0w is treated as "g0w"
> instead of "g0" and "w"?
Vim is a multi-mode editor, in different mode, it accepts comple
>inside a script you're in "command-mode", and the command "w" you've meant
>to should be in "normal-mode", the correct way might be :normal w, :normal
>g0w, etc...
Couldn't find anything about command-mode. How is it different from normal
mode? Is each line treated as one command? Like g0w is tre
I can answer some of the questions. See below.
2007/4/13, OnionKnight <[EMAIL PROTECTED]>:
I've been thinking of migrating to using vim (gvim) but I'm running into lots
of difficulties on the road I just can't solve, and the documentation is...
well, strange at best.
* Is it possible to make t
OnionKnight <[EMAIL PROTECTED]> 写于 2007-04-13 08:22:06:
> I've been thinking of migrating to using vim (gvim) but I'm running into
lots
> of difficulties on the road I just can't solve, and the documentation
is...
> well, strange at best.
It seems that Vim had a longer learning curve than other edi
20 matches
Mail list logo
