Hi Fan,
2008/1/21 Fan Decheng [EMAIL PROTECTED]:
[...]
Here is a snippet from the Vim's reference:
NOTE: Changing this option will not change the encoding of the
existing text in Vim. It may cause non-ASCII text to become
invalid.
It should normally be
(totally off-topic couldn't be more off-topic... really, I warned you!)
On Jan 20, 2008 3:01 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Corn oil comes from corn and olive oil comes from olives, so where
does baby oil come from?
You can make this even worse by saying:
Corn oil comes from
On Fri, Jan 18, 2008 at 13:29:51 +0100, Bram Moolenaar wrote:
Adri Verhoef wrote:
Compilation of Vim 7.1.230 on an Alpha processor with Gcc yielded:
gui_motif.c: In function 'find_replace_dialog_create':
gui_motif.c:3816: warning: cast to pointer from integer of different size
Adri Verhoef wrote:
On Fri, Jan 18, 2008 at 13:29:51 +0100, Bram Moolenaar wrote:
Adri Verhoef wrote:
Compilation of Vim 7.1.230 on an Alpha processor with Gcc yielded:
gui_motif.c: In function 'find_replace_dialog_create':
gui_motif.c:3816: warning: cast to pointer from
Ben Schmidt wrote:
Here is a snippet from the Vim's reference:
NOTE: Changing this option will not change the encoding of the
existing text in Vim. It may cause non-ASCII text to become invalid.
It should normally be kept at its default value, or set when Vim
hi,I use OpenSolaris (solaris express community edition,snv_73).I download
vim-7.1.tar.zip2,vim-7.1-extra.tar.zip2,vim-7.1-lang.tar.zip2,bunziped them
into a directory .configureed options as bellow:
./configure --enable-gui --enable-pythoninterp --enable-cscope --enable-sniff
On Thu, Jan 17, 2008 at 05:19:39PM +0100, Dominique Pelle wrote:
Then vim -u /tmp/vimrc -X hangs when run under screen. It does not
display anything, or respond to terminal input (including Ctrl-C).
When killed (SIGTERM), it draws the intro screen and prints a
message saying Received
I cannot imagine a situation where this would be desirable.
Conversely, I think it makes for a great April Fool's Joke. I'd rather
prefer not being the recipient, though.
What does everyone think about making
guifont unsettable from the modeline? It is a global option, after all.
I just don't
Erik Falor wrote:
I cannot imagine a situation where this would be desirable.
Conversely, I think it makes for a great April Fool's Joke. I'd rather
prefer not being the recipient, though.
What does everyone think about making
guifont unsettable from the modeline? It is a global
But something I really do think is worth changing because it's really
confusing, is ++enc. Why do we call this ++enc not ++fenc which would
make a huge amount more sense, and be more consistent with ++ff and
++bin which both set their namesake options? We see evidence of people
getting 'enc'
I am wondering how one might go about adding keywords while a file is
being syntax-highlighted.
The idea is that at the top of a file, one defines a new function.
Afterwards, in that file, that function should be highlighted as
known.
I realize it can be done using tags; I am looking for
2008/1/21 noname wind [EMAIL PROTECTED]:
but, I got a vim without ,why?
I presume you mean you got a version without X.
As you seem to have configured it correctly, I suggest you send
the whole output of make to this list so people can look at it :)
RIchard
Tony Mechelynck wrote:
What does everyone think about making guifont unsettable from
the modeline? It is a global option, after all. I just don't
think it makes that much sense to be set from the modeline.
It is a global option, but if you know what you're doing it
may sometimes be useful
13 matches
Mail list logo
