On 20 August 2013, Ingo Karkat wrote:
> On 13-Aug-2013 18:46 +0200, ZyX wrote:
>
> > I see that all g:vimsyn_embed flags say things like ?embed ? **(but
> > only if vim supports it)**?. This is ridiculous: you don?t have to
> > have vim lua support to code in lua and have syntax highlighting;
> >
Oh, and this happens even with
:call mkdir('foo/', 'p')
Seems like all that matters is the trailing slash and the 'p' flag, nothing
special about the path.
David
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
Ensure ./foo doesn't exist, and do
:call mkdir('foo/bar/', 'p')
Vim gives you an error:
E739: Cannot create directory: foo/bar/
but the directory was created just fine.
Dropping the trailing slash works without error:
:call mkdir('foo/bar', 'p')
David
--
--
You received this message fro
Christian Brabandt wrote:
> On Do, 15 Aug 2013, Bram Moolenaar wrote:
>
> > Christian Brabandt wrote:
> > > Wouldn't it be a good idea, to have the file set readonly for as long it
> > > hasn't been encrypted (e.g. the current windows behaviour)?
> >
> > You mean, until it has been decrypted.
spellsuggest with 'set sps:file:{filename}' doesn't work.
I'm using vim 7.4.5 on windows 7.
I created a file, say sps.txt, and put there the following lines:
Enantes/Antes
chaofa/chaufa
aser/hacer
kion/kión
sutra/sūtra
Suppose I have a file, say test.txt, with the following line:
Enantes pude a
On Tue, Aug 20, 2013 at 9:29 PM, Ingo Karkat wrote:
[...]
> I came to the same conclusion: While it is noble that the Vim syntax
> plugin notifies the user that the used script interpreter is not
> available in the current editor, having huge blocks of red error
> highlighting is certainly overdoi
On 13-Aug-2013 18:46 +0200, ZyX wrote:
> I see that all g:vimsyn_embed flags say things like “embed … **(but
> only if vim supports it)**”. This is ridiculous: you don’t have to
> have vim lua support to code in lua and have syntax highlighting; you
> specifically don’t have to have vim lua suppor
Hi Marius!
On Di, 20 Aug 2013, Marius Gedminas wrote:
> Vim 7.4 broke my svn filetype plugin (http://mg.pov.lt/vim/ftplugin/svn.vim).
>
> The plugin opens a new split window and puts the output of 'svn diff' in
> there when I run 'svn commit'. This window gets some attributes set,
> including '
Vim 7.4 broke my svn filetype plugin (http://mg.pov.lt/vim/ftplugin/svn.vim).
The plugin opens a new split window and puts the output of 'svn diff' in
there when I run 'svn commit'. This window gets some attributes set,
including 'previewwindow', which I use to make vim quit as soon as I
close th
Hi, this bug really hurts me a long time.If you use VIM on a Windows
system and using directories with an exclamation mark the filename
completion does not work.
If you want to load
c:folder!file.txt you can write :e c:fold Now the line will
be expanded to :e c:folder! The exclamation mar
Pasting text produces inconstisten screen state. Looks like a mixture of
monospaced and proportional font. Resetting rop to empty fixes the
problem--and reintroduces the missing char glyphs.
Attached is screenshot with the lines showing
1) state right after paste (cursor was aligned above the 2nd-
On Mon, Aug 19, 2013 at 2:31 PM, Ken Takata wrote:
> Using DirectWrite seems to fix the following issue from the todo.txt:
>
>> 8 Win32: Multi-byte characters are not displayed, even though the same font
>> in Notepad can display them. (Srinath Avadhanula) Try with the
>> UTF-8-demo.txt
You are correct Danek. I cleared out the config.cache and it installed fine. I
installed it earlier on Solaris 10.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/mai
On Tue, August 20, 2013 09:02, Ingo Karkat wrote:
> Note that concealing has to extend the existing syntax, which can break
> it.
Well changing the syntax rules is of course a way of breaking it, but
I think it should work well enough most of the times. And while I am not
very proficient with synt
On 20-Aug-2013 02:16 +0200, Jesus Antonio Santos Giraldo wrote:
> Good one.
>
> Didn't knew about _concealing_ but so far it looks like the best
> approach to show spaces that I've seen.
Note that concealing has to extend the existing syntax, which can break
it. You need autocmds to set it up (a
15 matches
Mail list logo
