[Unicode plugin] Strange behaviour of :UnicodeName on combining characters

gvim 8.0.1658 with GTK2/Gnome GUI $VIM/vimfiles/plugin/unicode.vim 0.21 according to both the script and the help. (I ran :UseVimball manually to put the script where I wanted it.) :UnicodeName on a Cyrillic letter followed by a combining character (e.g. U+0435 CYRILLIC SMALL LETTER IE followed

Patch to modify job_info() to return information about all the jobs

Hi all, Currently the job_info() function returns information about a specific job and there is no function available to return information about all the jobs. The attached patch modifies the job_info() function to return information about all the jobs in a List when an argument is not supplied.

Re: Strange ':file' command behaviour after "E23: no alternate file.

On Tue, Apr 3, 2018 at 7:14 PM, Bram Moolenaar wrote: > > Tom M wrote: > > > > On Thu, Mar 29, 2018 at 2:06 PM, Bram Moolenaar > > > wrote: > > > > > >> > > >> Tom M wrote: > > >> > > >> > First of all, thank you for VIM. Now, I'd like to share an example

Re: Strange ':file' command behaviour after "E23: no alternate file.

Tom M wrote: > > On Thu, Mar 29, 2018 at 2:06 PM, Bram Moolenaar > > wrote: > > > >> > >> Tom M wrote: > >> > >> > First of all, thank you for VIM. Now, I'd like to share an example of > >> > a rather confusing behaviour. It's the ':file' ex command when used in > >> >

Re: Strange ':file' command behaviour after "E23: no alternate file.

On Mon, Apr 2, 2018 at 1:33 AM, Tom M <7to...@gmail.com> wrote: > > > On Thu, Mar 29, 2018 at 2:06 PM, Bram Moolenaar > wrote: > >> >> Tom M wrote: >> >> > First of all, thank you for VIM. Now, I'd like to share an example of >> > a rather confusing behaviour. It's the

Re: Patch 8.0.1656

On Di, 03 Apr 2018, Bram Moolenaar wrote: > And we should have a test for xxd some day. I'll have a look. Best, Christian -- Aus Murphy's Gesetze: "Drag und drop" ist die Methode, etwas sehr langsam und mühevoll über den Bildschirm zu bewegen. Animation auch. -- -- You received this

Re: Patch 8.0.1656

Christian wrote: > On Di, 03 Apr 2018, Bram Moolenaar wrote: > > > Patch 8.0.1656 > > Problem:No option to have xxd produce upper case variable names. > > Solution: Add the -C argument. (Matt Panaro closes #2772) > > Files: src/xxd/xxd.c > > Shouldn't the mangpage also be adjusted?

Patch 8.0.1658

Patch 8.0.1658 Problem:Capitalize argument not available in long form. Solution: Recognize -capitalize. Update man page. Files: src/xxd/xxd.c, runtime/doc/xxd.1, runtime/doc/xxd.man *** ../vim-8.0.1657/src/xxd/xxd.c 2018-04-03 12:17:19.816196268 +0200 --- src/xxd/xxd.c

Re: !command error when buffer is split

Nope. Just tried running the file. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the

Re: Patch 8.0.1656

On Di, 03 Apr 2018, Bram Moolenaar wrote: > Patch 8.0.1656 > Problem:No option to have xxd produce upper case variable names. > Solution: Add the -C argument. (Matt Panaro closes #2772) > Files: src/xxd/xxd.c Shouldn't the mangpage also be adjusted? Best, Christian -- Geiz läßt

Re: !command error when buffer is split

On Di, 03 Apr 2018, Bram Moolenaar wrote: > > > On Sunday, April 1, 2018 at 6:57:13 AM UTC-4, Bram Moolenaar wrote: > > > > Sorry so you can open a file xxx.py and then :sp .then run :!python > > > > %.(with the guioption=!) > > > > > > What is in xxx.py then? > > > > xxx.py has

Patch 8.0.1657

Patch 8.0.1657 Problem:Crash when reading a channel. Solution: Clear the write flag before writing. (idea by Shinya Ohyanagi, closes #2769). Files: src/channel.c *** ../vim-8.0.1656/src/channel.c 2018-03-16 20:46:52.674189967 +0100 --- src/channel.c 2018-04-03

Re: vim prompt E484: Can't open file

On Di, 03 Apr 2018, brucekan...@gmail.com wrote: > I'm using VIM 8.0 and set the option: "set cscopequickfix=s-,c-,d-,i-,t-,e-" > vim will prompt "E484: Can't open file /tmp/vx/n" occasionally if I'm not > root user. > > when set above option, vim will generate a temp directory under /tmp,

vim prompt E484: Can't open file

I'm using VIM 8.0 and set the option: "set cscopequickfix=s-,c-,d-,i-,t-,e-" vim will prompt "E484: Can't open file /tmp/vx/n" occasionally if I'm not root user. when set above option, vim will generate a temp directory under /tmp, I found the temp direcoty was deleted every time when the

Patch 8.0.1656

Patch 8.0.1656 Problem:No option to have xxd produce upper case variable names. Solution: Add the -C argument. (Matt Panaro closes #2772) Files: src/xxd/xxd.c *** ../vim-8.0.1655/src/xxd/xxd.c 2018-02-24 18:30:51.173639406 +0100 --- src/xxd/xxd.c 2018-04-03

Re: !command error when buffer is split

> On Sunday, April 1, 2018 at 6:57:13 AM UTC-4, Bram Moolenaar wrote: > > > Sorry so you can open a file xxx.py and then :sp .then run :!python > > > %.(with the guioption=!) > > > > What is in xxx.py then? > > xxx.py has print("hello") and a blank line after. So no specific Python command.