Re: Patch 8.2.2071

Am 30.11.2020 um 21:12 schrieb Bram Moolenaar: Problem:Vim9: list assign doesn't except empty remainder list. :s/except/accept/ -- Andy -- -- 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,

Re: Vim9: rethinking conditions and boolean expressions

Am 03.10.2020 um 17:44 schrieb Bram Moolenaar: Therefore, I'm going to make && and || have a boolean result again. I think that is the easiest to understand, and what most languages do. +100 -- Andy -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply

Re: Clearing the contents of a dictionary

Am 25.05.2020 um 22:35 schrieb Bram Moolenaar: Yegappan wrote: To clear the contents of a list named "abc", we can use "unlet abc[:]". It looks like a similar method for clearing the contents of a dictionary is not available. We can set the dictionary variable to another empty dictionary (but

Re: Patch 8.2.0762

Am 18.05.2020 um 15:18 schrieb Bram Moolenaar: Am 15.05.2020 um 22:31 schrieb Bram Moolenaar: Patch 8.2.0762 Problem:Buffer is not considered modified after setting crypt key. Solution: Set the modified flag. (Christian Brabandt, closes #6082) Files: src/optionstr.c,

Re: Patch 8.2.0762

Am 15.05.2020 um 22:31 schrieb Bram Moolenaar: Patch 8.2.0762 Problem:Buffer is not considered modified after setting crypt key. Solution: Set the modified flag. (Christian Brabandt, closes #6082) Files: src/optionstr.c, src/testdir/test_crypt.vim *** ../vim-8.2.0761/src/optionstr.c

Re: [vim/vim] In bash syntax you can't escape a backquote in a double-quoted string. (#5991)

Am 26.04.2020 um 18:03 schrieb Charles Campbell: John Little wrote: This is a regression, the syntax/sh.vim from 2019-06-16 does not show this problem. The maintainer of this syntax script has his own version numbering, and if you want to report problems he usually will first ask that you try

Re: How about highlighting captured groups in regex?

Am 09.10.2019 um 18:57 schrieb Dominique Pell??: Andy Wokula wrote > Am 07.10.2019 um 13:51 schrieb Dominique Pell??: > > Hi > > > > Vim now highlights matching text when > > typing an Ex command like :%s/foobar/ > > I like it. But I wish that it

Re: How about highlighting captured groups in regex?

Am 07.10.2019 um 13:51 schrieb Dominique Pell??: Hi Vim now highlights matching text when typing an Ex command like :%s/foobar/ I like it. But I wish that it would use a different color for the regex captured group(s). For example, if I do :%s/foo\(bar\)/ I would like "bar" (the captured

Re: [vim/vim] :! {cmd} quoting issues on windows 10 when using bash as shell (#4950)

Am 18.09.2019 um 00:09 schrieb CrispyDrone (Vim Github Repository): *Describe the bug* I've exhausted all options and followed the documentation but am unable to get |:! {cmd}| to work with the following shell configuration: |set shell=\"$PROGRAMW6432\Git\bin\bash.exe\" | I've also the tried

Re: Patch 8.1.2052

Am 18.09.2019 um 17:42 schrieb Christian Brabandt: On Mi, 18 Sep 2019, 'Andy Wokula' via vim_dev wrote: Am 17.09.2019 um 22:45 schrieb Bram Moolenaar: Patch 8.1.2052 Problem:Using "x" before a closed fold may delete that fold. Solution: Do not translate 'x' do "dl".

Re: RFC: Function to get the list of marks (getmarks)

Am 18.09.2019 um 17:18 schrieb Yegappan Lakshmanan: Hi all, Currently the following Vim built-in functions are available to get information about individual marks: getpos(), line() and col(). But we don't have a function to get the list of marks placed in a buffer or the list of global marks

Re: Patch 8.1.2052

Am 17.09.2019 um 22:45 schrieb Bram Moolenaar: Patch 8.1.2052 Problem:Using "x" before a closed fold may delete that fold. Solution: Do not translate 'x' do "dl". (Christian Brabandt, closes #4927) Files: src/normal.c, src/testdir/test_fold.vim So it's ok when `dl' deletes that

Re: Patch 8.1.2035

Am 15.09.2019 um 21:13 schrieb Bram Moolenaar: Andy Wokula wrote: Am 15.09.2019 um 14:33 schrieb Bram Moolenaar: Patch 8.1.2035 Problem:Recognizing octal numbers is confusing. Solution: Introduce scriptversion 4: do not use octal and allow for single quote inside numbers

Re: Patch 8.1.2044

Am 15.09.2019 um 23:02 schrieb Bram Moolenaar: Patch 8.1.2044 Problem:No easy way to process postponed work. (Paul Jolly) Solution: Add the SafeState autocommand event. Files: runtime/doc/autocmd.txt, src/main.c, src/proto/main.pro, src/vim.h, src/autocmd.c,

Re: Patch 8.1.2035

Am 15.09.2019 um 14:33 schrieb Bram Moolenaar: Patch 8.1.2035 Problem:Recognizing octal numbers is confusing. Solution: Introduce scriptversion 4: do not use octal and allow for single quote inside numbers. Files: runtime/doc/eval.txt, src/vim.h, src/eval.c,

Re: Patch 8.1.1952

Am 31.08.2019 um 21:07 schrieb Bram Moolenaar: Andy Wokula wrote: Am 31.08.2019 um 19:14 schrieb Bram Moolenaar: ! < *globpath()* globpath({path}, {expr} [, {nosuf} [, {list} [, {alllinks}]]]) Perform glob() on

Re: Patch 8.1.1952

Am 31.08.2019 um 19:14 schrieb Bram Moolenaar: ! < *globpath()* globpath({path}, {expr} [, {nosuf} [, {list} [, {alllinks}]]]) Perform glob() on all directories in {path} and concatenate the results.

Re: Proposal for User methods

Am 11.08.2019 um 00:11 schrieb Bram Moolenaar: So if you intentionally want to define a function to both be used without a context and as a method, but still want to specify the type, we should allow for: function Total(arg: list) function Total(arg: dict) This basically means

Re: Proposal for User methods

Am 11.08.2019 um 18:27 schrieb Bram Moolenaar: I'm not sure about methods for a specific type, e.g. only defined for a list or dict. I suppose in many cases you have very similar functionality in both, and might as well define both. It would be possible to make the type available to the

map() and lambda

:h expr-lambda I think this is a design mistake: :echo map([1, 2, 3], {idx, val -> val + 1}) It should be :echo map([1, 2, 3], {val, idx -> val + 1}) 95% of map() expressions do not need v:key (er, idx). It annoys me whenever I use it. Especially nice: dummy examples that are

Re: [vim/vim] Support for "" in mappings (Neovim patch) (#4784)

Am 07.08.2019 um 14:04 schrieb Daniel Hahler (Vim Github Repository): Neovim has a nice feature where you can use || in a mapping to stay in the current mode (a better alternative to |vnoremap x :???|, where you then have to handle re-entering visual mode etc). (in the case at hand it allows

Re: Patch 8.1.1510

Am 09.06.2019 um 17:22 schrieb Bram Moolenaar: Patch 8.1.1510 Problem:A plugin cannot easily expand a command like done internally. Solution: Add the expandcmd() function. (Yegappan Lakshmanan, closes #4514) Files: runtime/doc/eval.txt, runtime/doc/usr_41.txt, src/evalfunc.c,

Re: Patch 8.1.1083

Am 30.03.2019 um 17:28 schrieb Bram Moolenaar: Patch 8.1.1083 Problem:MS-Windows: hang when opening a file on network share. Solution: Avoid using FindFirstFile(), use GetLongPathNameW(). (Ken Takata, closes #3923) Files: src/os_win32.c Thanks for this one, very much

Re: Don't use function!

Am 08.12.2018 um 16:03 schrieb Bram Moolenaar: Yasuhiro Matsumoto wrote: On Saturday, December 8, 2018 at 10:53:07 PM UTC+9, Bram Moolenaar wrote: I have recently changed the behavior of :function to allow for redefining (overwriting) a function when that should normally be fine. Therefore,

Re: Comments halfway continuation lines

Am 19.08.2018 um 18:37 schrieb Bram Moolenaar: Currently, when making a list with continuation lines, it is not possible to add a comment somewhere: let array = [ \ item, \ item, \ item, \] Maybe you can't put a comment,

Re: [vim/vim] general check for range in command-line (#2912)

Am 14.05.2018 um 19:17 schrieb Christian Brabandt: On Mo, 14 Mai 2018, 'Andy Wokula' via vim_dev wrote: Am 14.05.2018 um 17:00 schrieb Enno (Vim Github Repository): Perhaps permitting all marks, |.|, |$| and |%| is a speedy compromise. (Maybe line numbers as well?!). I vote for undoing

Re: Patch 8.0.1837

Am 13.05.2018 um 18:36 schrieb Bram Moolenaar: Patch 8.0.1837 Problem:One character cmdline abbreviation not triggered after '<,'>. Solution: Skip over the special range. (Christian Brabandt, closes #2320) Files: src/ex_getln.c, src/testdir/test_mapping.vim Do you have a good

Re: [vim/vim] Reproducible crash with matchadd, conceal cursor and submatches (#2910)

Am 13.05.2018 um 20:53 schrieb Max Christian Pohle (Vim Github Repository): In my .vimrc I do not want to have UTF-8 chars if possible, but working with numeric representations of those isn't that comfortable either. For that reason I tried to use Vims conceal feature to replace nr2char(0xE0B4)

Re: [vim/vim] general check for range in command-line (#2912)

Am 14.05.2018 um 17:00 schrieb Enno (Vim Github Repository): Perhaps permitting all marks, |.|, |$| and |%| is a speedy compromise. (Maybe line numbers as well?!). Is it so hard to stick with abbrevs of two or more characters or to type a space? I think no. For me it's much more annoying to

Re: [vim/vim] general check for range in command-line (#2912)

Am 14.05.2018 um 17:00 schrieb Enno (Vim Github Repository): Perhaps permitting all marks, |.|, |$| and |%| is a speedy compromise. (Maybe line numbers as well?!). I vote for undoing that shitty patch. You start with one inconsistency, and then there is no end. -- Andy -- -- You received

Re: Wish:

Am 23.03.2018 um 19:16 schrieb Ingo Karkat: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 23-Mar-2018 17:28 +0100, 'Andy Wokula' via vim_dev wrote: Am 13.04.2011 um 17:07 schrieb Andy Wokula: Am 09.04.2011 20:27, schrieb Ingo Karkat: On 09-Apr-2011 14:54, Andy Wokula wrote: For example

Re: Wish:

Am 13.04.2011 um 17:07 schrieb Andy Wokula: Am 09.04.2011 20:27, schrieb Ingo Karkat: On 09-Apr-2011 14:54, Andy Wokula wrote: For example, I have a command :InFunc . It's quite a trivial command, it takes an argument Ex-command and executes it within a function. Purpose is to automatically

Re: [vim/vim] Exception in context of :silent! and try-conditional suppresses all errors in future commands (#2531)

Am 06.01.2018 um 00:00 schrieb ben-reilly (Vim Github Repository): I imagine this may be related to #538 . ... and https://groups.google.com/d/msg/vim_dev/GI0CYo-b4qg/9ABGgopVBgAJ -- Andy -- -- You received this message from the "vim_dev" maillist. Do

Re: Substitutions in closed folds

Am 13.12.2017 um 22:43 schrieb Gary Johnson: To follow up, here is what I did to fix the problematic function in my plugin. I added code above and below this line, which had been modifying every line in a closed fold instead of just l:lnum, silent exe l:lnum.'s/:.*/:\t'.strftime("%Y-%m-%d

Re: Substitutions in closed folds

Am 13.12.2017 um 18:57 schrieb Gary Johnson: I've had a bug in one of my plugins that I finally traced to what appears to be a bug in Vim (8.0.1257): a substitution on one line of a closed fold affects all lines in that fold. Here's an example. Create a file, fold_test, as shown.

Re: Patch 8.0.1281

Am 09.11.2017 um 20:46 schrieb Bram Moolenaar: Patch 8.0.1281 Problem:Loading file type detection slows down startup. Solution: Move functions to an autoload script. Files: runtime/filetype.vim, runtime/autoload/filetype.vim, runtime/scripts.vim Can we have a dedicated

Re: [vim/vim] `:unlet $FOOBAR` (#1116)

Am 26.09.2016 um 00:10 schrieb Luc Hermitte (Vim Github Repository): When an environment variable isn't set, `exists()` return false. We can assign a value to the variable with `:let`, after which point it exists. But we can't revert to an non-existent state (related to `unsetenv (3C)`)

Re: Patch 8.0.1206

Am 19.10.2017 um 18:36 schrieb Bram Moolenaar: Patch 8.0.1206 Problem:No autocmd for entering or leaving the command line. Solution: Add CmdlineEnter and CmdlineLeave. Files: runtime/doc/autocmd.txt, src/ex_getln.c, src/fileio.c, src/vim.h, src/testdir/test_autocmd.vim

Re: Patch 8.0.0794

Am 28.07.2017 um 16:47 schrieb Bram Moolenaar: Make count() accept a string. Looks like count() eventually becomes useful. -- Andy -- -- 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

Re: Regression: Patch 7.4.709

Am 20.07.2017 um 20:24 schrieb Tony Mechelynck: FWIW, I also think that :tabmove 5 should move the current tab after what is now tab 5. Andy: when you do ":1,5move 10", where would you expect the present first 5 lines to go? After the present line 10 (becoming lines 5-10 after the move) or

Re: Regression: Patch 7.4.709

Am 20.07.2017 um 15:35 schrieb 'Andy Wokula' via vim_dev: Am 19.07.2017 um 22:22 schrieb Bram Moolenaar: In my idea it's OK. It's not important actually, and if nobody else cares, I'll just throw in some Vimscript, it's an easy workaround. -- Andy -- -- You received this message from

Re: Regression: Patch 7.4.709

Am 19.07.2017 um 22:22 schrieb Bram Moolenaar: Andy Wokula wrote: Looks like Patch 7.4.709 isn't ok yet, even the test is wrong: " starting at first tab page (see link): tabmove 5 call assert_equal(5, tabpagenr()) should be call assert_equal(6, tabpagenr()) because

Regression: Patch 7.4.709

Looks like Patch 7.4.709 isn't ok yet, even the test is wrong: " starting at first tab page (see link): tabmove 5 call assert_equal(5, tabpagenr()) should be call assert_equal(6, tabpagenr()) because it's supposed to move the tab page to *after* tab page number 5; when starting at a

Re: [proposal][patch] Want to stop supporting troublesome options 'gdefault' and 'edcompatible'.

Am 08.05.2017 um 22:28 schrieb Gary Johnson: On 2017-05-08, 'Andy Wokula' via vim_dev wrote: Am 08.05.2017 um 12:53 schrieb Bram Moolenaar: For flexibility this needs to work recursively. We could do something like: let saved_options = options_save() ... do your stuff

Re: [proposal][patch] Want to stop supporting troublesome options 'gdefault' and 'edcompatible'.

Am 08.05.2017 um 12:53 schrieb Bram Moolenaar: For flexibility this needs to work recursively. We could do something like: let saved_options = options_save() ... do your stuff ... call options_restore(saved_options) The options being saved should be small to keep this

Re: [proposal][patch] Want to stop supporting troublesome options 'gdefault' and 'edcompatible'.

Am 08.05.2017 um 13:04 schrieb Christian Brabandt: On Mo, 08 Mai 2017, Bram Moolenaar wrote: Besides that, plugin writers also have a problem with very common options, such as 'wrapscan' and 'ignorecase'. We are nog going to remove these. Having an easy way to set these to their default,

Re: [proposal][patch] Want to stop supporting troublesome options 'gdefault' and 'edcompatible'.

Am 03.05.2017 um 11:11 schrieb Christian Brabandt: Hi h_east! On Mi, 03 Mai 2017, h_east wrote: 'gdefault' invertes the 'g' flag of `:substitute`. In addition to 'edcompatible', it also inverts the 'c' flag. When using `:substitute` with plugin, save and restore of the above options are

Re: Variable nested too deep for displaying

Am 13.03.2017 um 23:03 schrieb Bram Moolenaar: Andy Wokula wrote: (I'm using a pre-Vim 8.0 version). Still: can somebody confirm the following bug: " script.vim let s:f = {} func! s:f.Foo() endfunc let s:f.Bar = s:f.Foo let s:f finish Error detected while processing script.vim:

Re: Add a count to the ^ command?

Am 14.03.2017 um 09:57 schrieb Nikolay Aleksandrovich Pavlov: 2017-03-14 0:29 GMT+03:00 Bram Moolenaar <b...@moolenaar.net>: Andy Wokula wrote: Am 13.03.2017 um 21:00 schrieb Ben Fritz: On Sunday, March 12, 2017 at 10:33:06 AM UTC-5, Bram Moolenaar wrote: Someone noticed that al

Re: Add a count to the ^ command?

Am 13.03.2017 um 22:29 schrieb Bram Moolenaar: Andy Wokula wrote: Am 13.03.2017 um 21:00 schrieb Ben Fritz: On Sunday, March 12, 2017 at 10:33:06 AM UTC-5, Bram Moolenaar wrote: Someone noticed that although $ takes a count to go down (count - 1) lines, the ^ does not. Since currently

Re: Add a count to the ^ command?

Am 13.03.2017 um 21:18 schrieb Ben Fritz: On Monday, March 13, 2017 at 3:11:04 PM UTC-5, Ben Fritz wrote: On Monday, March 13, 2017 at 3:04:51 PM UTC-5, Andy Wokula wrote: I'd vote for [count]^ going to the [count]th character in the line. (We can easily go to the [count]th screen column

Variable nested too deep for displaying

(I'm using a pre-Vim 8.0 version). Still: can somebody confirm the following bug: " script.vim let s:f = {} func! s:f.Foo() endfunc let s:f.Bar = s:f.Foo let s:f finish Error detected while processing script.vim: line 15: E724: variable nested too deep for displaying s:f

Re: Add a count to the ^ command?

Am 13.03.2017 um 21:00 schrieb Ben Fritz: On Sunday, March 12, 2017 at 10:33:06 AM UTC-5, Bram Moolenaar wrote: Someone noticed that although $ takes a count to go down (count - 1) lines, the ^ does not. Since currently the count is ignored, we could make it used to go (count - 1) lines up.

Re: some improvements for feedkeys()

Am 09.09.2016 um 09:22 schrieb Christian Brabandt: Hi 'Andy! On Do, 08 Sep 2016, 'Andy Wokula' via vim_dev wrote: Am 06.09.2016 um 20:42 schrieb Christian Brabandt: Bram, if in a test we do this: call feedkeys('d1', 'x!') call feedkeys('2l', 'x') Vim will stay in the first

Re: [vim/vim] Add columnspace option (#1011)

Am 08.09.2016 um 16:41 schrieb Christian Brabandt (Vim Github Repository): what problem does this solve? Probably the same problem partly solved with 'linespace'. -- Andy -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

Re: some improvements for feedkeys()

Am 06.09.2016 um 20:42 schrieb Christian Brabandt: Bram, if in a test we do this: call feedkeys('d1', 'x!') call feedkeys('2l', 'x') Vim will stay in the first feedkeys() call and wait for input. I'd like to have feedkeys() return after CursorHold triggered, You say Vim waits for

Re: Patch 7.4.2259

Am 27.08.2016 um 13:35 schrieb Bram Moolenaar: Urtica Dioica wrote: I do like the idea for the feature. I tried it, it has some bugs, but they'll get ironed out eventually. But I've gotta ask, does no one else use search command line history? The new bindings override the old

(bug) :sil!, :try and :echoerr

gVim 7.4.2239 :sil! throw 'foo' " throws exception (ok) " :h :sil only talks about error messages, not exceptions :sil! try|echoerr 'foo'|endtry " nothing, should probably throw an exception, given " error message is turned into an exception according to :h :echoerr " worse: this command

Re: Vim 8 pre-announcement

Am 16.08.2016 um 18:43 schrieb Bram Moolenaar: Hello Vim users, Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be released in about two weeks. This is a last chance to modify new features in a way that is not backwards compatible. Once 8.0 is out we can't make changes that

Re: [patch] Add Error autocmd event

Am 09.02.2016 um 20:48 schrieb Anton Lindqvist: Can you think of a command or situation where this patch provides a nice, useful solution? Other than the examples already provided, here's a couple of ideas: - Opening a new file in a non existing directory and then write triggers a E212

Re: [Bulk] Re: List of 2-letter and 3-letter substitute commands

Am 20.12.2014 um 11:33 schrieb Bram Moolenaar: Andy Wokula wrote: What about a help section for the following special commands? 2-letter and 3-letter :substitute commands == List of :substitute commands | cegiInp

Re: [Bulk] Re: BUG: Unclosed regexp collection breaks :substitute

Am 14.03.2015 um 20:14 schrieb Ingo Karkat: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14-Mar-2015 15:34, Bram Moolenaar wrote: Ingo Karkat wrote: On 14-Mar-2015 02:11, James McCoy wrote: On Fri, Mar 13, 2015 at 09:54:18PM +0100, Ingo Karkat wrote: it's possible to avoid escaping a

Re: Proposal: range('a', 'c') should be ['a', 'b', 'c']

Am 13.01.2015 um 02:09 schrieb mattn: I know what i want can do with map(range(char2nr('a'), char2nr('z')), 'nr2char(v:val)'). But it's too long. I think. If you want everything builtin, then what's the purpose of user functions? -- Andy -- -- You received this message from the vim_dev

Re: Patch 7.4.215, split modified

Am 25.03.2014 um 13:05 schrieb Bram Moolenaar: Patch 7.4.215 Problem:Inconsistency: :sp foo does not reload foo, unless foo is the current buffer. (Liang Li) Solution: Do not reload the current buffer on a split command. Files: runtime/doc/windows.txt, src/ex_docmd.c

Re: [Bulk] Re: Implementing TabNew event

Am 23.12.2014 um 03:32 schrieb Felipe Morales: I've been working on the implementation of WinNew, and I have some doubts: 1) Should WinNew trigger when a new tab page is created? 2) Should TabNew/WinNew trigger right before/after VimEnter? After all, windows and tabs are created at that point.

Re: [Bulk] Re: [Bulk] Re: typo in tag for :help :si

Am 20.12.2014 um 11:33 schrieb Bram Moolenaar: Andy Wokula wrote: Am 19.12.2014 um 16:55 schrieb Bram Moolenaar: Yukihiro Nakadaira wrote: I think that short tag for :simalt should be :sim. diff -r ab36689121ad runtime/doc/gui_w32.txt --- a/runtime/doc/gui_w32.txtWed Dec 17 21:00:49

Re: [Bulk] Re: typo in tag for :help :si

Am 19.12.2014 um 16:55 schrieb Bram Moolenaar: Yukihiro Nakadaira wrote: I think that short tag for :simalt should be :sim. diff -r ab36689121ad runtime/doc/gui_w32.txt --- a/runtime/doc/gui_w32.txtWed Dec 17 21:00:49 2014 +0100 +++ b/runtime/doc/gui_w32.txtThu Dec 18 19:31:16 2014

Re: [Bulk] Vim 2015 calendar available

Am 19.12.2014 um 15:27 schrieb Bram Moolenaar: Hello Vim users, I have updated the handy desktop calendar for 2015. It prints on one sheet of paper and, after folding and applying a bit of glue, stands on your desk. It is available in English and Dutch. You can find the PDF files on my

List of 2-letter and 3-letter substitute commands

What about a help section for the following special commands? 2-letter and 3-letter :substitute commands == List of :substitute commands | cegiInplr | c :sc :sce :scg :sci :scI :scn :scp :scl --- | e | g

Re: [Bulk] Re: typo in tag for :help :si

Am 19.12.2014 um 16:55 schrieb Bram Moolenaar: Yukihiro Nakadaira wrote: I think that short tag for :simalt should be :sim. diff -r ab36689121ad runtime/doc/gui_w32.txt --- a/runtime/doc/gui_w32.txtWed Dec 17 21:00:49 2014 +0100 +++ b/runtime/doc/gui_w32.txtThu Dec 18 19:31:16 2014

Re: [Bulk] Re: [Bulk] Performance improvement: skip applying of modelines if nothing was done in `:doautocmd`

Am 21.10.2014 um 16:51 schrieb Christian Brabandt: On Mo, 20 Okt 2014, Daniel Hahler wrote: Am Montag, 20. Oktober 2014 19:55:53 UTC+2 schrieb Andy Wokula: I want unconditional execution of modelines. :DoModelines manually execute the modelines (no matching autocmds is a good thing here

Re: [Bulk] Performance improvement: skip applying of modelines if nothing was done in `:doautocmd`

Am 20.10.2014 um 08:23 schrieb Daniel Hahler: I have seen a noticeable performance problem when using the `vim-oblique` plugin, which was caused by calls to `doautocmd User ...` - although the user events did not exist (https://github.com/junegunn/vim-oblique/issues/30). While there is the

Re: {func} of sort()

Am 22.08.2014 um 02:05 schrieb mattn: It need to do like below with MapSort() echo MapSort([{foo:{bar: 3}}, {foo:{bar: 3 0}}], '0 + v:val[foo][bar]') If using my patch, it is possible easy to avoid this. :echo sort([3 0, 3 0 1], a:lhs a:rhs) I suppose your examples should read as follows

Re: {func} of sort()

Am 21.08.2014 um 03:50 schrieb mattn: About making list sorted by string of one of value. echo 3 3 0 This is TRUE, then: echo MapSort([{foo:{bar: 3}}, {foo:{bar: 3 0}}], 'v:val[foo][bar]') We expecet it should be kept: [{foo:{bar: 3}}, {foo:{bar: 3 0}}] But results are: [{'foo': {'bar':

Re: [Bulk] Re: [Bulk] Re: Add count to :close and :hide commands

Am 21.08.2014 um 07:49 schrieb Christian Brabandt: Am 2014-08-20 19:03, schrieb 'Andy Wokula' via vim_dev: Some people expect :1,$bd or :%bd to delete all buffers. That only works by accident, because your current buffer has more lines than you have open buffers. Or saying it differently

Re: {func} of sort()

Am 19.08.2014 um 11:17 schrieb mattn: Keys? v:key is list index, it cannot contain spaces. Spaces in values shouldn't matter. Not sure what you mean. I wonder this won't works correctly. [{a: b}, {a b: }] Guessing you want to sort by dict key: :echo MapSort([{a: b}, {a b: }],

Re: [Bulk] Re: Add count to :close and :hide commands

Am 10.08.2014 20:33, schrieb Marcin Szamotulski: On 15:51 Sun 10 Aug , Bram Moolenaar wrote: I wrote: Marcin Szamotulski wrote: I wrote a patch which adds [count] to :colse, :hide and ^Wc normal command. When given the window with window number [count] will be closed/hidden.

Re: [Bulk] Re: [patch] :undorecover command

Am 16.08.2014 21:25, schrieb Christian Brabandt: The command is named :undorecover? Some places use :undorecovery (help, EMSG). -- Andy -- -- 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

Re: [Bulk] [patch] getcmdwintype()

Am 25.07.2014 21:04, schrieb Jacob Niehus: I think this is a useful function to allow different mappings depending on the type of command window (ex, search, input, etc.). I can add documentation if people agree. -Jake You can already check expand(afile) on CmdWinEnter. Seems to be buggy for

Re: A problem(bug) of 'statusline' expression evaluation

Am 20.12.2013 04:35, schrieb Bohr Shaw: Misbehavior: set statusline=%{','.1}= 1 Normal behavior: set statusline=%{'.'.1}= .1 It's a feature: :h 'stl|/comma | When displaying a flag, Vim removes the leading comma ... -- Andy -- -- You received this message from the vim_dev

[bug] No nested autoloading within `=expr`

Bug: no nested autoloading within `=expr` :h `= ,[ autoload/air.vim ]- | func! air#Fname() | return beer#Fname() | endfunc ` ,[ autoload/beer.vim ]- | func! beer#Fname() | return $TEMP.'/air-beer.txt' | endfunc ` :sp `=air#Fname()` Error detected while processing

Regexp item \@

Pattern item `\@', :h /\@ IMHO, `\@' is almost useless. Example: try to only match an odd number of backslashes before what follows in the text. Pattern (b = backslash-pattern, w = what-follows-pattern): \%(b\%(bb\)*\)\@w This pattern does not work as intended -- it still matches within an

Re: {func} of sort()

Am 06.11.2013 02:16, schrieb mattn: When keys or values contains space letter, I wonder it works correctly. Keys? v:key is list index, it cannot contain spaces. Spaces in values shouldn't matter. Not sure what you mean. -- Andy -- -- You received this message from the vim_dev maillist. Do

Re: {func} of sort()

Am 31.05.2013 15:14, schrieb mattn: :echo sort([{foo:3},{foo:2},{foo:4}], v:lhs.foo - v:rhs.foo) What I use: (copy) sort {list} by comparing strings obtained with {selexpr} func! MapSort(list, selexpr) {list} list to sort {selexpr}(string) expression to get a string from

Re: HTML indent script sucks

Am 05.08.2013 09:01, schrieb Gary Johnson: On 2013-08-04, Andy Wokula wrote: People, you can fill this thread with your complaints about the HTML indent script. I'm the current maintainer, lately I read lots of unspecific rants here and there but direct feedback is rare for some reason

Re: HTML indent script sucks

Am 04.08.2013 22:21, schrieb Ben Fritz: 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

Re: language-mapping is not applied to macro

Am 04.08.2013 05:29, schrieb Ron Aaron: On Saturday, August 3, 2013 10:57:29 PM UTC+3, Bram Moolenaar wrote: It appears you expect lmap's to be remappable. If you look at the output of :lmap you can see they are listed with a star, which means they are not remappable. No, I expect that if I

HTML indent script sucks

People, you can fill this thread with your complaints about the HTML indent script. I'm the current maintainer, lately I read lots of unspecific rants here and there but direct feedback is rare for some reason. The current version is a descendant of

Re: [PATCH] Add 'waitforglobalmap' option

Am 22.06.2013 15:04, schrieb ZyX: This patch negates effect of patch 7.3.1179 if 'waitforglobalmap' option is set. + *'waitforglobalmap'* *'wgm'* + *'nowaitforglobalmap'* *'nowgm'* +'waitforglobalmap' 'wgm' boolean

Re: Patch 7.3.1179

Am 22.06.2013 14:37, schrieb ZyX: How to disable this behavior? I have a bunch of global mappings starting with comma and translit3 plugin which translates things like “,,” into “„” in an IMAP-like fashion (translation is done only when last character of sequence is typed; preceding characters

Re: Patch 7.3.1249

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 for this change. I don't want lines starting with or containing Vim: to define a modeline. Several of my

Re: [] inside \%[] doesn't work with new regex engine.

Am 17.06.2013 21:33, schrieb Bram Moolenaar: Yukihiro Nakadaira wrote: [] inside \%[] doesn't work with new regex engine. Steps to reproduce: $ vim -u NONE :echo match('a', '\%#=1\%[[a]]') 0 :echo match('a', '\%#=2\%[[a]]') INTERNAL: Negative state char: -165 INTERNAL:

Re: Patch for variable tabstops

Am 04.06.2013 08:06, schrieb Christian Brabandt: On Mon, June 3, 2013 22:54, Matthew Winn wrote: On Mon, 3 Jun 2013 18:34:37 +0200, Christian Brabandt wrote: Oh, well. I'll just carry it around for myself and keep working on it. I already saw one problem, that when variable tabstops are

Re: :global// bug

Am 13.03.2012 15:57, schrieb Erik Falor: On Mon, Mar 12, 2012 at 09:01:29PM +, Dimitar DIMITROV wrote: Hi, I don't have the latest version of Vim installed, so this might not be a real bug. Please check! I don't think this is a bug, per se. 1. 60obuttercrchocolateesc (120 lines) 2. qwq

Re: :global// bug

Am 14.06.2013 17:42, schrieb Andy Wokula: :g and :y should work together to report one message at the end: qwq :g/butter/y W = 120 lines yanked or rather 60 ... -- Andy -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you

Re: CursorMoved Visual Mode

Am 14.06.2013 02:15, schrieb Mike Panciera: I'm working on a project to make vim produce speech output. https://code.google.com/p/phonim/ As part of the solution, we want to use autocommands such as CursorMoved and CursorMovedI to trigger speech. Is there an equivalent event for Visual mode?

Re: Patch 7.3.1112

Am 05.06.2013 08:56, schrieb Ingo Karkat: On 05-Jun-2013 08:03 +0200, Christian Brabandt wrote: [...] the old engine has an long standing bug with \%V ;( e.g: vim -u NONE -N ifoobaresc 0veesc /\%Vfoobar\%V I should have probably provided a fix long ago. Where is the bug, that there's no

Re: Another regexp bug : \

Am 05.06.2013 07:08, schrieb Ron Aaron: On Wednesday, June 5, 2013 6:58:22 AM UTC+3, ZyX wrote: Ah, I missed these dots. But still the OP says that with those two dots `foo` is highlighted and not `fo`. No, I also missed the two dots! I compared foo\ with \(foo\)\@=. So, never mind, I

Re: Patch 7.3.1122

Am 05.06.2013 18:54, schrieb Bram Moolenaar: Patch 7.3.1122 Problem:New regexp engine: \% not supported. Solution: Implement \%. Files: src/regexp_nfa.c, src/testdir/test64.in, src/testdir/test64.ok Should be `\@'. -- Andy -- -- You received this message from the vim_dev

Re: Another regexp bug : \

Am 04.06.2013 14:36, schrieb Ron Aaron: The help says: Note that using \ works the same as using \@=: foo\.. is the same as \(foo\)\@=... But using \ is easier, you don't need the braces. However, if you look for foo\, it only matches f and not foo. Tried with both re=1 and

  1   2   3   >