.vim
Thus, I really don't think this should be failing.
I also tried using the latest MacVim and console vim on Mac OS X 10.9, and I
also tried Cygwin console vim on the same Windows 8.1 system, and none of those
failed.
Thanks!
Ben
--
--
You received this message from the "vim_d
Just had a feature idea, thought I'd throw it out here.
It would be nice if you could specify the various ++opt options to instruct vim
how to interpret the bytestreams of files opened right from the command-line.
Currently the only way to use ++opt options is when calling :edit or :read (as
fa
either; should we include a preprocessor
test to exclude the code if compiling for GUI mode?
3. I'm not sure about how much testing needs to be done for a new
patch (this is the first patch I've ever submitted); I've only tested
it on one Windows 7 machine.
Any feedback is appreciated
On Dec 26, 1:16 am, Tony Mechelynck
wrote:
> On 26/12/11 06:37, Ben wrote:
>
> > Hi vim_dev,
>
> > I always liked the feature in win32 console vim where the cursor
> > changed shape depending on what mode you're in. I recently switched to
> > using cygwin con
On Dec 26, 9:47 pm, Tony Mechelynck
wrote:
> On 26/12/11 19:22, Ben wrote:
>
> > On Dec 26, 1:16 am, Tony Mechelynck
> > wrote:
> >> On 26/12/11 06:37, Ben wrote:
>
> >>> Hi vim_dev,
>
> >>> I always liked the feature in win32 console v
On Sunday, June 2, 2013 12:24:11 AM UTC-5, MarcWeber wrote:
> ZyX told me that I should try to write the way the source code looks.
>
>
>
> Now I find that files mix tab with spaces etc.
>
>
>
> The src/README.txt talks about many things, but not about how to
>
> configure Vim to write Vim's
On Sunday, June 2, 2013 6:02:01 AM UTC-5, Leszek Świrski wrote:
> There is an issue with vim's python support on Windows, when one tries to use
> python libraries that require the MSVC 9.0 runtime. This has been observer in
> vim-ipython[1]. It can be easily reproduced with
>
> :py import uu
On Sunday, June 2, 2013 7:27:57 AM UTC-5, Bram Moolenaar wrote:
>
>
> This is much faster:
>
>
>
> [<]\@2<=[^ /!?<>"']\+
>
I didn't know you could do that! I have an older Vim installed on this computer
currently...is this a new feature, or just undocumented?
--
--
You received this
On Sunday, June 2, 2013 1:28:05 PM UTC-5, yega...@gmail.com wrote:
> Hi all,
>
>
>
> I am attaching a patch to add the :cdo and :ldo commands. The :cdo command
>
> can be used to execute commands over all the buffers in the quickfix list.
>
> The :ldo command can be used to execute commands ov
On Sunday, June 2, 2013 2:44:20 PM UTC-5, MarcWeber wrote:
> How to continue?
>
>
>
> Submit ideas here:
>
> http://vim-wiki.mawercer.de/wiki/vim74/devs-workflows.html
>
>
>
> mercurial lovers speak up and tell why you'd prefer keep using
>
> mercurial for exchanging patches. (I'm not talki
On Monday, June 3, 2013 4:16:12 AM UTC-5, Bram Moolenaar wrote:
> ZyX wrote:
>
>
>
> > On Jun 3, 2013 1:09 AM, "Bram Moolenaar" wrote:
>
> > >
>
> > >
>
> > > Glts wrote:
>
> > >
>
> > > > On Sunday, June 2, 2013 9:30:20 PM UTC+2, Bram Moolenaar wrote:
>
> > > > > Christian Brabandt wrote
On Monday, June 3, 2013 7:21:04 AM UTC-5, Josh wrote:
> On Jun 3, 2013, at 6:25 AM, LCD 47 wrote:
> > (1) Mercurial and Git are virtually identical to one another in terms of
> >features. There are, of course, differences, but they are largely
> >irrelevant to this discussion.
>
> I woul
Sorry for the duplicate, Bram. I meant to include the list and forgot to "reply
all".
On Mon, Jun 3, 2013 at 10:42 AM, Bram Moolenaar wrote:
>
> Ben Fritz wrote:
>
>> One problem with the todo list, is that it is not up-to-date until you
>> publish runtime files p
On Sunday, June 2, 2013 3:36:54 PM UTC-5, Grant Farnsworth wrote:
> > - ":set nonu nornu" means: I don't want any line numbers;
> > - ":set nu nornu" means: I want to see only absolute numbers;
> > - ":set nonu rnu" means: I want to see only relative numbers;
> > - ":set nu rnu" means: I want to ha
/limitation/weakness that needs to be
resolved, related to the interplay between tabstop and vartabstop. I
will try to look into this in the next few weeks, too, and write a
followup message to the mailing list.
Ben.
--
--
You received this message from the "vim_dev" maillist.
Do not
On Wednesday, June 5, 2013 12:55:00 AM UTC-5, kartikkg wrote:
> Tried to mail to this ndrochips
> @pcampbellafamily.mbiz but seems like that address is invalid.
>
It shows in his files as ndroch...@pcampbellafamily.mbiz.
Remove NOSPAM and it's a valid address.
--
--
You received this message
With each version of TOhtml I run a simple brute-force script at
https://code.google.com/p/vim-2html-test/ to exercise all the plugin options.
There is a .bat file for Windows and a .sh file for Linux.
With the same Vim version (patch 1115 I believe), regexpengine set to 1 takes
around 350 seco
On Friday, May 24, 2013 12:10:18 PM UTC-5, c00kiemon5ter wrote:
>
> colorscheme molokai
> set guifont=Cousine\ 10
>
> (that's the whole ~/.gvimrc)
>
> Upon opening gvim I got this: http://i.imgur.com/FfZHYCR.png
>
I can't see anything like this on Windows. Setting my font to Cousine in my
On Wednesday, June 5, 2013 10:34:38 AM UTC-5, c00kiemon5ter wrote:
>
>
> I don't think bad or even horrible antialiasing
>
> could cause that. It mostly looks like the
>
> font file is not read correctly.
>
>
Agree. I meant, maybe when the GUI is not actually running, Vim can't load
fonts w
On Wednesday, June 5, 2013 10:43:23 AM UTC-5, Charles Campbell wrote:
>
> I plan on trying your patch out soon, probably tonight (can't build vim
>
> on my SL6.3 at work properly, although I can build it on a SL6.3 system
>
> at home). Sounds like a good solution to me.
>
It looks like it b
I'm trying to compile Vim as a normal user, with python support, on a Solaris
machine at work. I have NO sudo access, and am trying to use a python I built
myself (the Python version on the server is 2.2, and IT will NOT change it).
Here is the configure command I used:
./configure --with-featu
I found this stackoverflow post:
http://stackoverflow.com/questions/3373914/compiling-vim-with-python-support
Which led me to look at src/auto/config.log
Here I see something suspicious:
configure:5416: checking if -pthread should be used
configure:5443: gcc -o conftest -g -O2 -pthread -L/usr
On Wednesday, June 5, 2013 5:27:27 PM UTC-5, Andrei Olsen wrote:
> On Wednesday, June 5, 2013 11:47:43 PM UTC+2, Ben Fritz wrote:
> > I found this stackoverflow post:
> > http://stackoverflow.com/questions/3373914/compiling-vim-with-python-support
> >
> > Which
On Wednesday, June 5, 2013 4:47:43 PM UTC-5, Ben Fritz wrote:
> configure:5452: checking if compile and link flags for Python are sane
> configure:5469: gcc -o conftest -g -O2
> -I/rfs/proj/cs_ifis_projects/Tools/Python/current/include/python2.7
> -DPYTHON_HOME=\"/rfs/proj/cs_if
On Wednesday, June 5, 2013 9:04:38 PM UTC-5, hiwa wrote:
> I have made and gotten 7.3.1119 from Mercurial on Ubuntu 10.10.
>
> Simple program exit via :q and :wq etc. freezes entire gvim.
>
> Edited result is not saved after a forced process killing.
>
>
>
> What could be the cause and the sol
On Thursday, June 6, 2013 3:08:24 AM UTC-5, Roland Eggner wrote:
> On 2013-06-05 Wednesday at 12:43 +0200 Bram Moolenaar wrote:
>
> > Roland Eggner wrote:
>
> > > After update 7.3.{865,969} I notice this regression:
>
> > > “:wviminfo! filename” writes only new history entries, misses old
>
> >
On Wednesday, June 5, 2013 5:43:40 PM UTC-5, Andrei Olsen wrote:
> On Thursday, June 6, 2013 12:32:41 AM UTC+2, Ben Fritz wrote:
> > On Wednesday, June 5, 2013 5:27:27 PM UTC-5, Andrei Olsen wrote:
> > > On Wednesday, June 5, 2013 11:47:43 PM UTC+2, Ben Fritz wrote:
> &g
On Friday, June 7, 2013 2:29:48 PM UTC-5, Dominique Pelle wrote:
> TOTAL COUNT MATCH SLOWEST AVERAGE NAME PATTERN
>
> 3.234792 47684 0 0.0028020.68 xmlSyncDT
>
> \_.\(
> [Snip]
>
>
> Clearly the top regexp (xmlSyncDT) stands out even
>
> if it
On Friday, June 7, 2013 8:49:12 PM UTC-5, MarcWeber wrote:
>
>
> I personally don't want to spend time on thinking about how to use
>
> malloc, realoc or such for simple things like lists, maps, ...
>
>
>
> Thus is there a standard way, a preprocessor like library which gets the
>
> job done
On Sunday, June 9, 2013 7:31:36 AM UTC-5, glts wrote:
>
> URI EmailDateSum3 URI|EmailWord
>
> re=1 16.73 13.844.08 34.65 29.430.49
>
> re=22.943.071.527.535.612.31
>
>
>
>
On Monday, June 10, 2013 5:55:16 AM UTC-5, Bram Moolenaar wrote:
> configure:5467: checking if compile and link flags for Python are sane
> configure:5484: gcc -o conftest -O2 -fno-strength-reduce -Wall
> -I/usr/include/python2.7 -DPYTHON_HOME=\"/usr\" -pthread
> -I/usr/local/include -L/usr/loc
On Monday, June 10, 2013 3:00:45 AM UTC-5, mattn wrote:
> Hi list.
>
> When completion popup is displayed, the popup window flicker with typing
> several keys.
>
> [snip]
>
> So I'm thinking it don't need to call update_screen(0) while completing.
> However, redrawing status_line is needed.
>
>
On Tuesday, June 11, 2013 5:25:42 AM UTC-5, mattn wrote:
> On Tuesday, June 11, 2013 1:33:45 PM UTC+9, v...@googlecode.com wrote:
> > Status: New
> > Owner:
> > Labels: Type-Defect Priority-Medium
> > New issue 141 by zulolox4...@gmail.com:
> >
> > http://code.google.com/p/vim/issues/detail?
On Monday, June 10, 2013 8:26:57 PM UTC-5, Andrei Olsen wrote:
> Also, though unrelated to this problem, older GCC compilers (version < 4) do
> not accept "-pthread" on Solaris, so to add support for multithreading using
> the POSIX threads library we need to use "-pthreads".
>
> I added a fix f
On Friday, June 7, 2013 12:32:35 PM UTC-5, Andrei Olsen wrote:
> On Thursday, June 6, 2013 7:47:56 PM UTC+2, Ben Fritz wrote:
> >
> > And, it still gets a compile error when checking for "sane" libraries
> > unless I remove that check.
> >
> > I atta
On Tuesday, June 11, 2013 11:43:30 AM UTC-5, Ben Fritz wrote:
>
> But the "sane" check still fails. I got a hint from here:
>
> http://mail.python.org/pipermail/distutils-sig/2002-January/002744.html
>
> The problem is in the escaping of the -DPYTHON_HOME flag. I had
On Tuesday, June 11, 2013 4:56:08 PM UTC-5, John Wiersba wrote:
>
> I run into several issues when editing/viewing files on a filesystem with
> 64-bit inodes on vim 7.3 (built from source) on AIX 6.1. I
> didn't see any mention of similar issues in the patches list. Have I missed
> something?
On Tuesday, June 11, 2013 4:56:08 PM UTC-5, John Wiersba wrote:
> --- Options ---
> ...
> compatible key= shellcmdflag=-c ttytype=xterm
I note you have 'compatible' set. Vim behaves much nicer with 'nocompatible',
but I doubt this is your issue. You might give it a s
On Monday, June 10, 2013 8:47:35 PM UTC-5, Hiroshi Shirosaki wrote:
>
> rubyPredefinedConstant pattern looks much slower with this file.
>
> syntime result:
>
> :set re=0
>
> TOTAL COUNT MATCH SLOWEST AVERAGE NAME PATTERN
> 0.073358 1870 0.0015260
On Tuesday, June 11, 2013 2:50:12 PM UTC-5, glts wrote:
> On Tue, Jun 11, 2013 at 5:18 PM, Ben Fritz wrote:
>
> > That pattern contains a few patterns using \@ > two characters before. They should probably be explicitly limited like
> > \@2 > byte-limiting behavior was
On Wednesday, June 12, 2013 12:13:48 AM UTC-5, Ben Fritz wrote:
> Isn't that first bit much too complicated? Am I missing something, or is this:
>
> \%(\%(\.\@
> equivalent to this:
>
> \%([^.]\.\_s*\)\@
> ?
>
Well, it's not quite equivalent. For examp
On Wednesday, June 12, 2013 2:30:37 AM UTC-5, Hiroshi Shirosaki wrote:
> On Wednesday, June 12, 2013 2:21:55 PM UTC+9, Ben Fritz wrote:
> > On Wednesday, June 12, 2013 12:13:48 AM UTC-5, Ben Fritz wrote:
> > > Isn't that first bit much too complicated? Am I missing somet
On Wednesday, June 12, 2013 11:11:57 AM UTC-5, Bram Moolenaar wrote:
>
> Although autoconf is used to make software portable, configure files
>
> themselves are written for a specific version of autoconf :-).
>
> Well, at least you can't use an old version.
>
Good to know, thanks. And thanks f
On Wednesday, June 12, 2013 1:08:22 PM UTC-5, LCD 47 wrote:
> > You can do it in one comparison with this trick:
> >
> > if ((unsigned)c - '0' < 10)
>
> Actually, the second version is a bit slower than the first. :) A
> comparison is exactly as fast as a subtraction of the same length, and
On Thursday, June 13, 2013 10:15:11 AM UTC-5, Ken Takata wrote:
> Hi Ajit,
>
> 2013/06/13 Thu 22:59:42 UTC+9 Ajit Thakkar wrote:
> > 32-bit gVim 7.3.1182 (features=normal) on 64-bit Win7+SP1 freezes when I
> > attempt to edit any file in a directory that is hard linked to another
> > directory.
On Friday, June 14, 2013 7:58:48 AM UTC-5, Christian Wellenbrock wrote:
> I attached a yaml file as example. Please open it with vim to test the
> highlighting speed. Scolling and searching is very slow. Tested on vim
> 7.3.1106
1106 is very old news for the new regex engine. At that point Bram
On Friday, June 14, 2013 11:49:25 AM UTC-5, Bram Moolenaar wrote:
> Christian Wellenbrock wrote:
>
>
>
> > I attached a yaml file as example. Please open it with vim to test the
>
> > highlighting speed. Scolling and searching is very slow. Tested on vim
>
> > 7.3.1106
>
>
>
> There have be
On Monday, June 17, 2013 2:34:00 PM UTC-5, Bram Moolenaar wrote:
>
> I do not like the idea of accessing functions with arbitrary names.
>
> I would rather also disallow:
>
> let dict['/foo'] = function('tr')
>
> Would that break any plugin?
>
I think of it as "accessing a dict element with
On Wednesday, June 19, 2013 8:13:55 PM UTC-5, kien wrote:
> While `\v(&&|str)` (order reversed) works and doesn't cause the error.
>
> Both expressions work with the old regexp engine.
While you shouldn't get an error message...I don't think that pattern is doing
what you think unless you're jus
On Wednesday, June 19, 2013 10:40:49 PM UTC-5, kien wrote:
> On Thursday, June 20, 2013 10:07:59 AM UTC+7, Ben Fritz wrote:
> > On Wednesday, June 19, 2013 8:13:55 PM UTC-5, kien wrote:
> > > While `\v(&&|str)` (order reversed) works and doesn't cause the error.
>
On Wednesday, June 19, 2013 11:19:44 PM UTC-5, kien wrote:
> On Thursday, June 20, 2013 11:06:20 AM UTC+7, Ben Fritz wrote:
> > If I escape the & characters as \&, this is exactly what I get.
>
> You didn't, and still doesn't need to escape & if using `\v(&a
On Tuesday, June 25, 2013 7:36:34 AM UTC-5, Christian Brabandt wrote:
> On Tue, June 25, 2013 13:16, Tony Mechelynck wrote:
>
> > IMHO the mention of s[ubstitute] and su[spend] in the POSIX manual is
>
> > where the bug lies, since it implies that :su would mean _both_ :suspend
>
> > and :substi
On Monday, June 17, 2013 2:34:00 PM UTC-5, Bram Moolenaar wrote:
>
> I do not like the idea of accessing functions with arbitrary names.
>
> I would rather also disallow:
>
> let dict['/foo'] = function('tr')
>
> Would that break any plugin?
>
Hi, Bram! I saw in your recent todo.txt update
On Tuesday, June 25, 2013 12:56:01 PM UTC-5, sxc...@g.rit.edu wrote:
>
> Is there any movement with this patch? What are Bram's thoughts on it?
>
Bram's thoughts were that he doesn't want any new option for this.
But patch 7.3.1115 changes the 'number' and 'relativenumber' options so that
inst
eteen and (inner html)
>
> > 3. Paste into my blog entry
>
> >
>
> > But in latest TOHtml added . I
>
> > don't want this part in my use-case. So could you let me know the way
>
> > to get old style format?
>
>
>
> I had t
On Thursday, June 27, 2013 2:35:04 PM UTC-5, Andy Wokula wrote:
> Am 26.06.2013 20:04, schrieb Bram Moolenaar:
>
> > Patch 7.3.1249
>
> > Problem:Modeline not recognized when using "Vim" instead of "vim".
>
> > Solution: Also accept "Vim".
>
> > Files: src/buffer.c
>
>
>
> -1
On Thursday, June 27, 2013 3:29:56 PM UTC-5, Bram Moolenaar wrote:
> Ben Fritz wrote:
>
> > On Thursday, June 27, 2013 2:35:04 PM UTC-5, Andy Wokula wrote:
> > >
> > > I don't want lines starting with or containing "Vim:" to define a
> > >
On Wednesday, July 3, 2013 10:14:24 AM UTC-5, Bram Moolenaar wrote:
> Patch 7.3.1297
>
> Problem:findfile() directory matching does not work when a star follows
>
> text. (Markus Braun)
>
> Solution: Make a wildcard work properly. (Christian Brabandt)
>
When looking into the bu
UTC-5, Ben Fritz wrote:
> I use the delimitMate plugin by Israel Chauca Fuentes:
>
>
>
> http://www.vim.org/scripts/script.php?script_id=2754
>
> https://github.com/Raimondi/delimitMate
>
>
>
> I found this plugin to be "the best" at automatical
On Saturday, July 6, 2013 6:58:56 AM UTC-5, Zulox4 wrote:
> Hello,
>
> Could you add paredit : http://www.vim.org/scripts/script.php?script_id=3998
> to the vim plugin runtime files ?
>
> Thanks !
Does that belong at the list here?
http://vim.wikia.com/wiki/Automatically_append_closing_charac
On Tuesday, July 9, 2013 10:13:22 AM UTC-5, Bram Moolenaar wrote:
> Ben Fritz wrote:
>
> > I don't remember how setline() solves the problem, but just returning
>
> > cursor sequences doesn't work, because it breaks undo/redo/repeat.
>
>
>
> Yeah, th
On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote:
>
> Perhaps we can somehow detect that CTRL-R = had the side effect of
>
> changing the text and then split undo. When it only returns the text to
>
> be inserted, there is no need to split undo.
>
Even though it won't fix it a
On Thursday, July 11, 2013 10:45:16 AM UTC-5, Christian Brabandt wrote:
> On Thu, July 11, 2013 17:36, Ben Fritz wrote:
>
> > On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote:
>
> >>
>
> >> Perhaps we can somehow detect
On Monday, July 15, 2013 9:31:00 AM UTC-5, ZyX wrote:
> I would vote against any development process that uses patches, be it current
> one, suggested two-eye system or anything else.
>
>
>
> The two-eye system looks reasonable, but it should be applied to PR’s (commit
> series requested for i
On Monday, July 15, 2013 11:33:55 AM UTC-5, ZyX wrote:
> > Since we're using Mercurial, and Bram wants to allow email submissions, a
> > developer can email a "bundle" if he/she doesn't have/want access to a
> > public repository. Then just the commits required for the fix (with some
> > commit
On Monday, July 15, 2013 12:27:03 PM UTC-5, ZyX wrote:
> > > With bundles one still needs to repost each time he has an update (common
> > > for emailed bundles and diff).
> >
> > I view that as a good thing. You'll need to post anyway when you make an
> > update, otherwise nobody knows about it
On Tuesday, July 16, 2013 9:16:09 PM UTC-5, MarcWeber wrote:
> Excerpts from Tony Mechelynck's message of Wed Jul 17 03:45:35 +0200 2013:
>
> > You can share them in diff format, just like the patches that I see on
>
> > vim_dev.
>
> I'm talking about "hg pull" like sharing.
>
>
>
> > URL?
>
On Wednesday, July 17, 2013 1:20:15 AM UTC-5, Ingo Karkat wrote:
> On 17-Jul-2013 07:58 +0200, Ron Aaron wrote:
>
>
>
> > I (and my colleagues) often need to view extremely large log files (>
>
> > 1G). From force of habit we use vim; but vim takes a very long time
>
> > to open huge files.
>
On Tuesday, July 16, 2013 9:29:19 PM UTC-5, v...@googlecode.com wrote:
>
> I tested with vim 7.3.822 on win7 this config:
>
> :ver
>
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 17 2013 03:39:13)
>
> MS-Windows 32-bit console version
>
> Included patches: 1-822
>
> Compiled by g_user7@w
On Wednesday, July 17, 2013 11:54:59 AM UTC-5, Mike Williams wrote:
> On 17/07/2013 17:13, Benjamin Fritz wrote:
>
> > On Wed, Jul 17, 2013 at 10:49 AM, Mike Williams
>
> > wrote:
>
> >>
>
> >> Does anyone have hard numbers? I have just loaded an ~900MB PDF file in
> >> ~7s
>
> >> (Win7 x64
On Wednesday, July 17, 2013 2:51:24 PM UTC-5, Zulox4 wrote:
>
> I think that the problem is result of "fileencoding" or "utf8 encoding"
> options.
>
> I found another problem:
>
> 1. I have 1 line in the buffer:
> s\x6fme\tt\x65xt\n\"Sa\155ba\u201d: net\\share
>
> 2.After these commands
On Wednesday, July 17, 2013 5:42:28 PM UTC-5, Zulox4 wrote:
> > Please see http://vim.wikia.com/wiki/Working_with_Unicode
>
>
>
> I would like to initialize in vim (code), like the linux version, not with
> "vimrc" file config.
>
> Thanks for helping !
Vim gets its default 'encoding' setting
On Thursday, July 18, 2013 3:15:22 PM UTC-5, Marcin Szamotulski wrote:
> On 11:15 Thu 18 Jul , studog wrote:
>
> > This morning I noticed that the svn syntax file isn't quite correct; in a
> > few places the regex
>
> > ^--.*--$
>
> > is used to find the commit message delimiter.
>
> >
>
On Friday, July 19, 2013 8:59:38 AM UTC-5, Bram Moolenaar wrote:
>
>
>
> Does the pattern actually match in the wrong place?
>
>
TortoiseSVN generates commit comments like this whenever you merge:
Merged revision(s) {range} from {branch path}:
change 1 description
change
On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
> On windows 7 64-bit I get this behaviour both in gvim and vim.
> The options I have in the vimrc file are read, so this seems like a bug.
>
> Regards
> Andreas Stabel
Does your .vimrc show up in the output of :scriptnames?
What does ":verb
> *abandon*
> Vim remembers whether you have changed the buffer. You are protected from
> losing the changes you made. If you try to quit without writing, or want to
> start editing another file, Vim will refuse this. In order to overrule thi
On Monday, July 29, 2013 11:39:11 AM UTC-5, Stephen Lee wrote:
> On Monday, July 29, 2013 9:51:43 PM UTC+8, Ben Fritz wrote:
> > On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
> > > On windows 7 64-bit I get this behaviour both in gvim and vim.
> > > The optio
On Wednesday, July 31, 2013 9:37:24 AM UTC-5, Christian Brabandt wrote:
> On Tue, July 16, 2013 16:57, Benjamin Fritz wrote:
>
> > Eric Van Dewoestine found this while investigating an eclim issue I was
>
> having.
>
> > When 'autochdir' is set, calling setbufvar() changes Vim's current
>
> dir
On Wednesday, July 31, 2013 10:31:54 AM UTC-5, Christian Brabandt wrote:
> On Wed, July 31, 2013 17:17, Ben Fritz wrote:
>
> > A while ago there was a similar problem where :vimgrep was causing
>
> > directory changes due to 'autochdir'. The fix for :vimgrep also h
On Wednesday, July 31, 2013 8:41:21 PM UTC-5, Richard wrote:
> If you insert or delete lines, mostly the correct error location is still
>
> found because hidden marks are used. Sometimes, when the mark has been
>
> deleted for some reason, the message "line changed" is shown to warn you
>
> t
On Thursday, August 1, 2013 11:28:45 AM UTC-5, David Fishburn wrote:
> > 2. If your task bar is at the top of your screen (instead of the default
> > bottom) the "X" to close the window is also not visible. Because it is not
> > visible, you cannot "move" the window to get access to it.
> > A
On Sunday, August 4, 2013 2:53:39 PM UTC-5, Andy Wokula wrote:
>
>
> The current version is a descendant of
>
> http://vim.sf.net/scripts/script.php?script_id=2075
>
> It's very different from the original version by J. Zellner.
>
How long ago did "the original version" get replaced with your
On Tuesday, August 6, 2013 11:21:02 AM UTC-5, Benjamin R. Haskell wrote:
> On Tue, 6 Aug 2013, Dimitar DIMITROV wrote:
>
>
>
> > Hi all,
>
> >
>
> > If you open the latest vim (vim -nNX -u NONE) and insert these lines:
>
> >
>
> > .jpg 01;35
>
> > .jpeg 01;35
>
> > .gif 01;35
>
> > .b
On Thursday, August 8, 2013 9:27:27 AM UTC-5, Dimitar DIMITROV wrote:
> As per the subject :)
>
Verified that . has no effect after a gUgn that capitalized a match for the
last search, on 7.3.822 Windows, and also 7.4b.14 on Solaris.
--
--
You received this message from the "vim_dev" maillis
On Thursday, August 8, 2013 11:37:38 AM UTC-5, Bram Moolenaar wrote:
> Dimitar Dimitrov wrote:
>
>
>
> > >> As per the subject :)
>
> > >>
>
> > >
>
> > >Verified that . has no
>
> > effect after a gUgn that capitalized a match for the last search, on
>
> > 7.3.822 Windows, and also 7.4
On Friday, August 9, 2013 9:52:58 AM UTC-5, Dimitar DIMITROV wrote:
> Hi,
>
>
> First vim -nNX -u NONE ad :se ve=all
> Then enter the following test with X representing the cursor:
>
>
> if {
>
>
>
>
> X
>
>
>
>
> }
>
>
> Now vaB is wrong
>
I don't see anything wrong. F
On Friday, August 9, 2013 11:20:37 AM UTC-5, Dimitar DIMITROV wrote:
> >I don't see anything wrong. For me it selects all text from the opening { to
> >the closing }. What do you
> see?
> >
> >I tried gvim 7.3.822 on Windows, and also vim (not gvim) 7.4b.14 on Solaris,
> >both with "Huge" featur
On Sunday, August 11, 2013 12:52:16 PM UTC-5, v...@googlecode.com wrote:
> Comment #7 on issue 28 by brammool...@gmail.com: out of the box, gVim
>
> 7.3.46 for Win32 cannot write swap files on Windows 7
>
> http://code.google.com/p/vim/issues/detail?id=28
>
>
>
> I do not see the problem "ou
On Wednesday, August 14, 2013 10:49:17 AM UTC-5, John Szakmeister wrote:
> On Mon, Aug 12, 2013 at 9:49 PM, John Szakmeister
> wrote:
>
> > All,
>
> >
>
> > I've been working on some vimscript to help expand an UltiSnips
>
> > template for a new file and ran across an interesting bug.
>
> >
On Wednesday, August 14, 2013 4:34:12 PM UTC-5, Christian Brabandt wrote:
> On Di, 13 Aug 2013, Christian Brabandt wrote:
>
>
>
> > On Tue, August 13, 2013 01:00, Einar Lielmanis wrote:
>
> > > Encrypted file contents are destroyed, if something (e.g autocmd)
>
> > > triggers write event, whil
On Thursday, August 15, 2013 10:02:36 PM UTC-5, DrChip wrote:
> ZyX wrote:
>
> > I see that all g:vimsyn_embed flags say things like �embed � **(but
> > only if vim supports it)**�. This is ridiculous:
>
> Ah, I disagree -- not ridiculous at all. What's ridiculous is to assume
>
> that
On Friday, August 16, 2013 9:06:41 AM UTC-5, Albert Simenon wrote:
> Installed Vim7.3 without any problems on Solaris 9.
>
> However when i try to install Vim7.4 on Solaris 9 i run into issues. With
> default configure options i get an error on
>
> error: 'acl_t' undeclared
>
Well rats, I tho
On Saturday, August 17, 2013 5:22:35 PM UTC-5, John Szakmeister wrote:
> On Wed, Aug 14, 2013 at 12:02 PM, Ben Fritz wrote:
>
> [snip]
>
> > Otherwise, I think --remote commands internally use the :drop command to
> > edit a file. You can see whether you can reproduce
On Saturday, August 31, 2013 2:24:23 PM UTC-5, ZyX wrote:
> 1. When using concealed characters color that extends past the end of line
> (i.e. diff color) shows different line end positions:
> http://img-fotki.yandex.ru/get/6704/9151298.3/0_9e202_6394ebc0_orig.png (also
> attached image 1.png).
On Sunday, September 1, 2013 8:42:25 PM UTC-5, Geoff Greer wrote:
> This patch adds asynchronous functions to vimscript. If you want to perform
> an action in 700ms, simply:
>
> let timeout_id = settimeout(700, 'echo("hello")')
>
> To cancel the timeout before it's fired:
>
> canceltimeout(time
On Tuesday, September 3, 2013 1:17:59 PM UTC-5, Bjorn Tipling wrote:
> I am pretty excited about this patch and hope it makes it in.
>
>
> Ben, why should asynchronous receive any type of restriction not already
> placed on code that runs some milliseconds after a key press (an e
On Tuesday, September 3, 2013 1:53:31 PM UTC-5, kans wrote:
> On Tuesday, September 3, 2013 9:04:40 AM UTC-7, Ben Fritz wrote:
> > On Sunday, September 1, 2013 8:42:25 PM UTC-5, Geoff Greer wrote:
> > > This patch adds asynchronous functions to vimscript. If you want to
> >
On Wednesday, August 28, 2013 11:53:32 PM UTC-5, Dmitry Frank wrote:
> Hello.
>
>
> I used very old Vim 7.3.46 before (on Windows), now I tried Vim 7.4, and I
> have an issue with popup-menu.
>
> Say, I have popup-menu with three items: "one", "two", "three".
>
>
>
> In Vim 7.3, when I type
On Tuesday, September 3, 2013 3:30:51 PM UTC-5, ZyX wrote:
>
> The problem here is not gaps, they are standable. In fact, I have gaps
> problem with these characters too, though it is different gaps problem (gap
> between input with sign or line number and adjacent lines). The real problem
> is
On Tuesday, September 3, 2013 9:04:38 PM UTC-5, Shougo wrote:
> 2013年8月29日木曜日 13時53分32秒 UTC+9 Dmitry Frank:
>
> > Hello.
>
> >
>
> >
>
> > I used very old Vim 7.3.46 before (on Windows), now I tried Vim 7.4, and I
> > have an issue with popup-menu.
>
> >
>
> > Say, I have popup-menu with
1 - 100 din 1448 matches
Mail list logo
