Hi list,
Last night I switched to Vim 7.3 and one of the first things I wanted to
try was the new conceal feature. A perfect test subject for me was
Markdown text formatting because its goal is to be very readable but its
syntax rules kind of get in the way of readability :-) (IMHO).
After s
On Thu, Jul 22, 2010 at 04:57:57AM +0200, Tony Mechelynck wrote:
> Note that syntax/perl.vim is well-behaved: what it does at line 57
> is ":setlocal foldmethod=syntax" (not plain :set) so it will only
> apply to Perl sources and to filetypes which (like Vim scripts) may
> contain embedded Perl sou
On 22/07/10 04:35, Christian J. Robinson wrote:
I just noticed that my 'foldmethod' is getting set to "syntax" when
editing Vim script files, but the syntax/vim.vim file doesn't set that
option even if you've enabled syntax folding for Vim code.
Since I have "let perl_fold=1" in my vimrc, I get
I just noticed that my 'foldmethod' is getting set to "syntax" when
editing Vim script files, but the syntax/vim.vim file doesn't set that
option even if you've enabled syntax folding for Vim code.
Since I have "let perl_fold=1" in my vimrc, I get this when I do
":verbose set fdm?" while in
On 22/07/10 02:50, Cesar Romani wrote:
I'm getting the following error:
...
gcc ... if_perl.c -o gobjZ/if_perl.o
if_perl.xs:101:19: fatal error: dlfcn.h: No such file or directory
compilation terminated.
make: *** [gobjZ/if_perl.o] Error 1
Many thanks i
On 22/07/10 02:50, Cesar Romani wrote:
I'm getting the following error:
...
gcc ... if_perl.c -o gobjZ/if_perl.o
if_perl.xs:101:19: fatal error: dlfcn.h: No such file or directory
compilation terminated.
make: *** [gobjZ/if_perl.o] Error 1
Many thanks i
I'm getting the following error:
...
gcc ... if_perl.c -o gobjZ/if_perl.o
if_perl.xs:101:19: fatal error: dlfcn.h: No such file or directory
compilation terminated.
make: *** [gobjZ/if_perl.o] Error 1
Many thanks in advance,
--
Cesar
--
You received th
I just noticed that autocmd.txt references $VIMRUNTIME/plugin/netrw.vim
which doesn't exist. This is with the latest Vim 7.3 from the mercurial
repository (I upgraded to check this, the upgrade from 7.2 -> 7.3 went
flawless BTW thanks to http://www.vim.org/mercurial.php). I guess the
filename s
On 21/07/10 20:35, Dominique Pellé wrote:
duffman wrote:
Many thanks for your replies! I am working at a big corporation and
the IT-powers that be have access to most root level modifications. I
have read/write permissions on my home directory (/home/myName).
Could I install the vim editor und
On Wed, Jul 21, 2010 at 3:41 PM, James Vega wrote:
> On Wed, Jul 21, 2010 at 4:58 PM, Christian J. Robinson
> wrote:
>> On Wed, Jul 21, 2010 at 2:08 PM, Bram Moolenaar wrote:
>>>
>>> We could wait for people to test this, but on the other hand if we
>>> want to do the same for ruby/tcl/mzscheme
On Wed, Jul 21, 2010 at 5:05 PM, Tony Mechelynck
wrote:
> On 21/07/10 22:08, Bram Moolenaar wrote:
>>
>> James Vega wrote:
>>
>>> On Mon, Jul 19, 2010 at 3:17 PM, Bram Moolenaar
>>> wrote:
If you can make this work with a configure argument, it's fine to
include these changes and l
On Wed, Jul 21, 2010 at 4:58 PM, Christian J. Robinson
wrote:
> On Wed, Jul 21, 2010 at 2:08 PM, Bram Moolenaar wrote:
>>
>> We could wait for people to test this, but on the other hand if we
>> want to do the same for ruby/tcl/mzscheme we need to do it now, next
>> week I won't include patches l
On Jul 21, 1:17 pm, duffman wrote:
> Many thanks for your replies! I am working at a big corporation and
> the IT-powers that be have access to most root level modifications. I
> have read/write permissions on my home directory (/home/myName).
> Could I install the vim editor under my directory
On 21/07/10 22:08, Bram Moolenaar wrote:
James Vega wrote:
On Mon, Jul 19, 2010 at 3:17 PM, Bram Moolenaar wrote:
If you can make this work with a configure argument, it's fine to
include these changes and leave them disabled by default. For your
distribution, with a known environment, you
On Wed, Jul 21, 2010 at 2:08 PM, Bram Moolenaar wrote:
>
> We could wait for people to test this, but on the other hand if we
> want to do the same for ruby/tcl/mzscheme we need to do it now, next
> week I won't include patches like this.
It broke compiling using Make_cyg.mak for me. (Just to be
On 21 July 2010 21:36, Bram Moolenaar wrote:
>
> Björn wrote:
>>
>> Bram: could you indicate if there is any chance this is making it for
>> 7.3 (or at all)? It seems this feature would mostly be used by Mac
>> users (since "all" Macs have horizontal scrolling abilities) and a few
>> users have as
On Wed, 21 Jul 2010, Maxim Kim wrote:
Christian J. Robinson wrote:
Maxim Kim wrote:
3. :syntax on
Sorry, I missed that somehow. But you'd also need to turn filetype
plugins on (:filetype plugin on). The help ftplugin sets
'concellevel'.
Cut from the top post:
1. run gvim
2. :filetype p
James Vega wrote:
> On Mon, Jul 19, 2010 at 3:17 PM, Bram Moolenaar wrote:
> > If you can make this work with a configure argument, it's fine to
> > include these changes and leave them disabled by default. For your
> > distribution, with a known environment, you could enable them.
>
> Attache
GVim fails to compile with revision 2368:435b5c6a5191 under MinGW:
if_ole.cpp: In static member function 'static CVim* CVim::Create(int*)':
if_ole.cpp:144:19: error: cannot allocate an object of abstract type 'CVim'
if_ole.cpp:97:1: note: because the following virtual functions are
pure within '
2010/7/21 Bram Moolenaar :
>
> Maxim Kim wrote:
>
>> With the following minimal .vimrc and only builtin plugins I have
>> quite a strange behaviour with help on strdisplaywidth() topic.
>>
>> .vimrc:
>> set nocompatible
>> finish
>>
>>
>> 1. run gvim
>> 2. :filetype plugin on
>> 3. :syntax on
>> 4.
Björn wrote:
> >> Ok, here is the updated patch. I've renamed the keys as follows:
> >>
> >>
> >>
> >>
> >>
> >>
> >> These all scroll the _window_ in the direction indicated. So if I
> >> push UP on my scroll wheel, the window moves up but the lines are
> >> actually scrolled down (this is
Matt Wozniski wrote:
> On Wed, Jul 14, 2010 at 4:57 PM, Bram Moolenaar wrote:
> >
> > Matt Wozniski wrote:
> >
> > [about a patch to support #rrggbb in a terminal]
> >
> > Where can I find the latest version of this patch? Â I only see one that
> > is two years old.
>
> As Benjamin Haskell noted
Mikeyao wrote:
> Vim support many languages interface and I just found new lua
> interface added in 7.3. I think most programmers know javascript and
> like it, it's going to mainstream.
> Many web developers using vim, they know javascript well.
The reason people write Javascript is because it'
On Wed, Jul 14, 2010 at 4:57 PM, Bram Moolenaar wrote:
>
> Matt Wozniski wrote:
>
> [about a patch to support #rrggbb in a terminal]
>
> Where can I find the latest version of this patch? I only see one that
> is two years old.
As Benjamin Haskell noted, I decided to shoot for a vimscript
impleme
Lech Lorens wrote:
> On 17-Jul-2010 Bram Moolenaar wrote:
> >
> > Lech Lorens wrote (more than a year ago):
> >
> > > On 28-Mar-2009 Lech Lorens wrote:
> > > > Improved version of patch is attached. I took into consideration most of
> > > > the suggestions. I will be grateful for any more com
Christian J. Robinson wrote:
> Attached patch is for a fix to doc/editing.txt, under ":help :X",
> regarding the file magic lines.
Thanks!
> At least some versions of the file command allow you to add personal,
> custom magic lines to ~/.magic as well, but I didn't add that to help
> file.
James Vega wrote:
> The runtime/doc makefile doesn't express the required tags.ref
> pre-requisite for building the html files using makehtml.awk. When
> doing a parallel make, this can result in some of the html files not
> containing all the links that they should since tags.ref may not be
> g
Gary Johnson wrote:
> I found a bug in undo.c while trying to build Vim 7.3 for the first
> time on my Cygwin 1.5 system. The problem is that the condition of
> an 'if' contains a pair of parentheses, but only the closing
> parenthesis is contained within an #ifdef. I didn't see any reason
> fo
On 21 июл, 20:13, "Christian J. Robinson" wrote:
> On Tue, 20 Jul 2010, Maxim Kim wrote:
> >> Because you don't have syntax highlight enabled in your example,
> >> which turns off the conceal feature as well, since it uses the
> >> highlighting engine.
>
> > 3. :syntax on
>
> Sorry, I missed that
duffman wrote:
> Many thanks for your replies! I am working at a big corporation and
> the IT-powers that be have access to most root level modifications. I
> have read/write permissions on my home directory (/home/myName).
> Could I install the vim editor under my directory? If so, any pointers
Many thanks for your replies! I am working at a big corporation and
the IT-powers that be have access to most root level modifications. I
have read/write permissions on my home directory (/home/myName).
Could I install the vim editor under my directory? If so, any pointers
on what to do? Once down
Bram,
The runtime/doc makefile doesn't express the required tags.ref
pre-requisite for building the html files using makehtml.awk. When
doing a parallel make, this can result in some of the html files not
containing all the links that they should since tags.ref may not be
generated yet. Attached
Attached patch is for a fix to doc/editing.txt, under ":help :X",
regarding the file magic lines.
At least some versions of the file command allow you to add personal,
custom magic lines to ~/.magic as well, but I didn't add that to help
file.
- Christian
--
Christian J. Robinson -- http
On 2010年07月22日 00:03, Matt Wozniski wrote:
Please bottom post on this list... I'm reformatting...
On Wed, Jul 21, 2010 at 6:05 AM, mikeyao wrote:
On Jul 21, 5:38 pm, Bram Moolenaar wrote:
Mikeyao (?) wrote:
Why not javascript interface ?
The code has developed.
http://www.vim.org/scripts
I found a bug in undo.c while trying to build Vim 7.3 for the first
time on my Cygwin 1.5 system. The problem is that the condition of
an 'if' contains a pair of parentheses, but only the closing
parenthesis is contained within an #ifdef. I didn't see any reason
for the parentheses, so I removed
On Tue, 20 Jul 2010, Maxim Kim wrote:
Because you don't have syntax highlight enabled in your example,
which turns off the conceal feature as well, since it uses the
highlighting engine.
3. :syntax on
Sorry, I missed that somehow. But you'd also need to turn filetype
plugins on (:filetype
On Wednesday 21 July 2010 17:13:33 Bram Moolenaar wrote:
> Is there some specific reason you want to disable float support?
Yes; I can't imagine any reason I would ever want floating-point support in my
vimscripts, so as far as I'm concerned it's just a waste of space.
--
Sending me something
On 2010-07-21, duffman wrote:
> Hi,
>
> I tried to look up information online on this but wasn't able to find
> anything that worked. I used Vi at my old job and loved the editing
> features it provided. I've moved to a new place now and I am the only
> "developer" here. I logged into a SunOS U
On Wed, Jul 21, 2010 at 10:11 AM, duffman wrote:
> Hi,
>
> I tried to look up information online on this but wasn't able to find
> anything that worked. I used Vi at my old job and loved the editing
> features it provided. I've moved to a new place now and I am the only
> "developer" here. I log
> Can anyone please help make my vi editor colorful?
Hi, it is a big difference between 'vi' and 'vim'. You work with plain 'vi' as
being on solaris, probably. So the right answer should be 'install vim'.
Try http://sunfreeware.com/
After vim installation, I recommend:
:help coloring
And if it
Please bottom post on this list... I'm reformatting...
On Wed, Jul 21, 2010 at 6:05 AM, mikeyao wrote:
> On Jul 21, 5:38 pm, Bram Moolenaar wrote:
>> Mikeyao (?) wrote:
>> > Why not javascript interface ?
>>
>> > The code has developed.
>> >http://www.vim.org/scripts/script.php?script_id=2375
>>
Hi,
I tried to look up information online on this but wasn't able to find
anything that worked. I used Vi at my old job and loved the editing
features it provided. I've moved to a new place now and I am the only
"developer" here. I logged into a SunOS Unix box (bash shell) and
while things work
Maxim Kim wrote:
> With the following minimal .vimrc and only builtin plugins I have
> quite a strange behaviour with help on strdisplaywidth() topic.
>
> .vimrc:
> set nocompatible
> finish
>
>
> 1. run gvim
> 2. :filetype plugin on
> 3. :syntax on
> 4. :h strdisplaywidth()
> 5. navigate to s
Nico Raffo wrote:
> The :py3file command appears not to work as expected, specifically it
> seems like when you type
>
> :py3file foo.py
>
> Vim is running
>
> :py3 file foo.py
>
> Which gives the obvious syntax error
>
> File "", line 1
> file foo.py
>^
> SyntaxError: inva
Ron Aaron wrote:
> I understand I can do that; but that means I have to manually "fix" it
> on each new release from Bram :(
Is there some specific reason you want to disable float support?
--
TALL KNIGHT: When you have found the shrubbery, then you must cut down the
mightiest tre
On 21 июл, 13:59, Maxim Kim wrote:
> On 21 июл, 09:41, Maxim Kim wrote:
> > With the following minimal .vimrc and only builtin plugins I have
> > quite a strange behaviour with help on strdisplaywidth() topic.
>
> > .vimrc:
> > set nocompatible
> > finish
>
> > 1. run gvim
> > 2. :filetype plug
Vim support many languages interface and I just found new lua
interface added in 7.3. I think most programmers know javascript and
like it, it's going to mainstream.
Many web developers using vim, they know javascript well.
On Jul 21, 5:38 pm, Bram Moolenaar wrote:
> Mikeyao (?) wrote:
> > Why
On 21 июл, 09:41, Maxim Kim wrote:
> With the following minimal .vimrc and only builtin plugins I have
> quite a strange behaviour with help on strdisplaywidth() topic.
>
> .vimrc:
> set nocompatible
> finish
>
> 1. run gvim
> 2. :filetype plugin on
> 3. :syntax on
> 4. :h strdisplaywidth()
> 5. n
On 21/07/10 11:31, ron wrote:
I understand I can do that; but that means I have to manually "fix" it
on each new release from Bram :(
Now that Bram is using Mercurial, you can clone the Mercurial repo and
merge your local changes with that. I have two one-line changes in
feature.h myself, to
Mikeyao (?) wrote:
> Why not javascript interface ?
>
> The code has developed.
> http://www.vim.org/scripts/script.php?script_id=2375
I haven't actually heard from someone using it.
Also, I have no idea why someone would want to write plugins in
Javascript. Perhaps because it's the only lang
I understand I can do that; but that means I have to manually "fix" it
on each new release from Bram :(
--
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/maillist.php
On 21/07/10 08:08, ron wrote:
There is no configure option I can see to disable the 'floats'.
IIUC, there's no configure argument for that, but you can disable
floating-point in feature.h line 390:
/*
* +evalBuilt-in script language and expression evaluation,
*
52 matches
Mail list logo
