Re: Don't set "text" filetype for files that look like help files

2015-10-22 Fir de Conversatie glts
On Wednesday, October 21, 2015 at 11:51:04 PM UTC+2, Gary Johnson wrote: > On 2015-10-21, glts wrote: > > On Wednesday, October 21, 2015 at 8:32:32 PM UTC+2, Gary Johnson wrote: > > > On 2015-10-21, glts wrote: > > > > On Tuesday, October 20, 2015 at 8:47:27 PM UTC+2

Re: Don't set "text" filetype for files that look like help files

2015-10-21 Fir de Conversatie glts
On Wednesday, October 21, 2015 at 8:32:32 PM UTC+2, Gary Johnson wrote: > On 2015-10-21, glts wrote: > > On Tuesday, October 20, 2015 at 8:47:27 PM UTC+2, ZyX wrote: > > > 2015-10-20 21:11 GMT+03:00 glts <676c7...@gmail.com>: > > > > In a plain Vim install

Re: Don't set "text" filetype for files that look like help files

2015-10-21 Fir de Conversatie glts
On Tuesday, October 20, 2015 at 8:47:27 PM UTC+2, ZyX wrote: > 2015-10-20 21:11 GMT+03:00 glts <676c7...@gmail.com>: > > In a plain Vim installation, if I have a personal ftplugin > > ~/.vim/ftplugin/text.vim that contains the line > > > > setlocal ex

Re: Don't set "text" filetype for files that look like help files

2015-10-20 Fir de Conversatie glts
On Tuesday, October 20, 2015 at 8:47:27 PM UTC+2, ZyX wrote: > 2015-10-20 21:11 GMT+03:00 glts <676c7...@gmail.com>: > > In a plain Vim installation, if I have a personal ftplugin > > ~/.vim/ftplugin/text.vim that contains the line > > > > setlocal ex

Don't set "text" filetype for files that look like help files

2015-10-20 Fir de Conversatie glts
In a plain Vim installation, if I have a personal ftplugin ~/.vim/ftplugin/text.vim that contains the line setlocal expandtab then 'expandtab' will be on in Vim "help" files. It would be better not to apply settings for "text" files to help files. Would this be an acceptable fix? Alternat

Re: Unexpected result when using getreg() with three arguments

2015-10-07 Fir de Conversatie glts
On Wednesday, October 7, 2015 at 12:28:19 AM UTC+2, ZyX wrote: > 2015-10-05 19:18 GMT+03:00 glts <676c7...@gmail.com>: > > On Sunday, October 4, 2015 at 11:38:26 PM UTC+2, ZyX wrote: > >> 2015-10-05 0:02 GMT+03:00 glts <676c7...@gmail.com>: > >> > '

Re: Unexpected result when using getreg() with three arguments

2015-10-05 Fir de Conversatie glts
On Sunday, October 4, 2015 at 11:38:26 PM UTC+2, ZyX wrote: > 2015-10-05 0:02 GMT+03:00 glts <676c7...@gmail.com>: > > 'getreg(regname, 1, 1)' returns different lists for the same selection > > in characterwise and linewise mode. Why? > > > > To reprodu

Unexpected result when using getreg() with three arguments

2015-10-04 Fir de Conversatie glts
'getreg(regname, 1, 1)' returns different lists for the same selection in characterwise and linewise mode. Why? To reproduce: - Do 'Vy' on one line of text, then run :echo getreg('"', 1, 1). The result is ['text']. - Do '0v$y' on one line of text, then again run :echo getreg('"', 1, 1). The re

Incomplete documentation for CTRL-U in Insert mode

2015-05-17 Fir de Conversatie glts
Set 'backspace' to some sensible value ("indent,eol,start") and place the cursor in the middle of some line of text. Then try these: a deletes to the beginning of the line afoo deletes just "foo" afoo deletes "foo", then to the beginning of the line afoo deletes

Re: Patch 7.4.710

2015-04-21 Fir de Conversatie glts
On Tuesday, April 21, 2015 at 6:35:26 PM UTC+2, Bram Moolenaar wrote: > Patch 7.4.710 > Problem:It is not possible to make spaces visibible in list mode. > Solution: Add the "space" item to 'listchars'. (David Bürgin, issue 350) > Files: runtime/doc/options.txt, src/globals.h, src/messag

Junk added in runtime/doc/help.txt

2015-04-14 Fir de Conversatie glts
Hi, output of 'hg diff -c 6741' contains: diff -r 2ed977b23d68 -r fbc1131f0ba5 runtime/doc/help.txt --- a/runtime/doc/help.txtMon Apr 13 12:39:22 2015 +0200 +++ b/runtime/doc/help.txtMon Apr 13 12:43:06 2015 +0200 @@ -203,6 +204,16 @@ |pi_zip.txt| Zip archive explorer LOCAL ADDI

Re: Small patch for help-context

2015-04-11 Fir de Conversatie glts
On Saturday, April 11, 2015 at 12:31:05 PM UTC+2, Akshay Hegde wrote: > I found it useful to also include in, `:help help-context`, searching :help > for regular expression patterns. Here is the minor patch: ':h help-summary' would also be a good place to mention it. -- -- You received this me

