Re: Encoding problem

2007-01-12 Thread DervishD
Hi Tony :) * A.J.Mechelynck [EMAIL PROTECTED] dixit: DervishD wrote: * A.J.Mechelynck [EMAIL PROTECTED] dixit: [...] As long as your vimrc includes only 7-bit ASCII, there's no problem. But in the particular case of your vimrc, you could add the following lines at top, do :setlocal

Re: keys available for mapping/leader (was Reformat in visual area - vmap question)

2007-01-12 Thread DervishD
Hi Tim :) * Tim Chase [EMAIL PROTECTED] dixit: \ is hard to type in my keyboard (spanish) because I'm forced to press Alt-Gr plus the top left key in the keyboard (just below ESC), so I'm looking for a good substitute for the leader: do you know where could I find free characters to

Re: Reformat in visual area - vmap question

2007-01-12 Thread DervishD
Hi Tony :) * A.J.Mechelynck [EMAIL PROTECTED] dixit: * Matthew Winn [EMAIL PROTECTED] dixit: The Leader defaults to \ on some installations, I believe. \ is the default value, and that's the value used if mapleader is empty. It's a bad idea to set mapleader to , unless you have a

Re: Encoding problem

2007-01-12 Thread A.J.Mechelynck
DervishD wrote: Hi Tony :) * A.J.Mechelynck [EMAIL PROTECTED] dixit: DervishD wrote: * A.J.Mechelynck [EMAIL PROTECTED] dixit: [...] As long as your vimrc includes only 7-bit ASCII, there's no problem. But in the particular case of your vimrc, you could add the following lines at top,

Re: Reformat in visual area - vmap question

2007-01-12 Thread A.J.Mechelynck
DervishD wrote: [...] I have the 'ñ' at the tip of my right little finger ;) That's a perfect candidate for a leader or as a substitute for backslash :) I have 'ç' too (its a bit farther on the right, but still reachable with the little finger without having to actually look at the

Re: Reformat in visual area - vmap question

2007-01-12 Thread Tim Chase
Yes, ñ or ç would be good. Beware of ' and ` though: they are used in Normal mode for mark movements. Yes, but both keys do the same, so I'm on the safe side if I choose only one of them, am I wrong? They do similar, but not identical actions. The regular tick/apostrophe jumps to the

Re: Encoding problem

2007-01-12 Thread A.J.Mechelynck
DervishD wrote: Hi Tony :) * A.J.Mechelynck [EMAIL PROTECTED] dixit: DervishD wrote: :scriptencoding is used to tell Vim's sourcing engine in which 'fileencoding' the script was written. There are two cases where it is not necessary: - the same as 'encoding', or - UTF-8 with BOM. IOW,

Re: Encoding problem

2007-01-12 Thread A.J.Mechelynck
A.J.Mechelynck wrote: [...] If you leave 'encoding' set at Latin1, Vim won't be able to represent in memory any Unicode codepoints higher than U+00FF, even if you use :e ++enc=utf-8 filename. See for instance the Russian and Arabic text in my front page,

Re: Mac Questions

2007-01-12 Thread Robert Hicks
Alan G Isaac wrote: On Mon, 8 Jan 2007, Brett Calcott apparently wrote: I have just got a Macbook (switching from windows) and have downloaded and compiled the latest version of Vim on it. It all works fine, but I have a few questions. Would you mind outlining the steps you took for someone

Re: Mac Questions

2007-01-12 Thread Krzysztof MaJ
On 2007-01-12, at 03:45, A.J.Mechelynck wrote: By default, Vim doesn't change directories when you open a file. If you open Vim from the Dock, without a filename, the current dir is your home directory. If you later edit one or more files, the current directory is unchanged. If you

Re: .vimrc from URL

2007-01-12 Thread Charles E Campbell Jr
A.J.Mechelynck wrote: Charles E Campbell Jr wrote: OK, with all that: vim -U NONE -c set nocp|so $HOME/.vim/plugin/netrwPlugin.vim -c so scp://HOSTNAME/.vimrc Rather than -U NONE (i.e., no gvimrc) shouldn't that be -u NORC (i.e., with small u: don't source $HOME/.vimrc but do source

Re: vim and mlcscope

2007-01-12 Thread Bram Moolenaar
Frodak wrote: Hello, The cygwin packages allow the installation of vim and mlcscope. I had problems with vim hanging when trying to use the cscope interface. The problem was that vim is that is expecting the first line of the returned output to be cscope: X lines while mlcscope returns

Re: vim and mlcscope

2007-01-12 Thread Sergey Khorev
Maybe it would be a bit safer if we checked that stok ends with cscope: rather than contains? --- if_cscope.c (revision 199) +++ if_cscope.c (working copy) @@ -630,7 +630,7 @@ */ if ((stok = strtok(buf, (const char *) )) == NULL) continue; - if