English and Russian layouts vs mappings
Hi! Sicne I use both Russian and English keyboard layouts, obviously, I face the usual problem that pressing a Russian letter in Normal mode doesn't produce a command. Luckily, Vim has the `langmap` setting, which allows to tie my Russian keyboard layout with the English one. This makes default commands (like `G` or `yy`) working in Normal mode without switching layouts. However, _remapped_ commands (like `Y` for `y$`) or Leader-mappings (like `b`) still do not work (pressing the latter, for example, results in `word back`, as per `b` command). Is it possible somehow to make this work? Trying `langremap` or `nolangremap` doesn't affect the situation, too. Thanks. -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Capturing the exit status of 'makeprg'
I was working on a plugin in which I wanted to capture the exit status of my 'makeprg', preferably using v:shell_error. The trouble was that on Unix, 'shellpipe' is "2>&1| tee", so that following :make, v:shell_error contained the exit status of tee and not of 'makeprg'. I solved the problem by using bash's PIPESTATUS array variable to access the exit status of the first command in the :make pipeline and modifying 'shellpipe' to exit with that status. let l:save_sp = let .= " %s; exit ${PIPESTATUS[0]}" make " v:shell_error now contains the exit status of 'makeprg'. let = l:save_sp Let me know if there's a better way to do that. In the meantime, I hope someone finds that useful. Regards, Gary -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
What is gained by the extra level of map indirection recommended in help?
The 'write-plugin' section of the help recommends the following 3-level map approach: map ,c TypecorrAdd noremap
RE: List is quiet
All of us in the USA are recuperating from the Thanksgiving meals and the shopping we did over the weekend... > -Original Message- > From: vim_use@googlegroups.com [mailto:vim_use@googlegroups.com] On Behalf Of > Sven Guckes > Sent: Tuesday, November 29, 2016 7:56 AM > To: v...@vim.org > Subject: Re: List is quiet > > * Efraim Yawitz[2016-11-29 14:52]: > > Is there some problem with this mailing list? I haven't gotten > > any messages for a few days, and a message I wrote last week about > > a folding-related bug hasn't been answered or acknowledged. > > I sent it to vim_use@googlegroups.com if that matters. > > "it' quiet... *too* quiet!" ;-) > > yeah.. quiet it was. > > Sven > > 65279 N L 2016-Nov-03 Bram Moolenaar |1,9K|Re: Can I count on buffer > numbers never being re-us > 65395 ! 2016-Nov-06 Bram Moolenaar |3,3K|Updated Vim 8.0 available > with 69 patches > 65503 N L 2016-Nov-10 kamaraju kusumanchi |0,7K|print full file name > 65505 N L 2016-Nov-09 JohnBeckett |0,9K|Re: print full file name > 65506 N L 2016-Nov-09 JohnBeckett |0,9K|Re: print full file name > 65546 N L 2016-Nov-10 kamaraju kusumanchi |1,1K|Re: print full file name > 65547 N L 2016-Nov-10 kamaraju kusumanchi |1,1K|Re: print full file name > 65548 N L 2016-Nov-10 h_east |1,4K|Re: print full file name > 65549 N L 2016-Nov-10 h_east |1,4K|Re: print full file name > 65551 N L 2016-Nov-11 kamaraju kusumanchi |0,7K|Re: print full file name > 65552 N L 2016-Nov-11 kamaraju kusumanchi |0,7K|Re: print full file name > 65783 N L 2016-Nov-20 Severin Weingarten |1,1K|system() slow in Win10 Pro, > but not Home > 66002 L 2016-Nov-29 Efraim Yawitz |2,0K|List is quiet > 66003 L 2016-Nov-29 Paolo Bolzoni |1,4K|Re: List is quiet > 66004 L 2016-Nov-29 Paolo Bolzoni |1,4K|Re: List is quiet > > -- > -- > You received this message from the "vim_use" 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 Google Groups > "vim_use" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > vim_use+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Fold-related bug and pointer to fix
On Tue, Nov 29, 2016 at 7:02 PM, Ben Fritzwrote: > On Wednesday, November 23, 2016 at 4:39:24 AM UTC-6, Efraim Yawitz wrote: > > I had the following problem and I think it is a bug in some fold-related > code: > > > > I was trying to use the NarrowRegion plugin to do diffs between two > functions in the same file by creating narrowed buffers for each function > and calling :diffthis on them. When I tried to do this using folds, i.e. > :.,+2NarrowRegion to create a buffer for a folded-up function which looked > like this: > > > > int FuncName() { > > .folded > > } > > > > I got everything but the final brace in the narrowed buffer. Eventually > I discovered that this has nothing to do with NarrowRegion, but just a yank > such as: > > > > :.,+2y > > > > over a fold gives only the folded lines but not the line after the fold. > > > > A normal command of y2j works just fine and gets the line after the > fold. > > I can confirm this looks like a bug, seeing the same behavior in 64-bit > Vim 8.0.95 on Windows 7. > > It gets worse actually. I tried several yanks from code that looks like > this in Vim: > > else > { ---3 lines folded--- } > #endif > > if ( ---2 lines folded--- ) > > With the cursor on the top "else" line: > > :.,+2y yanks only the "else" and the folded lines beneath, when I expect > to also get the #endif > > :.,+3y yanks the exact same thing (omitting the #endif *and* the empty > line) > > :.,+4y finally includes the #endif (with nothing after it) but I expected > it to yank everything from "else" to the content of the second folded > section. > > The :d command acts in the same way. > > It appears something is wrong with handling of folded lines in the ranges > specified for ex commands. > > Forwarding to vim_dev as this appears to be a bug. > Thanks. As I wrote before, the handling of folds in do_one_cmd just has one call to hasFolding() for the end of the fold while in cursor_down() in edit.c, there is the following code which seems to take care of all folds: #ifdef FEAT_FOLDING if (hasAnyFolding(curwin)) { linenr_Tlast; /* count each sequence of folded lines as one logical line */ while (n--) { if (hasFolding(lnum, NULL, )) lnum = last + 1; else ++lnum; if (lnum >= curbuf->b_ml.ml_line_count) break; } if (lnum > curbuf->b_ml.ml_line_count) lnum = curbuf->b_ml.ml_line_count; } else #endif > > -- > -- > You received this message from the "vim_use" 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 Google Groups > "vim_use" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vim_use+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Fold-related bug and pointer to fix
On Wednesday, November 23, 2016 at 4:39:24 AM UTC-6, Efraim Yawitz wrote: > I had the following problem and I think it is a bug in some fold-related code: > > I was trying to use the NarrowRegion plugin to do diffs between two functions > in the same file by creating narrowed buffers for each function and calling > :diffthis on them. When I tried to do this using folds, i.e. > :.,+2NarrowRegion to create a buffer for a folded-up function which looked > like this: > > int FuncName() { > .folded > } > > I got everything but the final brace in the narrowed buffer. Eventually I > discovered that this has nothing to do with NarrowRegion, but just a yank > such as: > > :.,+2y > > over a fold gives only the folded lines but not the line after the fold. > > A normal command of y2j works just fine and gets the line after the fold. I can confirm this looks like a bug, seeing the same behavior in 64-bit Vim 8.0.95 on Windows 7. It gets worse actually. I tried several yanks from code that looks like this in Vim: else { ---3 lines folded--- } #endif if ( ---2 lines folded--- ) With the cursor on the top "else" line: :.,+2y yanks only the "else" and the folded lines beneath, when I expect to also get the #endif :.,+3y yanks the exact same thing (omitting the #endif *and* the empty line) :.,+4y finally includes the #endif (with nothing after it) but I expected it to yank everything from "else" to the content of the second folded section. The :d command acts in the same way. It appears something is wrong with handling of folded lines in the ranges specified for ex commands. Forwarding to vim_dev as this appears to be a bug. -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: List is quiet
* Efraim Yawitz[2016-11-29 14:52]: > Is there some problem with this mailing list? I haven't gotten > any messages for a few days, and a message I wrote last week about > a folding-related bug hasn't been answered or acknowledged. > I sent it to vim_use@googlegroups.com if that matters. "it' quiet... *too* quiet!" ;-) yeah.. quiet it was. Sven 65279 N L 2016-Nov-03 Bram Moolenaar |1,9K|Re: Can I count on buffer numbers never being re-us 65395 ! 2016-Nov-06 Bram Moolenaar |3,3K|Updated Vim 8.0 available with 69 patches 65503 N L 2016-Nov-10 kamaraju kusumanchi |0,7K|print full file name 65505 N L 2016-Nov-09 JohnBeckett |0,9K|Re: print full file name 65506 N L 2016-Nov-09 JohnBeckett |0,9K|Re: print full file name 65546 N L 2016-Nov-10 kamaraju kusumanchi |1,1K|Re: print full file name 65547 N L 2016-Nov-10 kamaraju kusumanchi |1,1K|Re: print full file name 65548 N L 2016-Nov-10 h_east |1,4K|Re: print full file name 65549 N L 2016-Nov-10 h_east |1,4K|Re: print full file name 65551 N L 2016-Nov-11 kamaraju kusumanchi |0,7K|Re: print full file name 65552 N L 2016-Nov-11 kamaraju kusumanchi |0,7K|Re: print full file name 65783 N L 2016-Nov-20 Severin Weingarten |1,1K|system() slow in Win10 Pro, but not Home 66002 L 2016-Nov-29 Efraim Yawitz |2,0K|List is quiet 66003 L 2016-Nov-29 Paolo Bolzoni |1,4K|Re: List is quiet 66004 L 2016-Nov-29 Paolo Bolzoni |1,4K|Re: List is quiet -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: List is quiet
I can read you. Perhaps is just a quiet moment. (I see this email from v...@vim.org though) On Tue, Nov 29, 2016 at 2:21 PM, Efraim Yawitzwrote: > Is there some problem with this mailing list? I haven't gotten any messages > for a few days, and a message I wrote last week about a folding-related bug > hasn't been answered or acknowledged. I sent it to vim_use@googlegroups.com > if that matters. > > Thanks, > > Ephraim > > -- > -- > You received this message from the "vim_use" 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 Google Groups > "vim_use" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vim_use+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
List is quiet
Is there some problem with this mailing list? I haven't gotten any messages for a few days, and a message I wrote last week about a folding-related bug hasn't been answered or acknowledged. I sent it to vim_use@googlegroups.com if that matters. Thanks, Ephraim -- -- You received this message from the "vim_use" 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 Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.