Re: Unused JUMPLIST_ROTATE in mark.c

2015-04-09 Fir de Conversatie glts
On Wednesday, April 8, 2015 at 10:36:23 PM UTC+2, Bram Moolenaar wrote: > David wrote: > > > mark.c uses an "#ifdef JUMPLIST_ROTATE" directive, but JUMPLIST_ROTATE > > is never defined. Any reason for this? > > I believe this was an alternative at some point. It's possible to add > the define in

Unused JUMPLIST_ROTATE in mark.c

2015-04-08 Fir de Conversatie glts
mark.c uses an "#ifdef JUMPLIST_ROTATE" directive, but JUMPLIST_ROTATE is never defined. Any reason for this? -- David -- -- 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.o

Re: Expanding pathnames issue.

2015-01-17 Fir de Conversatie glts
On Saturday, January 17, 2015 at 3:21:07 PM UTC+1, Yuri Kanivetsky wrote: > Consider the following chain of commands: > > > $ vim -u NONE > :file test > :!echo %:80 > > > It outputs "test0". With "%:79" it outputs "test:79", "%:81" -> "test1", > "%:89" -> "test9", "%:90" -> "test:90". Somethin

Re: Turning off auto commenting

2014-12-22 Fir de Conversatie glts
On Monday, December 22, 2014 9:20:18 PM UTC+1, Don wrote: > I am trying to turn off auto-commenting, completely without success. I > am running vim 7.4.540 on an up-to-date Arch Linux system. My .vimrc: > > 1 set nocp > 2 set shiftwidth=4 > 3 set tabstop=4 > 4 set background=lig

Re: [Bug] @{register} ends in the wrong line

2014-10-30 Fir de Conversatie glts
Hi Ramel, On Thursday, October 30, 2014 4:23:32 PM UTC+1, ram...@gmail.com wrote: > Please have a look: > > vim -u NONE > -open a file with more than 1 line (or just- 2iaaagg) > :let @q = ':norm l^M' "the ^M is > @q > > -The result should be moving one character to the right, but inste

Re: Patch: support for the "space" argument for "listchars"

2014-10-10 Fir de Conversatie glts
Dear Bram and list, On Saturday, August 24, 2013 1:54:14 PM UTC+2, glts wrote: > On Mon, Aug 19, 2013 at 12:41 AM, Jesus Antonio Santos Giraldo > wrote: > > Almost a year later since last comment, Vim 7.4 is out... and again there > > is no *space* option for listchars... :( :

Re: ftplugin/python.vim & indent/sass.vim overwrites my expandtab/tabstop settings

2014-10-07 Fir de Conversatie glts
On Tuesday, October 7, 2014 3:47:04 PM UTC+2, Martin Tournoij wrote: > > If you want your own settings and never want to have filetype plugins > > enabled, do NOT set the :filetype plugin command in your .vimrc (so > > ftplugins are effectively disabled). Alternatively you can override > > those

Re: JSON is not JavaScript

2014-08-25 Fir de Conversatie glts
Hi Eli, On Monday, August 25, 2014 8:35:41 PM UTC+2, elzr wrote: > Thanks rogerz! > > Bram, I've changed the header of the indent file on my JSON plugin so it now > lists me as the current maintainer and rogerz as the original author (it had > already started diverging from Zhang's version). >

Re: [feature request] list all variables defined by `let`

2014-07-08 Fir de Conversatie glts
On Tuesday, 8 July 2014 08:43:00 UTC+2, Brook Hong wrote: > It will be useful, if there is a function to get a list of all variables with > specific type. > > For example, > > let g:foo='foo' > let g:bar='bar' > > > call listvars('g') > // return ['foo', 'bar'] You can already obtain the lis

Re: :cd & 'cdpath'

2014-05-29 Fir de Conversatie glts
On Thursday, May 29, 2014 11:52:29 AM UTC+2, Dhruva Sagar wrote: > I recently discovered 'cdpath', and noticed VIM is doing a good job at it, > except :cd doesn't autocomplete the valid paths from the 'cdpath'. I wrote > this script as a hack to work around it : > > function! s:CdComplete(ArgLea

Re: Why does Vim still have vi-compatibility mode?

