Re: Terminal is very slow in the gui

On Wednesday, October 11, 2017 at 1:04:50 AM UTC+3, Ken Takata wrote: > Hi Ramel, > > 2017/10/11 Wed 6:08:33 UTC+9 Ramel Eshed wrote: > > On Saturday, September 30, 2017 at 5:00:38 PM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > >

Scrolling with the mouse-wheel when scrollbind is set

I found this in the help for scroll-binding: "When using the scrollbars, the binding only happens when scrolling the window with focus (where the cursor is). You can use this to avoid scroll-binding for a moment without resetting options." Actually, this is also the case for scrolling with the

Terminal is very slow in the gui

Hi, Running the following script in the gui (:terminal job.sh) takes more than 10 seconds. During that time the screen in not updated and vim is not responsive. Doing the same in terminal-vim is much faster, but the screen is updated only when the job is finished. running this script using

Problem to restore registers

Hi, Sometimes, there is a need for a mapping to yank something without a trace so it has to save and restore the relevant registers. The problem is that there is no way to set register " without modifying register 0. So if, for example, I yanked something and then deleted something else and

Another issue when searching with ? and CTRL-G

vim -u NONE -N :set incsearch iaaa (insert 3 lines of 'a') ?a (now line 2 is highlighted) ^G (now line 3 is highlighted) (cursor ends at line 1!) Thanks, Ramel -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying

'~' should be escaped when using search and CTRL-L

Hi, Please have a look: vim -u NONE -N :set incsearch ia~b (insert the text "a~b") ?a^L (search for 'a' and hit CTRL-L and ENTER) I'm getting E33 because '~' is not escaped. Thanks, Ramel -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the

Re: wrong command-line redraw when using 'out_io': 'buffer' with job_start()

On Friday, May 5, 2017 at 11:23:57 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > > > On Sunday, April 30, 2017 at 9:24:13 PM UTC+3, Bram Moolenaar wrote: > > > > > Ramel Eshed wrote: > > > > > > > > > > > O

