>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 the cursor at
the beginning of it.
>Try mapping it; put the following into your <.vimrc>:
> nmap <middlemouse> :tabc<cr>
But that's for the whole file? I was just thinking of when you middleclick
over the tab button like in Firefox or Opera.
>You're getting your modes confused.
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
endif
endif
endfunction
>Can't answer that -- I never use the mouse to drag-and-drop. Even if
>you set up some autocmds to do this,
>if you drop the same file onto vim you'll still get extra tabs unless
>your code sweeps through all the tabs
>and checks for a name match first.
autocmds seems interesting. They're basically callbacks? Would applying some
command/function to BufRead that creates a new tab and assigns that tab with
the new buffer work? I don't really care if it's dragged and dropped or if
it was opened through some command. I was thinking that any opening of a new
file should be done by creating a tab for it, but I felt like taking a
minimalistic approach and allowing other forms of opening to coexist like
using windows or just creating a buffer.
>By string, do you mean something with double-quotes?
I was thinking of an internal string, used in command mode, not having
anything to do with the document. But I found a solution in using =~ and
substitute().
--
View this message in context:
http://www.nabble.com/Troubles-configuring-vim-%28multi-questions%29-tf3569025.html#a9981336
Sent from the Vim - General mailing list archive at Nabble.com.
