On 28/12/11 01:53, wolfv wrote:
Hi Tony. I didn't get vary far. Here is what I tried. From the Vim
EX Line editor I typed::!mkdir $HOME/vimfiles
This cmd window popped up:
C:\Windows\system32\cmd.exe /c mkdir $HOME/vimfilesThe syntax of the
command is incorrect.shell returned 1Hit any key to
On 27/12/11 16:50, Peng Yu wrote:
Hi,
vim can open something like http:// But it doesn't open some other
files like href=/css/gray.css that is embedded in a html file by
default. Is there a way to allow this to happen?
Regards,
Peng
That's a relative link, it is relative to the folder
Hi Dotan!
On Di, 27 Dez 2011, Dotan Cohen wrote:
If I accidentally press ma instead of 'a, is there any way to revert
mark A to its previous value? Assuming, of course, that I do not
remember where it was and this is a _long_ file.
I don't think so.
regards,
Christian
--
Pubertät ist, wenn
Hi Suresh!
On Di, 27 Dez 2011, Suresh Govindachar wrote:
Hello,
Consider a C-file with folding method marker.
Declaring the comment regions with the argument conceal and setting
conceallevel to 2 would eat up all the characters in the comment -- except
for any carriage returns in the
On 27/12/11 18:22, Axel Bender wrote:
Why isn't it possible (in Windows?) to use :lanugage to set the language
to e.g. ge-GE.UTF-8 (while ge-GE.1252 would work)?
Because Windows does not support non-numeric code pages. This is, I
think, contrary to the ISO standard, but Microsoft never cared
Thanks for your answer Tony.
UTF-8 corresponds (afaik) to CodePage 65001. Setting language to this value
(e.g. :language English_United States.65001) is possible, however, what are
its effects?
I'll try to grok through the sources...
--
You received this message from the vim_use maillist.
Do
On 28/12/11 18:13, Axel Bender wrote:
Thanks for your answer Tony.
UTF-8 corresponds (afaik) to CodePage 65001. Setting language to this
value (e.g. :language English_United States.65001) is possible, however,
what are its effects?
I'll try to grok through the sources...
Oh, you have the
wolfv wrote the following on 28.12.2011 01:53
Hello wolfv
-- snip --
Second, create a filetype.vim in that new subfolder (I assume that you
don't yet have one in _that_ directory):
:e ~/vimfiles/filetype.vim
,[ ft=text ]---
txt
autocmd
On Dec 28, 1:15 am, Tony Mechelynck antoine.mechely...@gmail.com
wrote:
On 28/12/11 01:53, wolfv wrote:
Hi Tony. I didn't get vary far. Here is what I tried. From the Vim
EX Line editor I typed::!mkdir $HOME/vimfiles
This cmd window popped up:
C:\Windows\system32\cmd.exe /c mkdir
you can use exec !mkdir .expand($HOME).\\vimfiles
On Thu, Dec 29, 2011 at 9:00 AM, wolfv wolfvo...@gmail.com wrote:
On Dec 28, 1:15 am, Tony Mechelynck antoine.mechely...@gmail.com
wrote:
On 28/12/11 01:53, wolfv wrote:
Hi Tony. I didn't get vary far. Here is what I tried. From the
wolfv wrote:
I tried this from cmd window:
C:\Users\wolf
cd %HOME%
The system cannot find the path specified.
It's a long story, some of which is mentioned at:
http://vim.wikia.com/wiki/Filetype.vim
(search for $HOME).
The simplest is to use Vim to find what it thinks:
:echo $HOME
Then
On Dec 28, 7:29 pm, John Beckett johnb.beck...@gmail.com wrote:
wolfv wrote:
I tried this from cmd window:
C:\Users\wolf
cd %HOME%
The system cannot find the path specified.
It's a long story, some of which is mentioned
at:http://vim.wikia.com/wiki/Filetype.vim
(search for $HOME).
Hi Tony!
Oh, you have the sources of Windows?
There was a time when I did have them... But I think - for now - vim's
sources will suffice ;-)
Greetings
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
13 matches
Mail list logo
