On the page
http://vimdoc.sourceforge.net/htmldoc/help.html#reference_toc
if you click the link 'index.txt', which purports to take you to an
alphabetical index of the commands, you end up on
http://vimdoc.sourceforge.net/htmldoc/index.html
which is 'help.txt', not an index.
/Don
--
You
FWIW, you have my vote for making this happen. I think it's not that
hard to make everyone happy on this subject by the mean of .vimrc
settings, like we have between vi and vim for :set compatible.
Wether we use structures or the byte 80 for special key is
implementation detail, I mean wether
Vim crash when opening the following xpm file.
http://sites.google.com/site/yukihironakadaira/100x100.xpm
100x100.xpm is 100x100 size with 1 different colors. I generated it
with the following code and converted to xpm with Gimp.
# Python + OpenCV
import cv
img = cv.CreateImage((100,
On Fri, Feb 18, 2011 at 05:35:38AM -0800, Philippe Vaucher wrote:
FWIW, you have my vote for making this happen. I think it's not that
hard to make everyone happy on this subject by the mean of .vimrc
settings, like we have between vi and vim for :set compatible.
:set compatible does suggest
On Fri, Feb 18, 2011 at 10:24 AM, Ben Fritz fritzophre...@gmail.com wrote:
On Feb 15, 10:48 am, Donald Allen donaldcal...@gmail.com wrote:
I'm a fairly recent convert to vim, after using emacs for many, many
years (I used the very first version of emacs, built on top of Teco,
on Tenex on a
On Fri, Feb 18, 2011 at 04:12:47PM +1100, Ben Schmidt wrote:
Plus, it's only the queue of incoming keypresses - that queue isn't
going to stay very big for very long.
It's not just the input queue that's in question here, it's everywhere
in Vim where keypresses are represented. For instance,
Hi,
v:count1 is set to 0 when I run the following (vim 7.3 patches 1-107):
vim -c 'echo v:count1'
I confirmed this with other people on #vim@freenode, do you get the same
behavior?
Cheers,
Israel
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
On Sat, Feb 19, 2011 at 12:01:01AM +0900, Yukihiro Nakadaira wrote:
Vim crash when opening the following xpm file.
http://sites.google.com/site/yukihironakadaira/100x100.xpm
100x100.xpm is 100x100 size with 1 different colors. I generated it
with the following code and converted to
Reply to message «Bug? v:count1 is set to 0»,
sent 19:26:23 18 February 2011, Friday
by Israel Chauca F.:
Confirmed: vim-7.3.125 (mercurial revision e44523d45bf5).
Original message:
Hi,
v:count1 is set to 0 when I run the following (vim 7.3 patches 1-107):
vim -c 'echo v:count1'
I
Israel Chauca wrote:
v:count1 is set to 0 when I run the following (vim 7.3 patches 1-107):
vim -c 'echo v:count1'
I confirmed this with other people on #vim@freenode, do you get the
same behavior?
v:count1 is only set when a command was given. Does this ever matter?
--
Luke Macken wrote:
The attached patch updates the spec.vim syntax to recognize the
%global RPM macro.
Did you try contacting the maintainer, Donovan Rebbechi?
--
press CTRL-ALT-DEL for more information
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///
Yukihiro Nakadaira wrote:
Vim crash when opening the following xpm file.
http://sites.google.com/site/yukihironakadaira/100x100.xpm
100x100.xpm is 100x100 size with 1 different colors. I generated it
with the following code and converted to xpm with Gimp.
# Python + OpenCV
For me it seems to hang. May just be very slow. It does open the GUI
window, your output suggest it doesn't.
I just tried the file. Opening Vim took about a minute with Vim running
at 100% CPU after which Vim became responsive. I then scrolled down by
repeating 99PageDown and just before I
vim is fine (syn on)
gvim is fine (syn off)
Can you confirm this?
Marc Weber
--
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 Fri, Feb 18, 2011 at 4:54 PM, Benjamin Fritz fritzophre...@gmail.com wrote:
On Fri, Feb 18, 2011 at 10:07 AM, Donald Allen donaldcal...@gmail.com wrote:
:ed foo/bar produces the message
foo/bar is a directory
whereas :ed foo/bar/ (which is what you get if you hit tab to complete)
On Feb 15, 8:48 am, Donald Allen donaldcal...@gmail.com wrote:
I'm a fairly recent convert to vim, after using emacs for many, many
years (I used the very first version of emacs, built on top of Teco,
on Tenex on a DEC PDP-10; I guess just dated myself!).
The issue: using gvim (I think the
16 matches
Mail list logo