Re: [vim/vim] Regularly exiting vim sets xterm in bracketed paste mode (#1671)

On Tuesday, June 6, 2017 at 11:58:50 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > Any updates about this issue? > > I'm using gnome terminal 2.31.3 (which comes with RHEL6) and must set t_BE= > > to avoid the corrupted pate issue in the terminal after exiti

Re: Patch 8.0.0626

On Tuesday, June 6, 2017 at 11:25:30 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Monday, June 5, 2017 at 8:32:57 PM UTC+3, Bram Moolenaar wrote: > > > Patch 8.0.0626 > > > Problem:In the GUI the cursor may flicker. > > > Solution: Ch

Re: [vim/vim] Regularly exiting vim sets xterm in bracketed paste mode (#1671)

Hi All, Any updates about this issue? I'm using gnome terminal 2.31.3 (which comes with RHEL6) and must set t_BE= to avoid the corrupted pate issue in the terminal after exiting Vim. I think that there is no reason to break old behavior, even if there is a workaround for that. Thanks, Ramel

Re: Patch 8.0.0626

On Monday, June 5, 2017 at 8:32:57 PM UTC+3, Bram Moolenaar wrote: > Patch 8.0.0626 > Problem:In the GUI the cursor may flicker. > Solution: Check the cmd_silent flag before updating the cursor shape. > (Hirohito Higashi, closes #1637) > Files: src/getchar.c > > > ***

Re: wrong command-line redraw when using 'out_io': 'buffer' with job_start()

On Monday, May 1, 2017 at 3:32:04 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Sunday, April 30, 2017 at 9:24:13 PM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > On Sunday, April 30, 2017 at 5:25:08 PM UTC+3, B

Re: wrong command-line redraw when using 'out_io': 'buffer' with job_start()

On Sunday, April 30, 2017 at 9:24:13 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Sunday, April 30, 2017 at 5:25:08 PM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > This is not the case with every job, but redir

Re: wrong command-line redraw when using 'out_io': 'buffer' with job_start()

On Sunday, April 30, 2017 at 5:25:08 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > This is not the case with every job, but redirecting the following > > script output to a buffer causes messages to disappear from command > > line: > > > > --

wrong command-line redraw when using 'out_io': 'buffer' with job_start()

Hi, This is not the case with every job, but redirecting the following script output to a buffer causes messages to disappear from command line: -- loop.sh -- #!/bin/bash for i in `seq 1 1000`; do echo $i sleep 0.008s done vim -u NONE -N :call job_start('loop.sh', {'out_io':

Re: Inconsistency between the different insert mode * commands

On Wednesday, April 5, 2017 at 9:47:21 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > > > vim -u NONE > > > > > > > > ia="b\n" > > > > > > > > results: > > > > ab > > > >

Re: Inconsistency between the different insert mode * commands

On Monday, April 3, 2017 at 10:36:06 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > vim -u NONE > > > > ia="b\n" > > > > results: > > ab > > > > > > This should be the expected behavior as I understand. But if

Inconsistency between the different insert mode * commands

Hi, vim -u NONE ia="b\n" results: ab This should be the expected behavior as I understand. But if I use instead: ia="b\n" I get: b a Also: ia="b\n" I get: ab^@ -the ^@ is displayed instead of an empty new line. I'm using vim 8.0.540 on RHEL6. Please look into it. Thanks, Ramel -- --

Re: system() delay

On Monday, August 29, 2016 at 8:35:33 AM UTC+3, Dominique Pelle wrote: > Ramel wrote: > > > Nice catch! > > My 'shell' was tcsh and after changing it to /bin/sh (=bash) System() works > > much better (only ~x2 slower than Job()). I probably wouldn't get into this > > if I got

Re: system() delay

On Sunday, August 28, 2016 at 11:36:33 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > Of course, I've measured the time from job_start to close_cb. You can see > > this comparison in the example I've attached earlier in this thread. > > Hmm, it's

Re: system() delay

On Sunday, August 28, 2016 at 5:53:33 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Friday, August 26, 2016 at 7:29:58 PM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > On Friday, August 26, 2016 at 12:02:38 AM UT

Re: system() delay

On Friday, August 26, 2016 at 7:29:58 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Friday, August 26, 2016 at 12:02:38 AM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > On Thursday, August 11, 2

Re: system() delay

On Friday, August 26, 2016 at 12:02:38 AM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Thursday, August 11, 2016 at 3:08:01 AM UTC+3, Ramel Eshed wrote: > > > On Thursday, August 11, 2016 at 2:19:38 AM UTC+3, Tony Mechelynck wrote: > > > > There

autocommands not triggered for quickfix

Hi Bram, In the autocommand help it is mentioned that only few commands are triggered with the quickfix buffer. Is there a reason not to trigger other events? I'd expect that BufWinLeave, at least, would be triggered, like BufWinEnter does. Thanks, Ramel -- -- You received this message from

Re: gui cursor blinking issues (again)

On Friday, August 12, 2016 at 3:08:46 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Thursday, August 11, 2016 at 11:11:08 PM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > I guess that it depends on the job output ch

Re: gui cursor blinking issues (again)

On Thursday, August 11, 2016 at 11:11:08 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > I guess that it depends on the job output characteristics, but I can > > still see cursor blinking issues while using 'out_io': buffer in the > > gui. I don't see it alw

gui cursor blinking issues (again)

Hi Bram, I guess that it depends on the job output characteristics, but I can still see cursor blinking issues while using 'out_io': buffer in the gui. I don't see it always, but there are cases in which it becomes really disturbing. It was so bad that I've tried to disable cursor blinking

Re: system() delay

On Thursday, August 11, 2016 at 2:19:38 AM UTC+3, Tony Mechelynck wrote: > There are other factors which are right there in the help: > - job_start() returns a Job object and doesn't wait for the job to finish > - system() waits for the external command to finish and returns its > full stdout

Re: system() delay

On Thursday, August 11, 2016 at 12:57:27 AM UTC+3, Dominique Pelle wrote: > Ramel Eshed ]wrote: > > > Hi Bram, > > > > I noticed that using system() function has an overhead of 0.2 seconds > > (checked on RHEL 5.5) while using job_start() is 10 times faster (f

system() delay

Hi Bram, I noticed that using system() function has an overhead of 0.2 seconds (checked on RHEL 5.5) while using job_start() is 10 times faster (from job_start to close_cb). Is this because of system() is using temp files instead of pipes? This is a noticeable delay. Thanks, Ramel -- --

Re: request: word motions enhancement

On Thursday, July 21, 2016 at 6:59:14 PM UTC+3, Ramel Eshed wrote: > Hi, > > I always felt that Vim's (actually Vi) word motions design is a bit awkward. > Let's say that the cursor is on the word 'self' in the following line: > > if self.words.list[i/(j+1)] == '' >

Re: Using file name with quickfix commands

On Thursday, July 14, 2016 at 11:34:36 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > > Strange. Oh, perhaps it's because this "mybuf" is near the start of the > > > buffer list? I reversed the search order, thinking that there is a > >

request: word motions enhancement

Hi, I always felt that Vim's (actually Vi) word motions design is a bit awkward. Let's say that the cursor is on the word 'self' in the following line: if self.words.list[i/(j+1)] == '' If I want to take the naive way (without counting words or think of other commands combinations) and move

Re: Using file name with quickfix commands

On Monday, July 11, 2016 at 12:33:28 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Sunday, July 10, 2016 at 8:23:15 PM UTC+3, Bram Moolenaar wrote: > > > Lcd wrote: > > > > > > > [...] > > > > &

Re: Patch 7.4.1890

On Monday, July 11, 2016 at 12:13:40 AM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > I'm not sure if this patch was supposed to fix the issue completely, but > > there are still issues with the gui cursor. > > > > 1) When job output is redirected to a b

skipped echo after setbufvar()

Hi Bram, Please check this: vim -u NONE -N :new mybuf :let b:myvar = 1 :set hidden :q :call setbufvar('mybuf', 'myvar', 2) | echo 'done' I don't see the 'done' message. I can see it only when mybuf is displayed in a window. Thanks, Ramel -- -- You received this message from the "vim_dev"

Re: Using file name with quickfix commands

On Sunday, July 10, 2016 at 8:23:15 PM UTC+3, Bram Moolenaar wrote: > Lcd wrote: > > > [...] > > > > Currently an error item from loclist looks like this: > > > > > > > > { > > > > 'lnum': 148, > > > > 'bufnr': 1, > > > > 'col': 7, > > > >

Re: Using file name with quickfix commands

Hi Bram, On Thursday, July 7, 2016 at 10:24:49 PM UTC+3, Bram Moolenaar wrote: > There has been a request that when adding items to the quickfix list, no > buffer is created to hold the file name. > > The reason is that when there are many different file names this causes > the buffer list to

runtime/ftplugin/perl.vim is not up to date

Hi, There were few updates to this file in https://github.com/vim-perl/vim-perl/blob/master/ftplugin/perl.vim since Jul 2013. The version distributed with Vim sets the global value of iskeyword. It already fixed in Oct 2013. Thanks, Ramel -- -- You received this message from the "vim_dev"

Re: Patch 7.4.1890

On Saturday, June 4, 2016 at 5:24:42 PM UTC+3, Bram Moolenaar wrote: > Patch 7.4.1890 > Problem:GUI: When channel data is received the cursor blinking is > interrupted. (Ramel Eshed) > Solution: Don't update the cursor when it is blinking. > Files: sr

Re: Asynchronous grep plugin - thoughts and issues

On Thursday, June 9, 2016 at 6:53:06 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > > > 1) Actually, there is a bug here which is not exactly what I've > > > > described earlier. The issue is that :call setqflist([]), instead of > > > >

Re: Asynchronous grep plugin - thoughts and issues

On Thursday, June 9, 2016 at 11:52:41 AM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > 1) Actually, there is a bug here which is not exactly what I've > > described earlier. The issue is that :call setqflist([]), instead of > > adding one more list after t

Re: Asynchronous grep plugin - thoughts and issues

On Friday, June 3, 2016 at 7:54:12 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Friday, June 3, 2016 at 12:17:15 PM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > Hi Bram and Yegappan, > > > > > >

Re: Patch 7.4.1891

On Tuesday, June 7, 2016 at 12:14:25 AM UTC+3, Bram Moolenaar wrote: > Xavier de Gaye wrote: > > > On 06/05/2016 04:11 PM, Bram Moolenaar wrote: > > >> Xavier de Gaye wrote: > > >> > > >>> Two pyclewn tests fail after patch 7.4.1891. It seems that not all > > 'insert' > > >>> function

Re: Conceal highlight is not fully concealed

On Friday, June 3, 2016 at 6:53:52 PM UTC+3, Christian Brabandt wrote: > Hi Ramel! > > On Fr, 03 Jun 2016, Ramel Eshed wrote: > > > When there are concealed syntax elements in a line and 'wrap' is on the > > line will be wrapped in the wrong place. > > &g

Conceal highlight is not fully concealed

When there are concealed syntax elements in a line and 'wrap' is on the line will be wrapped in the wrong place. For example, look at line 12 in help.txt (:h). It actually has 75 virtual columns if we don't count the two concealed bars. But if you set vim window width to 75 columns (:set

Re: Asynchronous grep plugin - thoughts and issues

On Friday, June 3, 2016 at 12:17:15 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > Hi Bram and Yegappan, > > > > Yegappan, You were right -saving the qf_last makes a big difference. I > > probably checked your patch after using many quickfix operations

Re: Asynchronous grep plugin - thoughts and issues

On Thursday, June 2, 2016 at 7:53:25 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > Hi All, > > > > Thanks to Bram and his recent work on channels, I have a preliminary > > version of an asynchronous grep plugin which lets you work with the > > a

Re: Asynchronous grep plugin - thoughts and issues

Hi Bram and Yegappan, Yegappan, You were right -saving the qf_last makes a big difference. I probably checked your patch after using many quickfix operations (see below). Let me summarize the problems found so far using the agrep plugin: 1. SEGV crashes - fixed 2. Vim hangs while quickfix

Re: Use 'out_io': 'buffer' with nomodifiable

On Sunday, May 29, 2016 at 4:44:12 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > In every Vim plugin that I've used (which are not too many though) > > there was a protection on the general-purpose buffers (done by setting > > and resetting 'modifiable').

Re: Asynchronous grep plugin - thoughts and issues

On Monday, May 30, 2016 at 5:11:57 AM UTC+3, yega...@gmail.com wrote: > Hi, > > On Sat, May 7, 2016 at 2:42 PM, Ramel Eshed <rame...@gmail.com> wrote: > > Hi All, > > > > Thanks to Bram and his recent work on channels, I have a preliminary > > version of an

Re: Asynchronous grep plugin - thoughts and issues

On Sunday, May 29, 2016 at 4:44:12 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > I tried the patch from shougo's thread and it solved my problem. thanks! > > So the current Vim works for you? Yes. > > > There is another (minor) issue I noti

Re: Use 'out_io': 'buffer' with nomodifiable

On Friday, May 27, 2016 at 10:38:00 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Wednesday, May 25, 2016 at 11:49:48 PM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > Is there any way to use a nomodifiable bu

Re: Asynchronous grep plugin - thoughts and issues

On Friday, May 27, 2016 at 9:00:03 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > > > I'm not sure what exactly you've done in the last few patches, but it > > > > seems like the SEGV issue is solved now, Thanks. > > > > > > Glad to

Re: Navigate in Vim messages bug

On Thursday, May 26, 2016 at 6:03:25 PM UTC+3, h_east wrote: > Hi Bram, Ramel and developers, > > 2016-5-25(Wed) 23:16:51 UTC+9 h_east: > > Hi Ramel, > > > > 2016-5-25(Wed) 22:02:46 UTC+9 Ramel Eshed: > > > Hi All, > > > > > > Please check t

Re: Asynchronous grep plugin - thoughts and issues

On Wednesday, May 25, 2016 at 10:48:32 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > I'm not sure what exactly you've done in the last few patches, but it > > seems like the SEGV issue is solved now, Thanks. > > Glad to hear that. > > > Unfortunat

Re: Use 'out_io': 'buffer' with nomodifiable

On Wednesday, May 25, 2016 at 11:49:48 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > Is there any way to use a nomodifiable buffer as an output buffer for > > a job? If not, I think that it could be very useful. > > The idea of making a buffer nomodifiabl

Navigate in Vim messages bug

Hi All, Please check this: vim -u NONE -N :for i in range(1, 200) | echoerr 'mes ' . i | endfor G " - go to the bottom of the list Now, type k several times; instead of moving one line back each time, I get extra 'Press ENTER or type command to continue' messages. Thanks, Ramel -- -- You

Use 'out_io': 'buffer' with nomodifiable

Hi, Is there any way to use a nomodifiable buffer as an output buffer for a job? If not, I think that it could be very useful. Thanks, Ramel -- -- 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: Asynchronous grep plugin - thoughts and issues

On Sunday, May 8, 2016 at 8:50:30 PM UTC+3, Ramel Eshed wrote: > On Sunday, May 8, 2016 at 2:26:05 PM UTC+3, Bram Moolenaar wrote: > > Ramel Eshed wrote: > > > > > On Sunday, May 8, 2016 at 8:59:24 AM UTC+3, Bram Moolenaar wrote: > > > > Ramel Eshed wrot

Re: Asynchronous grep plugin - thoughts and issues

On Sunday, May 8, 2016 at 2:26:05 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Sunday, May 8, 2016 at 8:59:24 AM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > Thanks to Bram and his recent work on chan

Re: Asynchronous grep plugin - thoughts and issues

On Sunday, May 8, 2016 at 8:59:24 AM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > Thanks to Bram and his recent work on channels, I have a preliminary > > version of an asynchronous grep plugin which lets you work with the > > available results while grep is sti

Asynchronous grep plugin - thoughts and issues

Hi All, Thanks to Bram and his recent work on channels, I have a preliminary version of an asynchronous grep plugin which lets you work with the available results while grep is still running. I would like to take advantage of this relatively short script to raise some issues and thoughts I

Re: Adding to quickfix list issue

On Monday, April 18, 2016 at 9:39:15 AM UTC+3, Bram Moolenaar wrote: > Yegappan Lakshmanan wrote: > > > On Sun, Apr 17, 2016 at 11:38 AM, Yegappan Lakshmanan > > <yegapp...@gmail.com> wrote: > > > Hi, > > > > > > On Sun, Apr 17, 201

Re: Asynchronous screen update

On Monday, April 18, 2016 at 8:35:18 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Sunday, April 17, 2016 at 11:33:50 AM UTC+3, Bram Moolenaar wrote: > > > Ramel Eshed wrote: > > > > > > > When using “out_io”: “buffer

Re: Adding to quickfix list issue

On Monday, April 18, 2016 at 1:43:19 AM UTC+3, yega...@gmail.com wrote: > Hi, > > On Sun, Apr 17, 2016 at 11:38 AM, Yegappan Lakshmanan > <yegapp...@gmail.com> wrote: > > Hi, > > > > On Sun, Apr 17, 2016 at 3:35 AM, Ramel Eshed <rame...@gmail.com> wrote:

Re: Adding to quickfix list issue

On Sunday, April 17, 2016 at 3:12:55 AM UTC+3, yega...@gmail.com wrote: > Hi, > > On Sat, Apr 16, 2016 at 3:43 PM, Yegappan Lakshmanan > <yegapp...@gmail.com> wrote: > > Hi, > > > > On Sat, Apr 16, 2016 at 12:52 PM, Ramel Eshed <rame...@gmail.com>

Re: Asynchronous screen update

On Sunday, April 17, 2016 at 11:33:50 AM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > When using “out_io”: “buffer” in the job options there are some issues > > with the screen rendering. The first one is when I try to edit the > > command line while the job’s

Adding to quickfix list issue

Adding an item to the current quickfix list causes a jump to the first item rather than keeping the current context: Download the attached file; vim -u NONE -N :source qf_test.vim -After adding 2 items, :cn, adding one more item and another :cn we are in (2 of 3) instead of (3 of 3). Thanks,

Asynchronous screen update

Hi Bram, When using “out_io”: “buffer” in the job options there are some issues with the screen rendering. The first one is when I try to edit the command line while the job’s buffer is being updated; As long as there is room in the job’s window the only problem is that I don’t see the cursor