Re: [vim/vim] PYTHON-API: `vim.eval` breaks, if the string `a:items` contains invalid `utf-8` characters (#3213)

On Tue, Jul 24, 2018 at 4:17 AM alphaCTzo7G wrote: > @lilydjwg .. actually not sure if its a > problem with Universal ctags, (compiled a few days back.) there seems to be > multiple issues here.. One was with the python-api.. > > I thought what I posted above was

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

2018-05-24 0:53 GMT+03:00 Jason Franklin : > The first instance makes sense. After all, no one would want to change the > file name in the command line window. > > The second instance means that I can't run :file in the ftplugin for the "qf" > file type. I was

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

2018-05-24 0:33 GMT+03:00 Bram Moolenaar : > > Jason Franklin wrote: > >> To replicate with the cmdline window: >> >> vim -u NONE >> q: >> :file > > Well, what do you expect to happen? I would expect it to have same output as ``, though… > >> To replicate with the

Re: Fatal Python error: Py_Initialize:

2018-05-08 16:19 GMT+03:00 srlhyo : > On Tuesday, 8 May 2018 09:43:49 UTC+1, ZyX wrote: >> 2018-05-08 2:54 GMT+03:00 srlhyo : >> > Please find attached png file. >> > >> > >> > I am unable to run the plugin "browserlink.vim" >> >

Re: Fatal Python error: Py_Initialize:

2018-05-08 11:19 GMT+03:00 Nikolay Aleksandrovich Pavlov <zyx@gmail.com>: > 2018-05-08 6:55 GMT+03:00 Vlad Vladov <zloy...@gmail.com>: >> It is unable to locate a python library called encodings which might be > > `encodings` is a part of standard Python library

Re: Fatal Python error: Py_Initialize:

2018-05-08 2:54 GMT+03:00 srlhyo : > Please find attached png file. > > > I am unable to run the plugin "browserlink.vim" > (https://github.com/jaxbot/browserlink.vim). It shows the following error: > > Fatal Python error: Py_Initialize: unable to load the file system codec >

Re: Fatal Python error: Py_Initialize:

2018-05-08 6:55 GMT+03:00 Vlad Vladov : > It is unable to locate a python library called encodings which might be `encodings` is a part of standard Python library since at least the first Python version supported by Vim now. If you are unable to locate it then you are looking

Re: [vim/vim] add environ() (#2875)

2018-05-07 23:32 GMT+03:00 Ni Va : > Le lundi 7 mai 2018 22:17:06 UTC+2, Ni Va a écrit : >> Le lundi 7 mai 2018 21:55:57 UTC+2, Bram Moolenaar a écrit : >> > Ken Takata wrote: >> > >> > >> > >> > > This might be used for a workaround for the following todo item: >> > >> > > >>

Re: Patch 8.0.1735

2018-04-19 15:45 GMT+03:00 Bram Moolenaar : > > Christ van Willegen wrote: > >> On Thu, Apr 19, 2018 at 12:12 PM, Bram Moolenaar wrote: >> > >> > Nikolay Pavlov wrote: >> > >> >> 2018-04-19 0:01 GMT+03:00 Bram Moolenaar : >> >> > >> >> >

Re: Patch 8.0.1735

2018-04-19 0:01 GMT+03:00 Bram Moolenaar : > > Patch 8.0.1735 (after 8.0.1723 and 8.0.1730) > Problem:Flexible array member feature not supported by HP-UX. (John > Marriott) > Solution: Do not use the flexible array member feature of C99. > Files:

Re: Terminal API

2018-03-25 1:04 GMT+03:00 Bram Moolenaar : > > I wrote: > >> One piece of functionality that is missing from the terminal feature is >> for the job in the terminal to communcate back to Vim. It is possible >> with the client-server feature, but that is not always available and

Re: Terminal API

2018-03-24 21:24 GMT+03:00 Bram Moolenaar : > > One piece of functionality that is missing from the terminal feature is > for the job in the terminal to communcate back to Vim. It is possible > with the client-server feature, but that is not always available and > isn't easy

Re: How about a release?

2018-03-13 10:13 GMT+03:00 Christian Brabandt <cbli...@256bit.org>: > > On Di, 13 Mär 2018, Nikolay Aleksandrovich Pavlov wrote: > >> Conveniently viewing tab-separated file is one thing, assembling is >> entirely another. Who could you share such file except person

Re: How about a release?

2018-03-13 9:09 GMT+03:00 Matthew Winn <v...@matthewwinn.me.uk>: > On 12/03/18 22:06, Nikolay Aleksandrovich Pavlov wrote: >> >> 2018-03-12 0:36 GMT+03:00 Matthew Winn <v...@matthewwinn.me.uk>: >>> >>> But editing tabular information is something t

Re: How about a release?

different from cleverly remapped ``. Doubt they really will though, plugins which make aligning with spaces easier exist for a hell lot of time, you don’t really benefit from variable tabstops unless you do have tab stops. > > On Mon, Mar 12, 2018 at 5:06 PM, Nikolay Aleksandrovich Pavlov > <

Re: How about a release?

2018-03-12 0:36 GMT+03:00 Matthew Winn : > On 11/03/18 15:04, Bram Moolenaar wrote: >> >> First of all, I'm sorry to disappoint you. This patch has been floating >> around for a long time and has never made it in. It's not urgent, and >> not a small thing to include, with

Re: Statement reparsing

2018-02-22 0:07 GMT+03:00 Jason Felice : > I've been thinking about the recent thread about vimscript and performance > (after optimizing the heck out of a plugin that does a lot of text > processing), and I'm curious about vim's reparsing of statements in > functions and

Re: [vim/vim] Have vim placed in .config directory (#2655)

2018-02-20 2:01 GMT+03:00 Ariq Haqq : > Hello, I am in the process of reorganizing all of my files and such and I > was just wondering if there was any way to the ~/.vim directory somehow > placed in .config like how much user defined configuration files are placed. > I

Re: New feature: terminal screen dumps

2018-02-19 23:06 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> Some notes which I think are not clear from my rather lengthy (and >> probably too angry) post: >> >> 1. Point 1 and 2 are just something that is worth writing VimL library >> for. Would not suggest to

Re: New feature: terminal screen dumps

2018-02-19 1:33 GMT+03:00 Nikolay Aleksandrovich Pavlov <zyx@gmail.com>: > 2018-02-19 0:30 GMT+03:00 Bram Moolenaar <b...@moolenaar.net>: >> >> As mentioned in the discussion about the popup menu fix, it's not so >> easy to write a test to check that somethi

Re: New feature: terminal screen dumps

2018-02-19 0:30 GMT+03:00 Bram Moolenaar : > > As mentioned in the discussion about the popup menu fix, it's not so > easy to write a test to check that something shows up in the right > place, with the right highlighting, etc. Basically, that Vim displayes > the right text.

Re: syntax for EOF ruby/python/other lang in vimscript

2018-02-11 2:24 GMT+03:00 Ni Va : > Le dimanche 11 février 2018 00:01:30 UTC+1, ZyX a écrit : >> 2018-02-11 1:58 GMT+03:00 Ni Va : >> > Le samedi 10 février 2018 21:17:16 UTC+1, Tony Mechelynck a écrit : >> >> On Sat, Feb 10, 2018 at 7:29 PM, 'Andy Wokula'

Re: syntax for EOF ruby/python/other lang in vimscript

2018-02-11 1:58 GMT+03:00 Ni Va : > Le samedi 10 février 2018 21:17:16 UTC+1, Tony Mechelynck a écrit : >> On Sat, Feb 10, 2018 at 7:29 PM, 'Andy Wokula' via vim_use >> wrote: >> > Am 10.02.2018 um 17:40 schrieb Ni Va: >> >> >> >> Hi, >> >> >> >>

Re: syntax for EOF ruby/python/other lang in vimscript

2018-02-11 1:58 GMT+03:00 Ni Va : > Le samedi 10 février 2018 21:17:16 UTC+1, Tony Mechelynck a écrit : >> On Sat, Feb 10, 2018 at 7:29 PM, 'Andy Wokula' via vim_use >> wrote: >> > Am 10.02.2018 um 17:40 schrieb Ni Va: >> >> >> >> Hi, >> >> >> >>

Re: Patch 8.0.1491

2018-02-10 20:28 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> > + *'pumwidth'* *'pw'* >> > + 'pumwidth' 'pw' number (default 0) >> > + global >> > + {not

Re: Patch 8.0.1491

2018-02-10 17:37 GMT+03:00 Bram Moolenaar : > > Patch 8.0.1491 > Problem:The minimum width of the popup menu is hard coded. > Solution: Add the 'pumwidth' option. (Christian Brabandt, James McCoy, > closes #2314) > Files: runtime/doc/options.txt,

Re: [vim/vim] mac build with ./config --with-features=huge but conceal feature unabled (#2621)

2018-02-07 16:03 GMT+03:00 chdiza : > Why are you passing --enable-conceal? That will come automatically with a > huge build. That still should not harm, if it does this is a bug. Except that `--with-feature` is not a valid variant AFAIK; at least my build scripts do

Re: vimball, vundle vimplug compatibility

2018-02-04 0:12 GMT+03:00 Christian Brabandt : > > On Sa, 03 Feb 2018, Marc Weber wrote: > >> http://vam.mawercer.de/ >> You can add the plugins you want to the input and get the result as .zip >> for windows or linux. > > I have never had the need for that. When I used

Re: Null value for a job type variable

2018-01-10 6:19 GMT+03:00 Yegappan Lakshmanan <yegapp...@gmail.com>: > Hi Nikolay, > > On Tue, Jan 9, 2018 at 12:58 PM, Nikolay Aleksandrovich Pavlov > <zyx@gmail.com> wrote: >> 2018-01-09 18:59 GMT+03:00 Yegappan Lakshmanan <yegapp...@gmail.com>: >>

Re: Null value for a job type variable

2018-01-09 23:58 GMT+03:00 Nikolay Aleksandrovich Pavlov <zyx@gmail.com>: > 2018-01-09 18:59 GMT+03:00 Yegappan Lakshmanan <yegapp...@gmail.com>: >> Hi Nikolay, >> >> On Mon, Jan 8, 2018 at 11:41 PM, Nikolay Aleksandrovich Pavlov >> <zyx@gmail

Re: Null value for a job type variable

2018-01-09 18:59 GMT+03:00 Yegappan Lakshmanan <yegapp...@gmail.com>: > Hi Nikolay, > > On Mon, Jan 8, 2018 at 11:41 PM, Nikolay Aleksandrovich Pavlov > <zyx@gmail.com> wrote: >> 2018-01-08 9:23 GMT+03:00 Yegappan Lakshmanan <yegapp...@gmail.com>: >

Re: Null value for a job type variable

2018-01-08 9:23 GMT+03:00 Yegappan Lakshmanan : > Hi, > > Which value you can use as the default value for a job > type variable? I see that there is a test_null_job() function > that returns a null job value (but it is supposed to be used > only for testing). But I don't see

Re: vim-debugstring: Debug printf()-style at the speed of light

2018-01-02 13:06 GMT+03:00 Nikos Koukis : > Hey vimmers, happy new year! > > This is a description to a plugin that I developed. This is my first plugin > in Vim and I wanted to ask for some feedback, mainly: > > - Do you think it's in any way useful? > - Is there any similar

Re: Saving and restoring options

2017-12-16 16:37 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> 2017-12-15 22:09 GMT+03:00 Bram Moolenaar : >> > >> > Many plugins set options to a different value. To be able to restore >> > the original value very often the old value needs to

Re: Saving and restoring options

2017-12-15 22:09 GMT+03:00 Bram Moolenaar : > > Many plugins set options to a different value. To be able to restore > the original value very often the old value needs to be saved. > > Not only is this a bit of a hassle, especially for local options, it is > also incomplete,

Re: [vim/vim] can not restore registers content properly (#2345)

2017-11-18 7:37 GMT+03:00 Tony Mechelynck : > Have you tried saving and restoring with the :let command, by means of an > auxiliary variable (possibly a script-local variable)? (see :help > script-variable, :help let-register and :help expr-register) You can’t do that:

Re: [PATCH v2] viminfo: always enforce viminfo with mode 0600

2017-11-14 1:06 GMT+03:00 Bram Moolenaar : > > Simon Ruderich wrote: > >> On Sat, Nov 11, 2017 at 04:45:37PM +0100, Bram Moolenaar wrote: >> > Simon Ruderich wrote: >> >> Making viminfo readable by other users is most likely not useful. To >> >> prevent information leakage

Re: Patch 8.0.1280

2017-11-09 21:56 GMT+03:00 Bram Moolenaar : > > Patch 8.0.1280 > Problem:Python None cannot be converted to a Vim type. > Solution: Convert it to v:none. (Ken Takata) Still why v:none and not v:null? Also most those TypeErrors below were to test error handling in the

Re: Security risk of vim swap files

2017-11-07 15:46 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> 2017-11-06 23:33 GMT+03:00 Bram Moolenaar : >> > >> > Scott Court wrote: >> > >> >> Those are very valid points, and I agree that the way Neovim handles >> >> .swp files is better.

Re: Security risk of vim swap files

ll check following that agreement automatically. > > On Mon, 6 Nov 2017 at 22.26, Nikolay Aleksandrovich Pavlov > <zyx@gmail.com> wrote: >> >> 2017-11-06 23:33 GMT+03:00 Bram Moolenaar <b...@moolenaar.net>: >> > >> > Scott Court wrote: >> >

Re: Security risk of vim swap files

2017-11-06 23:33 GMT+03:00 Bram Moolenaar : > > Scott Court wrote: > >> Those are very valid points, and I agree that the way Neovim handles >> .swp files is better. I've already explained on here and on Openwall >> numerous reasons why I believe that is the best solution and

Re: Security risk of vim swap files

2017-11-06 23:14 GMT+03:00 Gary Johnson : > On 2017-11-06, Scott Court wrote: >> Those are very valid points, and I agree that the way Neovim handles >> .swp files is better. I've already explained on here and on Openwall >> numerous reasons why I believe that is the best

Re: vim 7.3

2017-10-30 16:51 GMT+03:00 Marius Gedminas : > On Sat, Oct 28, 2017 at 02:50:48AM +0200, Tony Mechelynck wrote: >> On Thu, Oct 26, 2017 at 7:19 PM, tooth pik wrote: >> > you don't use git? >> > >> No I don't, not for Vim anyway. Somehow I understand

Re: Replace current buffer with terminal?

2017-09-30 6:34 GMT+03:00 Diego Viola : > Hi, > > I'm currently trying the :terminal command. > > Is it possible to replace the current buffer with :terminal? I've noticed > when I call :terminal it creates a new split. > > Is it possible to replace the current split with

Re: [vim/vim] Windows: vimgrep stops throwing exceptions despite no match (#2125)

2017-09-19 3:19 GMT+03:00 FocusedWolf : > I tested my .vimrc on Linux gVim and found no issue, but Windows gVim > behaves strangely :) With the nature of the issue it is highly unlikely that linux/Windows makes any difference in this regard. What are versions in both

Re: ^\^N in terminal

2017-08-06 0:17 GMT+03:00 Christian J. Robinson : > On Sat, 5 Aug 2017, Christian Brabandt wrote: > >> What I mean is when in Insert Mode and pressing CTRL-\ CTRL-N we can enter >> a normal mode command. In what mode is Vim afterwards? It is back in insert >> mode, isn't it? And

Re: Vim is...not

2017-08-01 22:17 GMT+03:00 R0b0t1 : > On Tue, Aug 1, 2017 at 12:13 PM, Bram Moolenaar wrote: >> >> Ben Fritz wrote: >> >>> :help design-not needs an update considering the recent work on running a >>> terminal in Vim (even recursive vim in vim apparently):

Re: Patch 8.0.0817

2017-07-31 2:50 GMT+03:00 James McCoy : > On Sun, Jul 30, 2017 at 06:20:03PM +0200, Bram Moolenaar wrote: >> >> Patch 8.0.0817 >> Problem:Cannot get the line of a terminal window at the cursor. >> Solution: Make the row argunt optionsl. (Yasuhiro Matsumoto, closes

Re: Patch 8.0.0818

2017-07-30 19:28 GMT+03:00 Bram Moolenaar : > > Patch 8.0.0818 > Problem:Cannot get the cursor position of a terminal. > Solution: Add term_getcursor(). > Files: runtime/doc/eval.txt, src/evalfunc.c, src/terminal.c, > src/proto/terminal.pro > > > ***

Re: terminal buffer input ctrl-c

2017-07-30 0:27 GMT+03:00 Bram Moolenaar : > > Christian wrote: > >> Hi, >> running a terminal buffer and pressing CTRL-C disturbs the statusline >> and the tabline. When running with vim-airline, I see this in the >> statusline: >> >> airline#statusline(1) which is exactly,

Re: Patch 8.0.0787

2017-07-29 0:00 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> `` used as a prefix is extremely inconvenient and `.` is >> inconsistent with all software with terminal emulator (i.e. screen and >> tmux) I know which use `{smth}` by default. This thing is >>

Re: Patch 8.0.0787

2017-07-28 14:48 GMT+03:00 Bram Moolenaar : > > Patch 8.0.0787 > Problem:Cannot send CTRL-W command to terminal job. > Solution: Make CTRL-W . a prefex for sending a key to the job. > Files: src/terminal.c, runtime/doc/terminal.txt, src/option.c `` used as a prefix

Re: [vim/vim] [terminal] cannot send ^w into terminal (#1874)

2017-07-25 18:00 GMT+03:00 mattn : > Thanks your suggestion. BTW, I don't use neovim but I heard neovim have > tmap/tnoremap? to remap terminal keys. Neovim has separate terminal mode, with separate commands for mapping (:tmap/:tnoremap). So ``, as well as everything

Re: [vim/vim] scripts.vim: Improve detection of strace output files (#1837)

2017-07-13 21:59 GMT+03:00 Christian Brabandt : > @chrisbra commented on this pull request. > > > > In runtime/scripts.vim: > >> @@ -306,7 +306,9 @@ else > set ft=virata > > " Strace > - elseif s:line1 =~# '^\(\[pid \d\+\]

Re: [vim/vim] E518: "nos" and "noswapfile" (#1826)

2017-07-08 20:40 GMT+03:00 Chinggis Tenger : > :help nos says nos[wapfile] > > but set nos issues E518: > > E518: Unknown option: nos > > rendering the option shorthandless and having to fully set as noswapfile. :nos is a *command*. Options are almost never abbreviated

Re: [vim/vim] conflicts with on Windows console version (vim.exe) (#1823)

2017-07-06 18:02 GMT+03:00 Linwei : > Controlling what terminal sends is out of Vim responsibility most of time, > not possible sometimes. > > I can control the terminal emulator to send as ^?, for the purpose of > remapping to something new in vim, and after the

Re: [vim/vim] conflicts with on Windows console version (vim.exe) (#1823)

2017-07-06 17:37 GMT+03:00 Linwei : > SecureCRT is a popular terminal software on Windows, just like iTerm on > Mac OS X. > > I don't know what emulator are you using, I have checked all the emulators > I known and came to the > conclusion that is totally ASCII 127

Re: Adding terminal emulator support in Vim

2017-07-05 12:23 GMT+03:00 Bram Moolenaar : > > R0b0t1 wrote: > >> On Mon, Jul 3, 2017 at 7:50 AM, mattn wrote: >> > On Monday, July 3, 2017 at 6:16:51 PM UTC+9, Bram Moolenaar wrote: >> >> Yasuhiro Matsumoto wrote: >> >> >> >> > I have implementation (but

Re: Adding terminal emulator support in Vim

2017-07-03 1:34 GMT+03:00 R0b0t1 : > On Sun, Jul 2, 2017 at 3:46 PM, Bram Moolenaar wrote: >> >> For a long time I have been wondering whether it would be a good idea to >> add a terminal emulator inside Vim. It's a dangerous thing, it can >> easily grow out

Re: Adding terminal emulator support in Vim

2017-07-02 23:46 GMT+03:00 Bram Moolenaar : > > For a long time I have been wondering whether it would be a good idea to > add a terminal emulator inside Vim. It's a dangerous thing, it can > easily grow out of proportions and be a maintenance nightmare. At the > same time,

Re: do not redraw screen, if tabline function calls settabvar

2017-06-28 13:12 GMT+03:00 Christian Brabandt : > Bram, > I am maintaining a eye-candy statusline plugin, that can also create a > nice tabline. I recently made a change, trying to improve the > performance of the plugin by caching certain values >

Re: Patch 8.0.0654

2017-06-23 21:52 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> 2017-06-22 20:12 GMT+03:00 Bram Moolenaar : >> > >> > Patch 8.0.0654 >> > Problem:Text found after :endfunction is silently ignored. >> > Solution: Give a warning if 'verbose'

Re: Patch 8.0.0654

2017-06-22 20:12 GMT+03:00 Bram Moolenaar : > > Patch 8.0.0654 > Problem:Text found after :endfunction is silently ignored. > Solution: Give a warning if 'verbose' is set. When | or \n are used, > execute the text as a command. > Files:

Re: code after endfunction is silently ignored (for instance in multiline --cmd)

2017-06-20 22:00 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> It appears that executing commands after :endfunction in :execute is >> not that hard. My solution is in >> https://github.com/neovim/neovim/pull/6914. > > I do not see a documentation update. What

Re: code after endfunction is silently ignored (for instance in multiline --cmd)

It appears that executing commands after :endfunction in :execute is not that hard. My solution is in https://github.com/neovim/neovim/pull/6914. -- -- 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

Re: code after endfunction is silently ignored (for instance in multiline --cmd)

2017-06-19 13:11 GMT+03:00 Nikolay Aleksandrovich Pavlov <zyx@gmail.com>: > 2017-06-19 13:08 GMT+03:00 Nikolay Aleksandrovich Pavlov <zyx@gmail.com>: >> 2017-06-19 12:41 GMT+03:00 Björn Linse <bjorn.li...@gmail.com>: >>> vim --cmd "$(printf 'func!

Re: [vim/vim] :set equalalways not respected anymore. (#1707)

2017-05-16 9:14 GMT+03:00 Christian Brabandt : > I tried Vim 7.3.0, Vim 7.4.0, Vim 8.0 and Vim 8.0.569 and all behave the > same. I have a working vim-7.0.112 at my disposal and it does behave the same as well. > > — > You are receiving this because you are subscribed

Re: code after endfunction is silently ignored (for instance in multiline --cmd)

2017-06-19 13:08 GMT+03:00 Nikolay Aleksandrovich Pavlov <zyx@gmail.com>: > 2017-06-19 12:41 GMT+03:00 Björn Linse <bjorn.li...@gmail.com>: >> vim --cmd "$(printf 'func! XX()\nechomsg "aa"\nendfunc')" >> works fine but >> vim --cmd

Re: code after endfunction is silently ignored (for instance in multiline --cmd)

2017-06-19 12:41 GMT+03:00 Björn Linse : > vim --cmd "$(printf 'func! XX()\nechomsg "aa"\nendfunc')" > works fine but > vim --cmd "$(printf 'func! XX()\nechomsg "aa"\nendfunc\ncall XX()')" > does not. One would expect at least an error about 'trailing characters' as > vim

Re: [vim/vim] Add ! for ":csope find ..." command (#1769)

2017-06-14 23:08 GMT+03:00 Bram Moolenaar : > > Anishane wrote: > >> If ':cs find' command was called with a '!', e.g. >> :cs! find .. >> and cscopequickfix option was appropriately set, vim will not jump to the >> first result in the quickfix window. >> It will only

Re: [vim/vim] Bash substring removal breaks syntax highligh if pattern contains an open curly braces (#1750)

2017-06-12 17:52 GMT+03:00 Charles E Campbell : > Henry John Kupty wrote: >> >> Hi. >> >> The following snippet breaks the syntax highlight, making it consider >> from this check onwards until the end of the file a string: >> >> if [ -n "${arg%{*}" ]; then >> echo $arg

Re: [vim/vim] Search for Russian letter range `[а-яА-Я ]` misses the letters `ё` and `Ё` (#1751)

2017-06-07 16:47 GMT+03:00 Ruslan Kabatsayev : > Not correct, not semantically. What Vim does is deliberately ignoring > LC_COLLATE while grep acts according to this category which puts “ё” > between “е” and “ж” like in the Russian alphabet. > > I'm not really sure that

Re: [vim/vim] Search for Russian letter range `[а-яА-Я ]` misses the letters `ё` and `Ё` (#1751)

2017-06-07 14:17 GMT+03:00 Christian Brabandt : > Hm, ё is 'ё' U+0451 Dec:1105 CYRILLIC SMALL LETTER IO (io) , while я > is > 'я' U+044F Dec:1103 CYRILLIC SMALL LETTER YA (ja) . > Also Ё is 'Ё' U+0401 Dec:1025 CYRILLIC CAPITAL LETTER IO (IO) , while > А is > 'А' U+0410

Re:

2017-05-15 12:58 GMT+03:00 Jefferson Carpenter : > Hello, > > One of vim's greatest strengths is how it keeps key presses to a minimum. > Switching between modes, however, necessitates unnecessarily long > combinations of key presses. In short, at the second space

Re: Define behavior for over/underflow in vim script arithmetic

2017-05-05 23:23 GMT+03:00 Bram Moolenaar : > > James McCoy wrote: > >> Recently, there was some work done on defining how to handle converting >> numeric literals in vim script to C integers -- basically, clamp to the >> extremes of the datatype. If it would exceed the

Re: Patch 8.0.0571

2017-04-20 22:12 GMT+03:00 Bram Moolenaar : > > Patch 8.0.0571 > Problem:The cursor line number becomes negative when using :z^ in an empty > buffer. (neovim #6557) Github uses `user/repo#NR` (`neovim/neovim#6557`) to reference foreign issues. This would

Re: [vim/vim] job_stop(some_job, "int") closes the channel even if process does not quit (#1632)

2017-04-11 23:43 GMT+03:00 Bram Moolenaar : > > Martin Gammelsæter wrote: > >> I'm not sure whether this is intended or not, but it seems like there >> currently is no way of sending SIGINT to a job through the jobs api >> without also closing the channel. >> >> To

Re: [vim/vim] why the return type of `py3 vim.current.buffer.options["filetype"]` is bytes but not string? (#1625)

2017-04-10 5:54 GMT+03:00 Yggdroot : > For example, py3 print( repr(vim.current.buffer.options["filetype"]) ) will > print b'cpp' but not 'cpp', > while neovim will return a string. > I think it's not reasonable to return a bytes. Most Vim strings are not guaranteed to

Re: [vim/vim] Make menus available to scripts (#1563)

2017-03-31 17:58 GMT+03:00 Matthieu Coudron : > I can see it's useful. Currently the values could be obtained with a :menu > command, but parsing the output is quite complicated. > > correct. Just dumping the menus is enough for the scenariis I have in mind > so I've

Re: [vim/vim] Speed up parsing vim script (#1589)

2017-03-24 19:02 GMT+03:00 Pavol Juhas : > What for? Initialization of table is very fast anyway. And Vim has to parse > commands > almost immediately, when source .vimrc for example. > > To avoid hashing every possible abbreviation of builtin commands and to > handle

Re: [vim/vim] Speed up parsing vim script (#1589)

2017-03-23 11:34 GMT+03:00 Dominique Pellé : > @jamessan wrote: > > You could use something like gperf or triehash to generate the hash table at > build time. > gperf is widely available, but triehash is a simple Perl script with a > permissive license, > so it could

Re: curly-braces variables do not work as index for dictionaries

2017-03-20 16:29 GMT+03:00 Christian Brabandt : > Hi, > is this supposed to work or not? > > let a='foobar' > let c={} > let c.{a} = 10 > > Currently this gives E713: Cannot use empty key for Dictionary > > However reading :h curly-braces-names makes it sound like it should >

Re: python can not access predefined variable

2017-03-17 12:58 GMT+03:00 Yggdroot Chen : > One local buffer variable is predefined: > *b:changedtick* *changetick* > > But I can't access it through this: > > :py print vim.current.buffer.vars["changedtick"] > > I think this is a

Re: Variable nested too deep for displaying

2017-03-15 18:54 GMT+03:00 'Andy Wokula' via vim_dev : > 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 = {} >>> >>>

Re: Add a count to the ^ command?

2017-03-14 0:29 GMT+03:00 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)

Re: [vim/vim] Not all regexp classes [:...:] were not tested. (#1560)

2017-03-14 11:09 GMT+03:00 Kazunobu Kuriyama : > But it seems strange that we need to restrict [:cntrl:] and [:graph:] to > ASCII only. > > Quite understandable. But otherwise, we will have to either rely entirely on > the is*() functions provided by the OS in use or

Re: [vim/vim] Proper authorship of commits (#1554)

2017-03-13 2:09 GMT+03:00 chdiza : > Now contrast that with Vim. Even though we know @dpelle has authored at > least 1 > commit, this will show none: > > That's not the way that one should go about looking for authorship for Vim > patches, and it never has been. Grep the

Re: [patch] neovim patches

2017-03-08 1:14 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> 2017-03-05 16:56 GMT+03:00 Bram Moolenaar : >> > >> > Justin M. Keyes wrote: >> > >> >> On Sat, Mar 4, 2017 at 10:10 PM, Christian Brabandt >> >> wrote: >> >> >

Re: [patch] neovim patches

2017-03-05 16:56 GMT+03:00 Bram Moolenaar : > > Justin M. Keyes wrote: > >> On Sat, Mar 4, 2017 at 10:10 PM, Christian Brabandt >> wrote: >> > On Sa, 04 Mär 2017, Bram Moolenaar wrote: >> > >> >> >> >> Christian Brabandt wrote: >> >> >> >> > On Di, 28 Feb

Re: suspicious integer overflow in src/spellfile.c:1607

2017-02-28 23:30 GMT+03:00 Vekktone Official : > On Tuesday, February 7, 2017 at 9:36:20 PM UTC-6, shqking wrote: >> Hi all. >> >> Suspicious integer overflow is found in >> src/spellfile.c:1607.(https://github.com/vim/vim/blob/master/src/spellfile.c#L1607) >> >>

Re: [vim/vim] islocked('b:.changedtick') fails (#1495)

2017-02-23 16:25 GMT+03:00 Bram Moolenaar : > >> > Nikolai Pavlov wrote: >> > >> >> @brammool This is not fine. First, this shows yet another >> >> inconsistency between different notations. Second, dictionary with >> >> variables in not guaranteed to be `b:` and `let d =

Re: [vim/vim] islocked('b:.changedtick') fails (#1495)

2017-02-21 22:47 GMT+03:00 Bram Moolenaar : > > Nikolai Pavlov wrote: > >> @brammool This is not fine. First, this shows yet another >> inconsistency between different notations. Second, dictionary with >> variables in not guaranteed to be `b:` and `let d = b:|call >>

Re: [vim/vim] Is 'backup' supposed to be off by default? (#1468)

2017-02-12 7:17 GMT+03:00 thecliguy : > I am running the following version of Vim on Windows 10: > > VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Nov 6 2016 17:05:36) > MS-Windows 32-bit console version > Included patches: 1-69 > > I have observed that upon editing a

Re: [vim/vim] printf("%p") is useless (#1466)

2017-02-11 21:31 GMT+03:00 h_east : > Hi Nikolai, > > Excuse, This has nothing to do with the subject, will not you stop using > `VimL`? > GitHub ceased using VimL. > See the attached image. I have no reasons to, and me starting to use this term has nothing to do with GH:

Re: [vim/vim] Feature Request: Make :g/pattern/"ay work (#1416)

2017-01-28 17:26 GMT+03:00 glacambre : > While doing :g/pattern/y works (for each line matching pattern, the default > register is replaced with the matched line), :g/pattern/"ay (copying the > last line matching the pattern in the register "a") and :g/pattern/"Ay >

Re: job_info returns invalid JSON

2017-01-28 6:23 GMT+03:00 David Fishburn <dfishburn@gmail.com>: > On Fri, Jan 27, 2017 at 8:42 PM, Nikolay Aleksandrovich Pavlov > <zyx@gmail.com> wrote: >> >> 2017-01-28 4:33 GMT+03:00 David Fishburn <dfishburn@gmail.com>: >> > Running o

Re: job_info returns invalid JSON

2017-01-28 4:33 GMT+03:00 David Fishburn : > Running on Windows using: > > :ver > VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 24 2017 13:37:57) > MS-Windows 32-bit GUI version with OLE support > Included patches: 1-233 > > job_info(...) returned the following: > > { >

Re: YML formatting inconsistent bug

I do not see any problems with that file, it indents to ```YAML sudo: required language: generic services: - docker before_install: - sudo apt-get update - sudo apt-get install -o Dpkg::Options::="--force-confold" --force-yes -y docker-engine - docker build -t $REPO --build-arg

Re: Vim vulnerability

2017-01-19 22:12 GMT+03:00 Christian J. Robinson : > On Thu, 19 Jan 2017, Michal Grochmal wrote: > >> I went through the list of emails about this topic and am a little >> confused why it is being such a fuss. Apologies in advance if i'm talking >> out of my ass but, at least

Re: Vim vulnerability

2017-01-19 21:57 GMT+03:00 Michal Grochmal : > Hi guys, > > I went through the list of emails about this topic and am a little > confused why it is being such a fuss. Apologies in advance if i'm > talking out of my ass but, at least according to my understanding, there >

  1   2   3   >