2014-05-29 Fir de Conversatie glts
Hi, On Thursday, May 29, 2014 11:50:47 AM UTC+2, Dmitry Frank wrote: > Could anyone explain why does Vim still have vi-compatibility mode? Why would > one use it? > > > As a consequence, we have to keep set nocompatible in our .vimrc; there is > much noise in docs like {not in Vi}, {Vi: no ++o

Re: Patch 7.4.310

2014-05-28 Fir de Conversatie glts
On Wednesday, May 28, 2014 5:23:53 PM UTC+2, Christian Wellenbrock wrote: > On Wednesday, May 28, 2014 4:47:35 PM UTC+2, Bram Moolenaar wrote: > > I wrote: > > > > > Patch 7.4.310 > > > Problem:getpos()/setpos() don't include curswant. > > > Solution: Add a fifth number when getting/setting

Re: [PATCH] XDG Base Directory Specification support

2014-03-04 Fir de Conversatie glts
On Mon, Mar 3, 2014 at 11:20 PM, Jean-François Bignolles wrote: > the attached patch adds support for XDG Base Directory Specification. > This is a compile-time option ("--enable-xdg-basedir"), off by default. > See http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html > for detai

Suggestion: Add URL field to plugin information (vim.org)

2014-02-17 Fir de Conversatie glts
[To the maintainers of vim.org. List, I couldn't find a more appropriate email address, apologies for the noise.] Dear vim.org maintainers, I'd like to suggest adding a new, optional field 'URL' to the plugin information at vim.org. It is a common pattern for plugin authors to link to a source c

Re: search from command line

2014-02-02 Fir de Conversatie glts
On Sun, Feb 2, 2014 at 9:06 PM, Marcin Szamotulski wrote: > On 15:24 Sun 02 Feb , glts wrote: >> On Sun, Feb 2, 2014 at 2:46 PM, Marcin Szamotulski wrote: >> > Is this supposed to work (note the ":" at the beginning): >> > :/pattern >> > >&g

Re: search from command line

2014-02-02 Fir de Conversatie glts
Hi, On Sun, Feb 2, 2014 at 2:46 PM, Marcin Szamotulski wrote: > Is this supposed to work (note the ":" at the beginning): > :/pattern > > This does not land on the pattern when matching on a longer line. > For example the previous line in this email has only one place that > matches \. If I run

Re: Operator-pending mappings don't remember last count when being repeated

2014-01-29 Fir de Conversatie glts
On Wed, Jan 29, 2014 at 1:09 PM, Christian Wellenbrock wrote: > Here is a small example to illustrate the issue: > > echo 123456789 | vim - +":omap a0 :execute 'norm > 0v'.v:count1.'lh'" > > This invocation puts the string "123456789" into a new buffer and creates an > operator-pending mappin

Re: [PATCH] spec: add '%global' macros support

2014-01-26 Fir de Conversatie glts
On Sun, Jan 26, 2014 at 5:44 PM, Igor Gnatenko wrote: > # HG changeset patch > # User Igor Gnatenko > # Date 1390754183 -14400 > # Sun Jan 26 20:36:23 2014 +0400 > # Node ID 2886ccd9f4fad3109261b72107b2ca3db65814fc > # Parent c9cad40b418113f62ce3481f66351137b90910ef > spec: add '%global' ma

Re: Doc bug? (was Re: Curious remark about CTRL-V p in cmdline.txt)

2014-01-07 Fir de Conversatie glts
On Tuesday, January 7, 2014 3:29:13 PM UTC+1, glts wrote: > On Monday, January 6, 2014 11:47:09 PM UTC+1, Tim Chase wrote: > > On 2014-01-06 16:42, Tim Chase wrote: > > > > > Based on the Mercurial repo, this text has been there since roughly > > > > > the

Re: Doc bug? (was Re: Curious remark about CTRL-V p in cmdline.txt)

2014-01-07 Fir de Conversatie glts
On Monday, January 6, 2014 11:47:09 PM UTC+1, Tim Chase wrote: > On 2014-01-06 16:42, Tim Chase wrote: > > > Based on the Mercurial repo, this text has been there since roughly > > > the original load into Mercurial ("hg blame > > > vim/src/doc/cmdline.txt"), so I suspect one would have to dig i

Help tags for :function range abort dict

2014-01-04 Fir de Conversatie glts
Bram, could we add help tags for the [range] [abort] [dict] arguments of :function? Perhaps in the style of these tags? :map- :map- :map- ... :syn-keepend :syn-oneline :syn-skipwhite ... Thank you for your consideration. Best, diff -r 2f856c7c1d43 runtime/doc/eval.txt --- a/runtime/d

Re: Clojure runtime files update

2013-12-17 Fir de Conversatie glts
On Tue, Dec 17, 2013 at 2:08 PM, guns wrote: > The Clojure runtime files have been updated with the following changes: > > - A new indent option was added for compatibility with Emacs > - \. within regular expressions are no longer highlighted as > a predefined character class >

Re: [patch] Option to show indent level with 'expandtab' and 'list' option

2013-11-27 Fir de Conversatie glts
On Wed, Nov 27, 2013 at 3:59 PM, Ken Takata wrote: > 2013/11/27 Wed 23:34:12 UTC+9 ZyX wrote: >> On Nov 27, 2013 10:56 AM, "hari.g" wrote: >> > >> > Hi, >> > >> > The attached patch adds a 'listchars' option 'lsp' which marks leading >> > space at 'shiftwidth' with the defined characer so that y

Re: Patch to utilize undefined text-objects

2013-11-17 Fir de Conversatie glts
On Thu, Nov 14, 2013 at 2:14 AM, Daniel Thau wrote: > Attached is a patch to add an 'autotextobject' setting which will treat > undefined text-objects like quote text objects, using the provided > character as bounds. For example, with this setting if a user enters > "di," with the cursor between

Re: [PATCH] Asynchronous functions (settimeout, setinterval, and cancelinterval)

2013-10-13 Fir de Conversatie glts
On Sun, Oct 13, 2013 at 1:33 PM, glts <676c7...@gmail.com> wrote: > On Sun, Oct 13, 2013 at 11:15 AM, glts <676c7...@gmail.com> wrote: >> On Thu, Oct 3, 2013 at 12:40 AM, kans wrote: >>> I believe we have addressed all major concerns- the last one being the >>

Re: [PATCH] Asynchronous functions (settimeout, setinterval, and cancelinterval)

2013-10-13 Fir de Conversatie glts
On Sun, Oct 13, 2013 at 2:27 PM, Nikolay Pavlov wrote: > > On Oct 13, 2013 3:33 PM, "glts" <676c7...@gmail.com> wrote: >> >> On Sun, Oct 13, 2013 at 11:15 AM, glts <676c7...@gmail.com> wrote: >> > On Thu, Oct 3, 2013 at 12:40 AM, kans wrote: >

Re: [PATCH] Asynchronous functions (settimeout, setinterval, and cancelinterval)

2013-10-13 Fir de Conversatie glts
On Sun, Oct 13, 2013 at 11:15 AM, glts <676c7...@gmail.com> wrote: > On Thu, Oct 3, 2013 at 12:40 AM, kans wrote: >> I believe we have addressed all major concerns- the last one being the >> ex_timers command which shows all pending timers. If we have missed >> s

Re: [PATCH] Asynchronous functions (settimeout, setinterval, and cancelinterval)

2013-10-13 Fir de Conversatie glts
On Thu, Oct 3, 2013 at 12:40 AM, kans wrote: > I believe we have addressed all major concerns- the last one being the > ex_timers command which shows all pending timers. If we have missed > something, or you have other concerns, please let us know. As I wrote > before, we'd really like to see

Re: Patch: formatoptions in ftplugins

2013-10-02 Fir de Conversatie glts
Bram, On Wed, Oct 2, 2013 at 12:52 PM, Bram Moolenaar wrote: > > David Barnett wrote: > >> +Nikolai +Bram +Tim (authors of the majority of these plugins) >> >> I'm confident we can get consensus to at least remove a few of those >> formatoptions modifications. You should also add "setlocal >> for

Re: [doc] fix :dli, :dl and :dp

2013-10-01 Fir de Conversatie glts
Hi, On Tue, Oct 1, 2013 at 1:00 PM, Ken Takata wrote: > The note about ":dl" in the help of ":dli" seems wrong. > I also think the descriptions of ":dl" and ":dp" in the index.txt are > a little bit confusing. > > Please check the attached patch. This was introduced following this: https://group

Re: Patch: formatoptions in ftplugins

2013-09-30 Fir de Conversatie glts
On Mon, Sep 30, 2013 at 9:57 AM, David Barnett wrote: > I've found the built-in ftplugin files are all over the place with respect to > handling 'formatoptions'. Some ftplugins don't touch it, many clobber useful > user preferences. I put together a patch that batch-changes the ftplugin > files

Re: Promoting Newly Made Plug-ins

2013-09-27 Fir de Conversatie glts
On Thu, Sep 26, 2013 at 10:16 PM, Jacky Alciné wrote: > Hey, is it a good practice™ to promote your plug-ins in these mailing lists? I > have one I’ve been working on [1], but I don’t want to spam you guys. > > [1]: http://jalcine.me/weblog/introducing-cmake-for-vim/ vim_dev is for discussing Vim

Re: Surprised that "gi" doesn't modify the jumplist

2013-09-25 Fir de Conversatie glts
On Wed, Sep 25, 2013 at 10:04 PM, Christian Brabandt wrote: > I would even go so far and say that 'gi' is one of the more obscure > features of Vim that hardly ever someone uses. Other than that I totally > agree with Ingo, In my experience, extrapolating your own usage of Vim to that of other pe

Turn off folding in macros/less.vim

2013-09-21 Fir de Conversatie glts
Hi, the other day I piped some text into Vim's less.sh and to my surprise most of the text was folded. The text had a modeline that turned on folding. Since less does not do folding would it make sense to turn it off? diff -r 2ee5e568766c runtime/macros/less.vim --- a/runtime/macros/less.vim

Re: jump function

2013-08-29 Fir de Conversatie glts
On Friday, August 30, 2013 1:31:16 AM UTC+2, Marcin Szamotulski wrote: > That's interesting, but apparently: > > nm \ :exe "norm! \" > ends with error E471: Argument reuired, exactly the same as: > :normal! ^I > > Though as I have mentioned earlier there is no problem with ^O. I use > vim, but t

Re: jump function

2013-08-29 Fir de Conversatie glts
Hi Marcin, On Thu, Aug 29, 2013 at 8:10 PM, Marcin Szamotulski wrote: > Recently I tried to make a user function for jumping through the jump > list (by files), but it happens that there is no good interface for > that. For example CTRL-I could possibly be only with :normal! but > this does not

Re: New regexp engine problem with combining characters

2013-08-27 Fir de Conversatie glts
On Tue, Aug 27, 2013 at 11:01 PM, Dominique Pellé wrote: > glts wrote: > >> Hi, >> >> The new regexp engine seems unable to deal with combining characters. >> This is on Vim 7.4.9. Steps to reproduce: >> >> :put =\"ca\u0300t\" >&g

New regexp engine problem with combining characters

2013-08-27 Fir de Conversatie glts
Hi, The new regexp engine seems unable to deal with combining characters. This is on Vim 7.4.9. Steps to reproduce: :put =\"ca\u0300t\" :echo getline('.') =~ '\%#=0a' :echo getline('.') =~ '\%#=1a' Only the old regexp engine finds the match. Best, (Message has been boun

Different error messages for each regexp engine

2013-08-27 Fir de Conversatie glts
Hi, when searching /\? the old regexp engine says E64: \? follows nothing and the new engine says E866: (NFA regexp) Misplaced ? E64: \? follows nothing It may be me, but I'm uncomfortable with error messages being dependent on the 'regexpengine' setting. Also

Typo in comment in spell.c

2013-08-27 Fir de Conversatie glts
I believe this is a typo in spell.c: diff -r 2ee5e568766c src/spell.c --- a/src/spell.cThu Aug 22 14:14:27 2013 +0200 +++ b/src/spell.cSat Aug 24 17:08:07 2013 +0200 @@ -10135,7 +10135,7 @@ } /* - * "z?": Find badly spelled word under or after the cursor. + * "z=": Find badly spelled wo

Re: [PATCH] Fix substitution confirmation prompt in ex mode

2013-08-27 Fir de Conversatie glts
On Tue, Aug 27, 2013 at 8:28 AM, Benoit Pierre wrote: > Line number display is not taken into account so the pattern match > indicator is misaligned. > > Before: > > :%s/\cvim/VIM/gc# >1 README.txt for version 7.4 of Vim: Vi IMproved. > ^^^ > With the patch: > > :

Re: problem with spellsuggest on vim 7.4.5

2013-08-24 Fir de Conversatie glts
On Sat, Aug 24, 2013 at 9:48 PM, Cesar Romani wrote: > On 22/08/2013 07:14 a.m., Bram Moolenaar wrote: >> >> Cesar Romani wrote: >> >>> 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 lin

Re: Patch: support for the "space" argument for "listchars"

2013-08-24 Fir de Conversatie glts
On Mon, Aug 19, 2013 at 12:41 AM, Jesus Antonio Santos Giraldo wrote: > Almost a year later since last comment, Vim 7.4 is out... and again there is > no *space* option for listchars... :( :( :( > > Maybe anyone has implemented this patch in 7.4? If so, I really appreciate it. > As I said a year

Re: The numberd register 1 does not contain the text deleted by d% when the text is less than one line.

2013-08-23 Fir de Conversatie glts
On Fri, Aug 23, 2013 at 10:53 AM, Tony Mechelynck wrote: > On 23/08/13 10:36, glts wrote: >> >> On Fri, Aug 23, 2013 at 10:35 AM, glts <676c7...@gmail.com> wrote: >>> >>> On Thu, Aug 22, 2013 at 1:27 PM, Bohr Shaw wrote: >>>> >>>>

Re: The numberd register 1 does not contain the text deleted by d% when the text is less than one line.

2013-08-23 Fir de Conversatie glts
On Fri, Aug 23, 2013 at 10:35 AM, glts <676c7...@gmail.com> wrote: > On Thu, Aug 22, 2013 at 1:27 PM, Bohr Shaw wrote: >> However, the document says the register "1 always hold the text deleted by >> the delete operator with these movement commands:|%|, |(|, |)|,

Re: The numberd register 1 does not contain the text deleted by d% when the text is less than one line.

2013-08-23 Fir de Conversatie glts
On Thu, Aug 22, 2013 at 1:27 PM, Bohr Shaw wrote: > However, the document says the register "1 always hold the text deleted by > the delete operator with these movement commands:|%|, |(|, |)|, |`|, |/|, > |?|, |n|, |N|, |{| and |}|. I cannot reproduce this on Vim 7.4. Just to make sure we are

Re: Patch: support for the "space" argument for "listchars"

2013-08-19 Fir de Conversatie glts
On Mon, Aug 19, 2013 at 12:41 AM, Jesus Antonio Santos Giraldo wrote: > Almost a year later since last comment, Vim 7.4 is out... and again there is > no *space* option for listchars... :( :( :( > > Maybe anyone has implemented this patch in 7.4? If so, I really appreciate it. > As I said a year

Re: setpos() and => wrong position

2013-08-19 Fir de Conversatie glts
On Mon, Aug 19, 2013 at 10:16 AM, Dimitar DIMITROV wrote: > I will use the following text as an example: > > Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod > tempor > incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis > nostrud exercitation ullamco

GVim window width being increased when running ":vnew X | close"

2013-08-17 Fir de Conversatie glts
When I run the following two commands in my GVim 7.4 on Ubuntu 12.04 (Gnome), the net size of the GVim window doesn't change. :vnew __OpenClose__ :close But when I wrap them in a function, function! OpenClose() vnew __OpenClose__ close endfunct

Re: Vim 7.4 released!

2013-08-10 Fir de Conversatie glts
On Sat, Aug 10, 2013 at 5:50 PM, Bram Moolenaar wrote: > > glts wrote: > >> On Sat, Aug 10, 2013 at 3:44 PM, Bram Moolenaar wrote: >> > Announcing: Vim (Vi IMproved) version 7.4 >> >> Good news, thanks! >> >> By the way, vim.org still has the &quo

Re: Vim 7.4 released!

2013-08-10 Fir de Conversatie glts
On Sat, Aug 10, 2013 at 3:44 PM, Bram Moolenaar wrote: > Announcing: Vim (Vi IMproved) version 7.4 Good news, thanks! By the way, vim.org still has the "Official patches" page which links to an FTP dir, but I don't see any 7.4 patches there. Perhaps it would be good to make a note there that M

Redrawing problem when trying to scroll messages

2013-08-08 Fir de Conversatie glts
When I run an external command like :!find I can see the output in the messages area and the prompt Press ENTER or type command to continue By reflex I hit "u" to scroll up and I got Press ENTER or type command to continuePress ENTER or type command to continue Every "u" adds another enter prom

Re: Regex question (possible bug?)

2013-08-06 Fir de Conversatie glts
On Tue, Aug 6, 2013 at 10:09 PM, Hisashi T Fujinaka wrote: > I'm in nomagic and I'm trying to delete the last directory from a > directory path. So /a/b/c/d would end up being /a/b/c. > > This doesn't work, and I may be screwing it up: > :%s,/\[a-z]\*\$,, > > Or is it a bug? Not a bug, $ doesn't

Bug: Different regexp engine error messages for ":h \^x"

2013-07-28 Fir de Conversatie glts
With 'regexpengine' set to 0 or 2, ":h \^x" displays this error message: INTERNAL: Unknown character class char: 67 E149: Sorry, no help for \^x With 'regexpengine' set to 1 (also before the new regexp engine was introduced), the error message is: E63: invalid use of \_

Re: Patch: Remove invalid keywords from syntax/vim.vim

2013-07-28 Fir de Conversatie glts
On Sun, Jul 21, 2013 at 7:38 PM, Charles E Campbell wrote: > Please try syntax/vim.vim at my website: > http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM Better now, thanks. I see two remaining redundant entries, but they won't do any harm. dig dig[raph] star

Re: Update ftplugin/ocaml.vim

2013-07-24 Fir de Conversatie glts
On Wed, Jul 24, 2013 at 7:10 PM, Markus Mottl wrote: > Btw., the compiler-settings don't load unless I enter ":compiler > ocaml". This may be annoying for beginners who might expect things to > work without having to change their Vim-configuration. What would be > the best way to set this as an

Re: :25 does not save cursor position to jump list

2013-07-21 Fir de Conversatie glts
On Sun, Jul 21, 2013 at 6:48 AM, Tony Mechelynck wrote: > On 07/21/13 06:12, Dan wrote: >> >> These commands perform the same function: >> 25G >> 25gg >> :25 >> >> But the first two save the cursor position to the jump list, whereas the >> last command does not, which I feel is inconsistent and a

Re: :25 does not save cursor position to jump list

2013-07-21 Fir de Conversatie glts
On Sun, Jul 21, 2013 at 6:12 AM, Dan wrote: > These commands perform the same function: > 25G > 25gg > :25 > > But the first two save the cursor position to the jump list, whereas the last > command does not, which I feel is inconsistent and a bug. > > For example, with the following buffer: > >

Re: Patch: Very minor doc fix

2013-07-17 Fir de Conversatie glts
On Wed, Jul 17, 2013 at 4:32 PM, Jürgen Krämer wrote: > Bram Moolenaar wrote: >> >> glts wrote: >> >>> Spotted this very minor error in index.txt. Thanks. >>> >>> diff -r c015eedb9b4a runtime/doc/index.txt >>> --- a/runtime/doc/index.tx

Re: NFA-regexp problem in Vim 7.4a.24

2013-07-16 Fir de Conversatie glts
On Tue, Jul 16, 2013 at 8:41 PM, glts <676c7...@gmail.com> wrote: > On Tue, Jul 16, 2013 at 1:38 PM, Ingo Karkat wrote: >> I've found a discrepancy in pattern matching while re-running my >> plugins' test suites. With the new NFA-regexp, a (rather complex, >>

Re: NFA-regexp problem in Vim 7.4a.24

2013-07-16 Fir de Conversatie glts
On Tue, Jul 16, 2013 at 1:38 PM, Ingo Karkat wrote: > I've found a discrepancy in pattern matching while re-running my > plugins' test suites. With the new NFA-regexp, a (rather complex, > generated, used for searching insert mode completion matches) pattern > does not match any more: > > :echo '_

Re: BUG: 2dd does not delete on last line

2013-07-16 Fir de Conversatie glts
On Tue, Jul 16, 2013 at 4:17 PM, Ingo Karkat wrote: > Hello Vim developers, > > This was first reported on Stack Overflow: > > http://stackoverflow.com/questions/16710886/why-does-3dd-not-work-from-the-last-line-in-vim > > vim -N -u NONE -c "for i in range(1,3)|call setline(i,i)|endfor" > :no

Patch: Very minor doc fix

2013-07-15 Fir de Conversatie glts
Spotted this very minor error in index.txt. Thanks. diff -r c015eedb9b4a runtime/doc/index.txt --- a/runtime/doc/index.txtSun Jul 14 15:06:50 2013 +0200 +++ b/runtime/doc/index.txtMon Jul 15 20:07:27 2013 +0200 @@ -1191,7 +1191,7 @@ |:digraphs|:dig[raphs]show or enter digraphs |:

Re: Patch: Remove invalid keywords from syntax/vim.vim

2013-07-15 Fir de Conversatie glts
On Mon, Jul 15, 2013 at 6:59 PM, Charles Campbell wrote: > I've put syntax/vim.vim version 7.4a-1 up on my website: > http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM . I don't intend > to remove the documented standard-plugin commands that are in the help > (:TOhtml, etc). Thanks. It

Re: Vim development process is utterly broken (Was: Re: [patch] test98 stops when using gvim)

2013-07-15 Fir de Conversatie glts
I recently had an encounter with the dev process used for Go. They use Mercurial with the Rietveld code review extension. Every change must be submitted for public review first and needs explicit approval from the devs/community before receiving an LGTM ("looks good to me") and commit. I found it

Patch: Remove invalid keywords from syntax/vim.vim

2013-07-14 Fir de Conversatie glts
Hi list, sent this to the maintainer in May. Now resending an updated patch to the list. I removed some mistaken keywords from the vimCommand syntax group, namely: DiffOrig Man Ren TOhtml XMLent XMLns bar browseset c cmdname comment count dwim emenu* errormsg filename get index let@ locale mkdir

Re: Vim 7.4a ready for beta testing

2013-07-09 Fir de Conversatie glts
On Tue, Jul 9, 2013 at 4:22 PM, Yukihiro Nakadaira wrote: > On Tue, Jul 9, 2013 at 1:06 AM, glts <676c7...@gmail.com> wrote: >> >> On Saturday, July 6, 2013 3:59:06 PM UTC+2, Bram Moolenaar wrote: >> > Announcing: Vim (Vi IMproved) version 7.4a BETA >> > &

Re: Vim 7.4a ready for beta testing

2013-07-08 Fir de Conversatie glts
On Saturday, July 6, 2013 3:59:06 PM UTC+2, Bram Moolenaar wrote: > Announcing: Vim (Vi IMproved) version 7.4a BETA > > > This is the first BETA release of Vim 7.4. > > Please check that the distribution is OK. I haven't done one for a long > time. Report anything that isn't right. That include

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
On Sun, Jul 7, 2013 at 1:05 PM, Tony Mechelynck wrote: > On 07/07/13 13:02, Tony Mechelynck wrote: >> >> On 07/07/13 12:07, glts wrote: >>> >>> On Sun, Jul 7, 2013 at 11:44 AM, glts <676c7...@gmail.com> wrote: >>>> >>>> Trying to

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
On Sun, Jul 7, 2013 at 1:07 PM, Bram Moolenaar wrote: > > David Burgin wrote: > >> Trying to :read a remote file on VimEnter results in >> >> Error detected while processing VimEnter Auto commands for "*": >> E484: Can't open file http://www.openssh.org/txt/rfc1349.txt >> >> I used the fol

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
On Sun, Jul 7, 2013 at 11:44 AM, glts <676c7...@gmail.com> wrote: > Trying to :read a remote file on VimEnter results in > > Error detected while processing VimEnter Auto commands for "*": > E484: Can't open file http://www.openssh.org/txt/rfc1349.txt >

Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
Trying to :read a remote file on VimEnter results in Error detected while processing VimEnter Auto commands for "*": E484: Can't open file http://www.openssh.org/txt/rfc1349.txt I used the following minimal vimrc with Vim 7.4a. filetype plugin indent on autocmd VimEnter * read ht

Re: Vim 7.4a ready for beta testing

2013-07-06 Fir de Conversatie glts
On Sat, Jul 6, 2013 at 3:59 PM, Bram Moolenaar wrote: > Announcing: Vim (Vi IMproved) version 7.4a BETA > > > This is the first BETA release of Vim 7.4. > > Please check that the distribution is OK. I haven't done one for a long > time. Report anything that isn't right. That includes a crash b

Re: Vim 7.4a ready for beta testing

2013-07-06 Fir de Conversatie glts
On Sat, Jul 6, 2013 at 3:59 PM, Bram Moolenaar wrote: > Announcing: Vim (Vi IMproved) version 7.4a BETA > > > This is the first BETA release of Vim 7.4. > > Please check that the distribution is OK. I haven't done one for a long > time. Report anything that isn't right. That includes a crash b

Re: paredit.vim

2013-07-06 Fir de Conversatie glts
On Sat, Jul 6, 2013 at 1:58 PM, Zulox4 wrote: > Could you add paredit : http://www.vim.org/scripts/script.php?script_id=3998 > to the vim plugin runtime files ? It would seem arbitrary to include this, especially since there are equally viable alternatives such as vim-sexp. https://github.com/gu

Re: compatibility with Sun's original vi for command :su

2013-06-25 Fir de Conversatie glts
On Tue, Jun 25, 2013 at 1:16 PM, Tony Mechelynck wrote: > Looks like a feature, not a bug, to me. Vim does not always follow what the > POSIX pundits decreed from their high thrones that vi “must” do, especially > not in 'nocompatible' mode but not even in 'compatible' mode, unless > $VIM_POSIX is

Re: Missing commands in index.txt doc

2013-06-22 Fir de Conversatie glts
On Sat, Jun 22, 2013 at 8:12 AM, Shane Thornton wrote: > If I put my cursor on the C in that first sentence, then try to navigate to > the before "noticed" by using only the 'tn' or ';' command I am > unable to do so. The cursor will get caught at the before "new". > However, if I do the same

Re: Slow ruby syntax highlight with 7.3.1163

2013-06-11 Fir de Conversatie glts
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 I think performance of patterns like this is the reason the byte-limiting > behavior was added. On Tue, Jun 11, 2013 at 5:3

Re: Some performance figures for the new regexp engine

2013-06-09 Fir de Conversatie glts
I ran this benchmark again for Vim 7.3.1152, and I'd like to share the results with you because I think they're impressive. On Saturday, May 25, 2013 12:56:56 AM UTC+2, I wrote: > URI EmailDateSum3 URI|EmailWord > re=1 16.34 13.654.0

Re: Patch to add the :cdo and :ldo commands

2013-06-02 Fir de Conversatie glts
On Sun, Jun 2, 2013 at 8:28 PM, Yegappan Lakshmanan wrote: > 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 over all the buffers in > the loca

Re: FW: use of vim signs

2013-06-02 Fir de Conversatie glts
On Sunday, June 2, 2013 9:30:20 PM UTC+2, Bram Moolenaar wrote: > Christian Brabandt wrote: > > > Note, that latest patch I sent, does not require an extra option, is > > rather small, makes the code much more readable (imho) and we can even > > get rid of test89. > > You mean the patch you sen

Re: Some performance figures for the new regexp engine

2013-05-25 Fir de Conversatie glts
On Sat, May 25, 2013 at 1:13 PM, Bram Moolenaar wrote: > Did you also check for correctness? It's easy to make a regexp engine > that's fast but wrong. And do they possibly run out of memory and > crash? I rewrote the original Vim regexp engine to be iterative instead > of recursive to handle t

Re: Some performance figures for the new regexp engine

2013-05-25 Fir de Conversatie glts
On Sat, May 25, 2013 at 1:43 AM, glts <676c7...@gmail.com> wrote: > On Sat, May 25, 2013 at 1:17 AM, Marc Weber wrote: >> Starting vim takes less than a second, your runs are > 10 sec most of >> the time, so I guess that re=1 vs re=2 is representative for your cases.

Re: Some performance figures for the new regexp engine

2013-05-24 Fir de Conversatie glts
Thank you for your input. On Sat, May 25, 2013 at 1:17 AM, Marc Weber wrote: > I think its worth mentioning that all the timings above do include > startup times of the interpreter? I used a ~38M text file, startup time doesn't really enter here. > In your gist the only defined command is the v

Some performance figures for the new regexp engine

2013-05-24 Fir de Conversatie glts
on Linux, 64-bit i7-2700K CPU @ 3.50GHz x 8. (The Python, Perl, and egrep figures are just for comparison with the original benchmark.) I made a gist with the necessary materials here: https://gist.github.com/glts/5646749 Best, -- -- You received this message from the "vim_dev" mailli

Patch: vim.vim syntax file

2013-05-24 Fir de Conversatie glts
Hi, I sent this patch to the vim.vim maintainer, Charles Campbell, but didn't get a response. Resubmitting to vim_dev. On Fri, May 10, 2013 at 1:51 PM, I wrote: > Dear Charles Campbell, > > the regular expression for "vimNumber" in syntax/vim.vim is wrong. > > Attached patch fixes it. > > For ref

Re: Patch 7.3.970

2013-05-19 Fir de Conversatie glts
On Sun, May 19, 2013 at 8:02 PM, Tony Mechelynck wrote: > Compiling on linux_x86_64: > > gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2 > -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o > objects/regexp.o regexp.c > In file included from regexp.c:7749:0: > regex

Re: Variable for "motion type" in Operator-pending mode

2013-05-09 Fir de Conversatie glts
On Thu, Apr 18, 2013 at 4:58 PM, glts <676c7...@gmail.com> wrote: > Hi, > > I have recently learnt of a patch that was submitted to the list almost > five years ago. Please see here: > > https://groups.google.com/d/msg/vim_dev/lR5rONDwgs8/iLsVCrxo_WsJ > > The recep

  1   2   >