On 21 июл, 10:32, "Christian J. Robinson" wrote:
> On Tue, 20 Jul 2010, Maxim Kim wrote:
> > On 21 июл, 09:58, James Vega 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. :syn
On Tue, 20 Jul 2010, Maxim Kim wrote:
On 21 июл, 09:58, James Vega wrote:
See ":help new-conceal" for more information.
But as I pointed in PS block there is no 'shrink and widen'
behaviour if I run vim with -u NORC.
And I do not move cursor out of that line -- I do move it left and
right
On 21 июл, 09:58, James Vega wrote:
> This is due to the new conceal feature. The tags in Vim's help files
> are surrounded by ||. When your cursor is on a line with tags, the ||
> are displayed but highlighted using the Ignore group so they blend in
> with the background. When your cursor m
There is no configure option I can see to disable the 'floats'.
--
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 Tue, Jul 20, 2010 at 10:41:27PM -0700, 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.
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 strchars() function
6. press h several times t
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: invalid syntax
Vim 7.3b from fresh pull from hg repos
On Jul 20, 4:42 pm, "Christian J. Robinson" wrote:
>
> And before someone responds to point it out to me: Yes, I'm aware of
> the drawback of GPG/PGP files being decrypted to disk and being edited
> "in the clear" with Vim. If someone that determined manages to get
> physical access to my hard
Why not javascript interface ?
The code has developed.
http://www.vim.org/scripts/script.php?script_id=2375
--
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 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 comments.
> >
> > I found an invalid
On Tue, Jul 20, 2010 at 2:12 PM, Bram Moolenaar wrote:
>
> Christian Robinson wrote:
>> Also, the information for the "file" command's magic file under ":help
>> :X" needs to be updated. This worked for me (without the leading
>> spaces, of course):
>>
>> 0 string VimCrypt~ Vim encrypt
On Tue, 20 Jul 2010, Bram Moolenaar wrote:
Christian Robinson wrote:
On Tue, 20 Jul 2010, Bram Moolenaar wrote:
Before I realized what had happened I thought I'd lost a file (no
big deal, I just went to my backup).
You don't look at the text after doing ":e"? I think it's obvious
that so
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
>> 2348:586a459f3980 FREEZE (BUG)
>> 2347:8878a9f8db87 OK
>>
>> So the change which introduces the bug is this one:
>>
>> changeset: 2348:586a459f3980
>> branch: vim73
>> user: Bram Moolenaar
>> date: Mon Jul 19 20:13:22 2010 +0200
>> files: runtime/doc/options.txt s
Dominique Pellé wrote:
> >> Hi
> >>
> >> Vim-7.3b (2361:6cee3bf00495) freezes and use 100% of
> >> the CPU when I do this:
> >>
> >> 1) Download 3 sample files:
> >>
> >> $ wget http://dominique.pelle.free.fr/bug-vim-freeze/1
> >> $ wget http://dominique.pelle.free.fr/bug-vim-freeze/2
> >> $ wg
Charles Campbell wrote:
> Dominique Pellé wrote:
>>
>> Hi
>>
>> Vim-7.3b (2361:6cee3bf00495) freezes and use 100% of
>> the CPU when I do this:
>>
>> 1) Download 3 sample files:
>>
>> $ wget http://dominique.pelle.free.fr/bug-vim-freeze/1
>> $ wget http://dominique.pelle.free.fr/bug-vim-freeze/2
Dominique Pelle wrote:
> Vim-7.3b (2361:6cee3bf00495) freezes and use 100% of
> the CPU when I do this:
>
> 1) Download 3 sample files:
>
> $ wget http://dominique.pelle.free.fr/bug-vim-freeze/1
> $ wget http://dominique.pelle.free.fr/bug-vim-freeze/2
> $ wget http://dominique.pelle.free.fr/
On 19 July 2010 15:45, Benjamin R. Haskell wrote:
> On Sun, 18 Jul 2010, 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 u
Bram Moolenaar wrote:
That's easy to fix. I'll do that now.
Great, thanks!
- Peter Odding
--
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
Am 20.07.2010 13:30, schrieb Bram Moolenaar:
James -
I wonder if you noticed this problem: When I tear-off a menu in GTK, for
example the Help menu, the buttons don't do anything.
I have the same problem in Vim 7.2 and 7.3b, it might have something to
do with the GTK version. I can't recall w
On 20/07/10 13:30, Bram Moolenaar wrote:
James -
I wonder if you noticed this problem: When I tear-off a menu in GTK, for
example the Help menu, the buttons don't do anything.
I have the same problem in Vim 7.2 and 7.3b, it might have something to
do with the GTK version. I can't recall when
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.
Attached patch enables dynamic loading
Dominique Pellé wrote:
Hi
Vim-7.3b (2361:6cee3bf00495) freezes and use 100% of
the CPU when I do this:
1) Download 3 sample files:
$ wget http://dominique.pelle.free.fr/bug-vim-freeze/1
$ wget http://dominique.pelle.free.fr/bug-vim-freeze/2
$ wget http://dominique.pelle.free.fr/bug-vim-free
Christian Robinson wrote:
> On Tue, 20 Jul 2010, Bram Moolenaar wrote:
>
> > I have just submitted a patch that changes the 'cryptmethod' option
> > from local to a buffer to global-local. This makes it possible to
> > set a default value for new files in your vimrc file.
>
> This works for
Yukihiro Nakadaira wrote:
> On 2010年07月20日 20:30, Bram Moolenaar wrote:
> >
> > James -
> >
> > I wonder if you noticed this problem: When I tear-off a menu in GTK, for
> > example the Help menu, the buttons don't do anything.
> >
> > I have the same problem in Vim 7.2 and 7.3b, it might ha
Hi
Vim-7.3b (2361:6cee3bf00495) freezes and use 100% of
the CPU when I do this:
1) Download 3 sample files:
$ wget http://dominique.pelle.free.fr/bug-vim-freeze/1
$ wget http://dominique.pelle.free.fr/bug-vim-freeze/2
$ wget http://dominique.pelle.free.fr/bug-vim-freeze/3
2) use the followin
On Tue, 20 Jul 2010, Bram Moolenaar wrote:
I have just submitted a patch that changes the 'cryptmethod' option
from local to a buffer to global-local. This makes it possible to
set a default value for new files in your vimrc file.
This works for me, thank you.
Since the number value was cry
On 20 July 2010 13:10, Nazri Ramliy wrote:
> On Tue, Jul 20, 2010 at 8:06 AM, Nazri Ramliy wrote:
>> On Tue, Jul 20, 2010 at 12:47 AM, björn wrote:
>>> Oh, I didn't realize that. Well, I can confirm that ":fin" behaves
>>> identical to ":tabf" (duplicate entries).
>>
>> I can reproduce the dupl
Peter Odding wrote:
> In my ~/.vimrc I have :set nomh so I never noticed the following IMHO
> confusing behavior until I was testing one of my Vim plug-ins with the
> command "gvim -u NONE -U NONE --noplugin -N":
>
> When Vim started my mouse cursor was hidden (because mh is on by default
> i
James Vega wrote:
> On Tue, Jul 20, 2010 at 7:30 AM, Bram Moolenaar wrote:
> > I wonder if you noticed this problem: When I tear-off a menu in GTK, for
> > example the Help menu, the buttons don't do anything.
>
> Testing with a self-built 7.3b and Debian's latest Vim 7.2 packages,
> tear-off m
On Tue, Jul 20, 2010 at 8:06 AM, Nazri Ramliy wrote:
> On Tue, Jul 20, 2010 at 12:47 AM, björn wrote:
>> Oh, I didn't realize that. Well, I can confirm that ":fin" behaves
>> identical to ":tabf" (duplicate entries).
>
> I can reproduce the duplicate entries.
>
> I'll look into this.
Attached p
Hi,
I'm the developer of a file type plugin for R language:
http://www.vim.org/scripts/script.php?script_id=2628
The plugin includes a script to indent R code and I would like to
propose the inclusion of the script in the Vim' indent directory.
The plugin also has a syntax script for .Rout file
On 2010年07月20日 20:30, Bram Moolenaar wrote:
James -
I wonder if you noticed this problem: When I tear-off a menu in GTK, for
example the Help menu, the buttons don't do anything.
I have the same problem in Vim 7.2 and 7.3b, it might have something to
do with the GTK version. I can't recall wh
Nazri Ramliy wrote:
> On Tue, Jul 20, 2010 at 8:06 AM, Nazri Ramliy wrote:
> > On Tue, Jul 20, 2010 at 12:47 AM, björn wrote:
> >> Oh, I didn't realize that. Well, I can confirm that ":fin" behaves
> >> identical to ":tabf" (duplicate entries).
> >
> > I can reproduce the duplicate entries.
>
I have just submitted a patch that changes the 'cryptmethod' option from
local to a buffer to global-local. This makes it possible to set a
default value for new files in your vimrc file.
For global-local options it's necessary to have a value that indicates
the global value needs to be used. A
On 20/07/2010 09:03 a.m., Cesar Romani wrote:
> I'm using MinGW with gcc 4.5.0 on Win XP.
> Compiling to gvim.exe is fine but compiling to vim.exe gives:
>
>
> ...
> gcc -c -Iproto -DWIN32 ... option.c -o objZ/option.o
> option.c: In function 'ExpandSettings':
> option.c:10281
On Tue, Jul 20, 2010 at 7:30 AM, Bram Moolenaar wrote:
> I wonder if you noticed this problem: When I tear-off a menu in GTK, for
> example the Help menu, the buttons don't do anything.
Testing with a self-built 7.3b and Debian's latest Vim 7.2 packages,
tear-off menus work fine for me. I ran “g
On Jul 20, 3:49 am, "Brenner, Matthias"
wrote:
>
> I'm sorry, but I can't find anything regarding Windows 7 compatibility. Is
> the current version 7.2.446 compatible with Windows 7?
>
It looks like the closest I can find in Vim's help documents is :help
MS-Windows (execute that command in Vim
I'm using MinGW with gcc 4.5.0 on Win XP.
Compiling to gvim.exe is fine but compiling to vim.exe gives:
...
gcc -c -Iproto -DWIN32 ... option.c -o objZ/option.o
option.c: In function 'ExpandSettings':
option.c:10281:1: internal compiler error: Segmentation fault
make: *** [ob
On Jul 19, 11:01 pm, Masatake YAMATO wrote:
> > I think the following meta information might
> > be nice to have:
>
> > * Syntax of buffer, or comma-separated syntax list if more than one
> > buffer
> > * Version of the 2html script (I plan to add this in my next update)
> > * Comma-separated li
James -
I wonder if you noticed this problem: When I tear-off a menu in GTK, for
example the Help menu, the buttons don't do anything.
I have the same problem in Vim 7.2 and 7.3b, it might have something to
do with the GTK version. I can't recall when it stopped working.
Can others reproduce t
Bram Moolenaar wrote:
The documentation is too short. Looking at it I have many questions:
- Does this change the text in the buffer? I suppose not, then what
happens when the text is redisplayed?
Since the data is written directly to the screen, the displayed
data is lost after a redraw. N
Hi,
It seems that DirDiff is not yet working with the latest Gvim7.3.a
released by Bram when I open a new line of two files that are
different.
I don't understand cause it says that b_currentDiff is not set.
Thanks
--
You received this message from the "vim_dev" maillist.
Do not top-post! T
[redirected to vim-dev]
Marko Mahnic wrote:
> On 18. 07. 2010 22:51, Bram Moolenaar wrote:
> >
> > Thanks. I'll add a note in the todo list. I don't expect to include
> > this soon, thus keep working on it.
> >
>
> This patch adds the python_screen feature to python and python3.
> Examples ar
Hi list,
In my ~/.vimrc I have :set nomh so I never noticed the following IMHO
confusing behavior until I was testing one of my Vim plug-ins with the
command "gvim -u NONE -U NONE --noplugin -N":
When Vim started my mouse cursor was hidden (because mh is on by default
in nocp mode) and this
On Tue, Jul 20, 2010 at 12:47 AM, björn wrote:
> Oh, I didn't realize that. Well, I can confirm that ":fin" behaves
> identical to ":tabf" (duplicate entries).
I can reproduce the duplicate entries.
I'll look into this.
nazri.
--
You received this message from the "vim_dev" maillist.
Do not
Dimitar Dimitrov wrote:
> I wrote:
>
> > Dimitar Dimitrov wrote:
> >
> > > I always have 'cursorline' set.
> > >
> > > Try this: :h'exrc
> > >
> > > Setting the cursor on this line...:
> > >
> > >setting the 'secure' option (see initialization). Using a local
> > >
> > > ...makes it move
> I'm sorry, but I can't find anything regarding Windows 7 compatibility. Is
> the current version 7.2.446 compatible with Windows 7?
Yes.
--
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 h
-Original Message-
From: Tony Mechelynck [mailto:antoine.mechely...@gmail.com]
Sent: Monday, July 19, 2010 5:59 PM
To: vim_dev@googlegroups.com
Cc: Brenner, Matthias
Subject: Re: Windows 7 compatibility of VIM / GVIM
On 19/07/10 11:01, Brenner, Matthias wrote:
> Dear Product Supporters,
49 matches
Mail list logo
