Saturday, December 31, 2022

Re: Vim calendar for 2023 available

On 2022-12-31 19:23, Bram Moolenaar wrote:

> I have updated the handy desktop calendar for 2023.

Thank you. It looks really cool!

> It is available in English and Dutch.

Do you maybe also have, or is it easy for you to make, a Monday start
version?
I'd love to use your calendar if I could have that, because for me it
makes
sense that the weekends are grouped together at the end of the week
calendar.

Happy New Year
Ángel

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/f5cc5f428716ec002996a4a7fa0c36e7%40ugr.es.

Vim calendar for 2023 available

Happy New Year to all Vim users!

I have updated the handy desktop calendar for 2023. 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
website: https://moolenaar.net/#Calendar

Happy Vimming!

--
No man may purchase alcohol without written consent from his wife.
[real standing law in Pennsylvania, United States of America]

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221231182320.A0DCC1C0AA3%40moolenaar.net.

Simple Vim questions -- Backspace + Escape in maps

I used Vi for many years (on Unix) then stopped, but need it again (on Windows 10). There are couple of things that I used to be able to do in my sleep but no longer master, and the online information is hard to use (it talks about very complicated things but I was not able to find simple answers to simple questions).

 

1. Backspace in insert mode, over some characters, gives a special character instead of erasing. I remember that this was a feature, not a bug – a way to type special characters when they were troublesome to produce otherwise. I don't need that facility, which is very annoying; I just want backspace to erase. What should I do? My settings file (_vimrc) currently has

 

              set bs=2

 

2. How do I represent ESC in a macro (my name for the result of a "map")? I want to define something like

 

              :map v iSOME TEXT<Esc>

 

so that when I type "v" it will insert SOME_TEXT at the current position and then escape (get out of insert mode). But I no longer know how to type what appears above as <Esc> when entering the macro. I remembered various incantations involving CTRL-V or CTRL-G but they do not seem to work.

 

Very basic stuff, I just forgot.

 

Help will be much appreciated.

 

With best regards,

 

-- Bertrand Meyer

New book just out: Handbook of Requirements and Business Analysis, Springer, 2022

A treatise and textbook on requirements, see https://se.ethz.ch/requirements

 

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/245f1119-b114-44c2-929e-53d4a73ace3dn%40googlegroups.com.

Re: Multiple windows get corrupted

On Fri, 30 Dec 2022 21:17:26 -0800 (PST)
Ben Mehmet <ozumem@gmail.com> wrote:
> Could you help with recommending how to proceed with my .vimrc and
> plugins to find the culprit? I mean how should I start incorporating
> my settings in?

https://vi.stackexchange.com/questions/2003/how-do-i-debug-my-vimrc-file

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221231173841.000005df%40gmail.com.

Re: Multiple windows get corrupted

Not sure to whom you might be addressing this, but my general method would be to remove plugins and try to see if vim is still stable. Then add plugins back to the configuration until problems start to appear. That way you might find out what is causing the problem.
On Friday, December 30, 2022 at 10:17:27 PM UTC-7 ozu...@gmail.com wrote:
Got an update regarding this. As you suggested, I ran vim with --clean option and it is much more reliable and steadier than I have been experiencing for past few months. Could you help with recommending how to proceed with my .vimrc and plugins to find the culprit? I mean how should I start incorporating my settings in? 
Question 2: If I wanted to updated my vim version to 9, would it be recommended and most importantly safe to use the ppa approach? 

Thanks a lot in advance.
On Monday, December 19, 2022 at 11:03:00 PM UTC-6 3nan....@gmail.com wrote:
On Mon, 19 Dec 2022 20:55:23 +0000 (UTC)
"'hilal Adam' via vim_use" <vim...@googlegroups.com> wrote:
> Thanks for your reply. I am not sure what '$ vim --clean' does. Is
> this another way running vim? On Monday, December 19, 2022 at

You have to run it from your shell. It'll open Vim without any
user-level configuration. If the issue persists without your user-level
config, we can be sure it's a bug in Vim. But if it can't be reproduced
without '--clean', then we can be sure the problem is being caused by
your config. Either way, it'll narrow the suspects.

Read ':h --clean' for more details.

--
Enan
3nan....@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/94a5fd17-7d30-490c-8b89-7af70a0a0fb5n%40googlegroups.com.

Friday, December 30, 2022

Re: Multiple windows get corrupted

Got an update regarding this. As you suggested, I ran vim with --clean option and it is much more reliable and steadier than I have been experiencing for past few months. Could you help with recommending how to proceed with my .vimrc and plugins to find the culprit? I mean how should I start incorporating my settings in? 
Question 2: If I wanted to updated my vim version to 9, would it be recommended and most importantly safe to use the ppa approach? 

Thanks a lot in advance.
On Monday, December 19, 2022 at 11:03:00 PM UTC-6 3nan....@gmail.com wrote:
On Mon, 19 Dec 2022 20:55:23 +0000 (UTC)
"'hilal Adam' via vim_use" <vim...@googlegroups.com> wrote:
> Thanks for your reply. I am not sure what '$ vim --clean' does. Is
> this another way running vim? On Monday, December 19, 2022 at

You have to run it from your shell. It'll open Vim without any
user-level configuration. If the issue persists without your user-level
config, we can be sure it's a bug in Vim. But if it can't be reproduced
without '--clean', then we can be sure the problem is being caused by
your config. Either way, it'll narrow the suspects.

Read ':h --clean' for more details.

--
Enan
3nan....@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/6ed71d32-083f-40be-a2f2-1f1cb0454098n%40googlegroups.com.

Wednesday, December 28, 2022

Re: word count

On 12/28/22 08:26, Igor Lerinc wrote:
>we have relative numbering for lines, so we don't have to calculate when we
>want to jump between lines.
>
>But is something similar possible for words?
>For current line to show, what number of word it is? Depending on where
>cursor is?
>
>Because i don't feel like calculating how much words there is between
>cursor and word where i want to jump to. And it would be faster and
>efficient, 'to just know' how much words to jump in current line to get to
>some word

Don't you know there are vim-easymotion, vim-sneak, and many other
plugins for quick navigation? If you want pluginless, I don't come up
with an easy way to do so in a script with only a few lines.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221228174235.f4dig3wmucqxo65q%40zoho.com.

Re: word count

On Wed, 28 Dec 2022 08:26:01 -0800 (PST)
Igor Lerinc <igor.lerinc7@gmail.com> wrote:
> we have relative numbering for lines, so we don't have to calculate when we
> want to jump between lines.
>
> But is something similar possible for words?
> For current line to show, what number of word it is? Depending on where
> cursor is?
>
> Because i don't feel like calculating how much words there is between
> cursor and word where i want to jump to. And it would be faster and
> efficient, 'to just know' how much words to jump in current line to get to
> some word

Should be easy, specially if Vim has a way to add virtual text. But I
think that'd add too much noise to be useful.

I suggest using 'f' and 't' and plain searching ('/' and '?') to move
around than motions like 'nw', 'nb', 'ne', etc. (where 'n' is any
positive integer). I can't provide any statistical data supporting that
'f','t','/','?' are better, but try it out and see if it works before
investing time building a custom plugin to add "relative numbering for
words."

P.S. I don't use line numbers (relative or otherwise) either, except
when doing pair programming. I find that '/','?' are much faster and
precise and jumping to lines with 'nj','nk','nG', etc. So consider my
suggestion with enough skepticism.

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221228233703.00006573%40gmail.com.

Re: word count

Yes, but is there way for it, to show some sort of numbers relative to curson on that line. 
Some small nukber above word, idk. 
Just not to calculate how much words i need to jump, if i want to go jumping between words.


sre, 28. dec 2022. 17:56 Steve Litt <slitt@troubleshooters.com> je napisao/la:
Igor Lerinc said on Wed, 28 Dec 2022 08:26:01 -0800 (PST)

>we have relative numbering for lines, so we don't have to calculate
>when we want to jump between lines.
>
>But is something similar possible for words?
>For current line to show, what number of word it is? Depending on
>where cursor is?
>
>Because i don't feel like calculating how much words there is between
>cursor and word where i want to jump to. And it would be faster and
>efficient, 'to just know' how much words to jump in current line to
>get to some word

6w in display mode jumps you 6 words ahead.


SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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 a topic in the Google Groups "vim_use" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_use/hDg2QmgCGtc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221228115601.00354fed%40mydesk.domain.cxm.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CADZsa2rTck8sD2RNhZh8qAPBb-oO0HyccQa0cj%3DczbqR3fCjyA%40mail.gmail.com.

Re: word count

Igor Lerinc said on Wed, 28 Dec 2022 08:26:01 -0800 (PST)

>we have relative numbering for lines, so we don't have to calculate
>when we want to jump between lines.
>
>But is something similar possible for words?
>For current line to show, what number of word it is? Depending on
>where cursor is?
>
>Because i don't feel like calculating how much words there is between
>cursor and word where i want to jump to. And it would be faster and
>efficient, 'to just know' how much words to jump in current line to
>get to some word

6w in display mode jumps you 6 words ahead.


SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221228115601.00354fed%40mydesk.domain.cxm.

word count

we have relative numbering for lines, so we don't have to calculate when we want to jump between lines.

But is something similar possible for words? 
For current line to show, what number of word it is? Depending on where cursor is?

Because i don't feel like calculating how much words there is between cursor and word where i want to jump to. And it would be faster and efficient, 'to just know' how much words to jump in current line to get to some word


--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/43a8007a-debb-451e-bf31-36416f9491c0n%40googlegroups.com.

Thursday, December 22, 2022

Re: How to quickly move to a specific buffer?

On Thu, 22 Dec 2022 11:38:28 +0100
BPJ <bpj@melroch.se> wrote:
> I usually have one tab open for each buffer. Then I can jump between
> the tabs/buffers with COUNT + gt. You can set up 'tabline' to display
> the tab number and/or use :tabs (which I have mapped to <F-11>t) to
> see a list of the tabs. (Note: when I'm on termux and don't have too
> many tabs open I can just point my thumb on the tagline to switch —
> purists may shudder all they want! :-)

I did shudder, but I'm not gonna begrudge you your way. As long as it
works, no need to fix it. I just wanna add that using tabs as buffers
will keep you from using tabs as window-manager. I use tabs that way:
each tab has a set of windows, split and resized just the way I want.
The tabs are separated a/c a context. The context maybe a project (so
one tab per project) or a module (one tab for 'src/handle/', another for
'src/menu/').

Use cases:

o If I want to open a file without destroying the perfect arrangement of
windows I have got going on, I can open the file in a new tab.
o If I want to work on a different module, I can:
o Open a new tab
o ':tcd src/module/'
o ':e **/*<tab>'
That way I have a new workspace for that module.

If you don't require this workflow, or you've got a substitute for it,
using tabs as buffers won't be any less pure. If not, maybe you can do
a intuitive cost-benefit analysis and see if adopting a different
approach (buffers as buffers and tabs as window-manager) seems better.

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221222180805.0f803047%40cirdan.

Re: How to quickly move to a specific buffer?

I usually have one tab open for each buffer. Then I can jump between the tabs/buffers with COUNT + gt. You can set up 'tabline' to display the tab number and/or use :tabs (which I have mapped to <F-11>t) to see a list of the tabs. (Note: when I'm on termux and don't have too many tabs open I can just point my thumb on the tagline to switch — purists may shudder all they want! :-)

Den ons 14 dec. 2022 02:10Steve Litt <slitt@troubleshooters.com> skrev:
Hi all,

I typically use :bn and :bp to move between buffers, but I have five
buffers open on my current project, which requires a heck of a lot of
keystrokes to move to a specific buffer. So I'd like a command to bring
up a list of buffers so I can chose a specific one.

I've looked up :h buffers and can't find anything. Is there a way I
could do this?

Theoretically I could use the gvim menu system to do this, but it
involves taking my hands off home position to use the arrow keys, and
also, Alt+b is a difficult hotkey, so I'd much rather have some sort of
Vim command to do it.

Thanks,

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221213200942.40af4307%40mydesk.domain.cxm.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CADAJKhC2HdbnR-gDpmy7SPnh9-Am8UjmhPYP-aBOEayOUBPZ0w%40mail.gmail.com.

Monday, December 19, 2022

Re: Multiple windows get corrupted

On Mon, 19 Dec 2022 20:55:23 +0000 (UTC)
"'hilal Adam' via vim_use" <vim_use@googlegroups.com> wrote:
> Thanks for your reply. I am not sure what '$ vim --clean' does. Is
> this another way running vim? On Monday, December 19, 2022 at

You have to run it from your shell. It'll open Vim without any
user-level configuration. If the issue persists without your user-level
config, we can be sure it's a bug in Vim. But if it can't be reproduced
without '--clean', then we can be sure the problem is being caused by
your config. Either way, it'll narrow the suspects.

Read ':h --clean' for more details.

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221220110243.16fd840b%40cirdan.

Re: mysterious highlighting

Does :noh clear the highlights?

On Mon, Dec 19, 2022 at 9:28 PM Barry Gold <BarryDGold@ca.rr.com> wrote:
I'm editing a file. For some reason all occurrences of the letter "s"
are highlighted in green.

Notes:

1. I've tried searching for something else, but that doesn't change the
colors.

2. All occurrences are green, both upper- and lower-case.

Any suggestions?

--
My mottos:
It must be possible, Captain. It happened.
Run and find out.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d7d9270e-e03f-0cf8-75a0-3f187500f881%40ca.rr.com.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAOmRJrd%3DvFx-CPTUC0u1k4cGRHhm_jDYU_SV4%2BKex6xx-46OkQ%40mail.gmail.com.

mysterious highlighting

I'm editing a file. For some reason all occurrences of the letter "s"
are highlighted in green.

Notes:

1. I've tried searching for something else, but that doesn't change the
colors.

2. All occurrences are green, both upper- and lower-case.

Any suggestions?

--
My mottos:
It must be possible, Captain. It happened.
Run and find out.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d7d9270e-e03f-0cf8-75a0-3f187500f881%40ca.rr.com.

Re: Multiple windows get corrupted


Thanks for your reply. Yes, I did try Ctrl-L or the ex command :redraw as I found them when searching for similar experience from others.
I am running in GUI mode. 

Latest version meaning what? Vim 9 or the latest in 8.2xxx build? As I mentioned I am running 8.2.4919. 
However I would be glad to upgrade to Vim 9. The problem however when I tried this upgrade on a non work environment by cloning and building vim, the steps didn't mentioned how to go about populating all the other sub folders under vim. Example, plugin, syntax, colors, etc.

Thanks,
Ben
On Monday, December 19, 2022 at 04:33:02 AM CST, Christian Brabandt <cblists@256bit.org> wrote:


Am 2022-12-19 01:04, schrieb Ben Mehmet:
> When running vim (mostly) in multi-window mode in ubuntu, my windows
> get corrupted with random characters. Hard to explain, but as if the
> screen doesn't get refreshed. Like to see the actual buffer contents,
> I have to move up or down continuously. I try ctrl-r or :e with no
> result. I am on vim 8.2 and ubuntu 22.04.
> I appreciate any help with this matter.

Have you tried using `Ctrl-L` or the ex command `:redraw` (with or
without the `!`)?

Does it fix it?

Also, are you running vim in a terminal or using a GUI? Can you verify
using the latest Vim version?

Thanks,
Chris


--
--
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+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b82f0c0fb03160df7d635781d829abb9%40256bit.org.

Re: Multiple windows get corrupted

Thanks for your reply. I am not sure what '$ vim --clean' does. Is this another way running vim?

On Monday, December 19, 2022 at 12:22:05 AM CST, Enan Ajmain <3nan.ajmain@gmail.com> wrote:


Have you checked if '$ vim --clean' causes the same problem?

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N


--
--
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+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221219115946.1e45bebf%40cirdan.

Re: Atom and Substitute carraige return only in part of string

Thanks !

Le dimanche 18 décembre 2022 à 14:39:23 UTC+1, xigb...@gmail.com a écrit :
:s/\zs"[^"]\+"\ze/replace_string_here/g

On Sun, Dec 18, 2022 at 11:55 AM N i c o l a s <niva...@gmail.com> wrote:
Hi,

Getting this awfull string containing several carriage return, seome of them would to be substitute with space, seome others with nothing.

0.003^@99,"0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0","0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0",0.0,0.0,0.0,0.0001,0.003^@

Using atom, I search and fix part of string where carriage return need to be replaced by space : this is the atom pattern \zs,"[^"]\+"\ze


How to only substitute on these focused part of string ?
Thank you
N i c o l a s


--
--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ba410108-91e7-45ce-8327-f8b1d3860a34n%40googlegroups.com.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/62d1cb1f-0c41-4716-a658-90264b811b13n%40googlegroups.com.

Re: Multiple windows get corrupted

Am 2022-12-19 01:04, schrieb Ben Mehmet:
> When running vim (mostly) in multi-window mode in ubuntu, my windows
> get corrupted with random characters. Hard to explain, but as if the
> screen doesn't get refreshed. Like to see the actual buffer contents,
> I have to move up or down continuously. I try ctrl-r or :e with no
> result. I am on vim 8.2 and ubuntu 22.04.
> I appreciate any help with this matter.

Have you tried using `Ctrl-L` or the ex command `:redraw` (with or
without the `!`)?

Does it fix it?

Also, are you running vim in a terminal or using a GUI? Can you verify
using the latest Vim version?

Thanks,
Chris

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b82f0c0fb03160df7d635781d829abb9%40256bit.org.

Sunday, December 18, 2022

Re: Multiple windows get corrupted

Have you checked if '$ vim --clean' causes the same problem?

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221219115946.1e45bebf%40cirdan.

Multiple windows get corrupted

When running vim (mostly) in multi-window mode in ubuntu, my windows get corrupted with random characters. Hard to explain, but as if the screen doesn't get refreshed. Like to see the actual buffer contents, I have to move up or down continuously. I try ctrl-r or :e with no result. I am on vim 8.2 and ubuntu 22.04.
I appreciate any help with this matter.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b0909cd0-ef61-4f9e-887f-f99bea25ef94n%40googlegroups.com.

Re: Atom and Substitute carraige return only in part of string

:s/\zs"[^"]\+"\ze/replace_string_here/g

On Sun, Dec 18, 2022 at 11:55 AM N i c o l a s <nivaemail@gmail.com> wrote:
Hi,

Getting this awfull string containing several carriage return, seome of them would to be substitute with space, seome others with nothing.

0.003^@99,"0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0","0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0",0.0,0.0,0.0,0.0001,0.003^@

Using atom, I search and fix part of string where carriage return need to be replaced by space : this is the atom pattern \zs,"[^"]\+"\ze


How to only substitute on these focused part of string ?
Thank you
N i c o l a s


--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ba410108-91e7-45ce-8327-f8b1d3860a34n%40googlegroups.com.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAOmRJrfh3_DO2xL3R1rsN%2BV19uneFizNG-yPQLZ8-Q_pWgxEdg%40mail.gmail.com.

Atom and Substitute carraige return only in part of string

Hi,

Getting this awfull string containing several carriage return, seome of them would to be substitute with space, seome others with nothing.

0.003^@99,"0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0","0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0^@0;0;0",0.0,0.0,0.0,0.0001,0.003^@

Using atom, I search and fix part of string where carriage return need to be replaced by space : this is the atom pattern \zs,"[^"]\+"\ze


How to only substitute on these focused part of string ?
Thank you
N i c o l a s


--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ba410108-91e7-45ce-8327-f8b1d3860a34n%40googlegroups.com.

Thursday, December 15, 2022

Re: How to quickly move to a specific buffer?

On Wed, 14 Dec 2022 19:25:19 +0530
Yegappan Lakshmanan <yegappanl@gmail.com> wrote:
> I am referring to the former. You can enable this by adding 'fuzzy'
> to 'wildoptions'.

Damn! Didn't even know about it. Thanks.

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221215140419.0a7b8b49%40cirdan.

Wednesday, December 14, 2022

Re: How to quickly move to a specific buffer?

Since no one mentioned this:

You can use ':b<buffer number>' to move to a specific buffer.
When I forget which buffer is which number, I execute ':ls' and then I
do ':b2' for buffer number 2, ':b 1' for the first buffer, etc

On 14/12/2022 03:09, Steve Litt wrote:
> Hi all,
>
> I typically use :bn and :bp to move between buffers, but I have five
> buffers open on my current project, which requires a heck of a lot of
> keystrokes to move to a specific buffer. So I'd like a command to bring
> up a list of buffers so I can chose a specific one.
>
> I've looked up :h buffers and can't find anything. Is there a way I
> could do this?
>
> Theoretically I could use the gvim menu system to do this, but it
> involves taking my hands off home position to use the arrow keys, and
> also, Alt+b is a difficult hotkey, so I'd much rather have some sort of
> Vim command to do it.
>
> Thanks,
>
> SteveT
>
> Steve Litt
> Autumn 2022 featured book: Thriving in Tough Times
> http://www.troubleshooters.com/bookstore/thrive.htm
>

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/5978a826-1d6c-0395-b789-f8c5c7c1d3ca%40ifohancroft.com.

RE: version 9.0 and patches

Thanks Christian for the quick response. I appreciate it.

-----Original Message-----
From: vim_use@googlegroups.com <vim_use@googlegroups.com> On Behalf Of Christian Brabandt
Sent: Wednesday, December 14, 2022 2:30 AM
To: vim@vim.org
Subject: Re: version 9.0 and patches


On Di, 13 Dez 2022, Michael.Pearson2 via vim_use wrote:

> CVE-2022-4293

The fix is https://urldefense.com/v3/__https://github.com/vim/vim/releases/tag/v9.0.0804__;!!F9svGWnIaVPGSwU!vrh874nmeohti4UEIda_BF8Ao4x547JXxUo69xP-fQUnEQO7Ig9KSNn4A6sgfy8j_Xe3Q7J465f2ve7jXYv3b-BgQ1mQ$

> CVE-2022-4292

The fix is https://urldefense.com/v3/__https://github.com/vim/vim/releases/tag/v9.0.0882__;!!F9svGWnIaVPGSwU!vrh874nmeohti4UEIda_BF8Ao4x547JXxUo69xP-fQUnEQO7Ig9KSNn4A6sgfy8j_Xe3Q7J465f2ve7jXYv3b9Qj6x9L$

> CVE-2022-3491

The fix is https://urldefense.com/v3/__https://github.com/vim/vim/releases/tag/v9.0.0742__;!!F9svGWnIaVPGSwU!vrh874nmeohti4UEIda_BF8Ao4x547JXxUo69xP-fQUnEQO7Ig9KSNn4A6sgfy8j_Xe3Q7J465f2ve7jXYv3b5956pnU$

> CVE-2022-3520

The fix is https://urldefense.com/v3/__https://github.com/vim/vim/releases/tag/v9.0.0765__;!!F9svGWnIaVPGSwU!vrh874nmeohti4UEIda_BF8Ao4x547JXxUo69xP-fQUnEQO7Ig9KSNn4A6sgfy8j_Xe3Q7J465f2ve7jXYv3b7g0mryc$

> CVE-2022-3591

The fix is https://urldefense.com/v3/__https://github.com/vim/vim/releases/tag/v9.0.0789__;!!F9svGWnIaVPGSwU!vrh874nmeohti4UEIda_BF8Ao4x547JXxUo69xP-fQUnEQO7Ig9KSNn4A6sgfy8j_Xe3Q7J465f2ve7jXYv3b0W1muXt$

> Is there a cumulative patch for version 9 that will encompass all the
> patches for all the following CVE's?

No, we do not provide cumulative patches. If you are installing vim, best is always to go from the lastest patch in the master branch and keep it updated regularly.

If you are using a Distribution with Security Support, it will probably take care of those. But you should check with the maintainers separately to be sure.


Best,
Christian
--
Gib einem Mann einen Fisch und du ernährst ihn für einen Tag.
Lehre einen Mann zu fischen und du ernährst ihn für sein Leben.
-- Konfuzius (551-479 v. Chr.)

--
--
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 https://urldefense.com/v3/__http://www.vim.org/maillist.php__;!!F9svGWnIaVPGSwU!vrh874nmeohti4UEIda_BF8Ao4x547JXxUo69xP-fQUnEQO7Ig9KSNn4A6sgfy8j_Xe3Q7J465f2ve7jXYv3b2AcD4a_$

---
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://urldefense.com/v3/__https://groups.google.com/d/msgid/vim_use/20221214083005.GD3184211*40256bit.org__;JQ!!F9svGWnIaVPGSwU!vrh874nmeohti4UEIda_BF8Ao4x547JXxUo69xP-fQUnEQO7Ig9KSNn4A6sgfy8j_Xe3Q7J465f2ve7jXYv3b5D7Wf1Z$ .

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/58cbf038cf9e468e8ce7e98d45fdaacd%40wellsfargo.com.

Re: How to quickly move to a specific buffer?

I have this in my setup

set wildmenu
set wildoptions=pum,fuzzy


With this, the command fuzzy-completes in a pop-up window.

On Wed, Dec 14, 2022 at 1:55 PM Yegappan Lakshmanan <yegappanl@gmail.com> wrote:


On Wed, Dec 14, 2022 at 11:09 AM Enan Ajmain <3nan.ajmain@gmail.com> wrote:
On Wed, 14 Dec 2022 08:26:03 +0530
Yegappan Lakshmanan <yegappanl@gmail.com> wrote:
> Starting with Vim9, fuzzy completion of buffer names is supported.

By fuzzy completion, do you mean ':b cdent' should expand to a buffer
'src/cindent.c'? or do you mean I need to use ':b c*dent'?  Because the
latter is slightly different, I wouldn't necessarily call that fuzzy.

I am referring to the former.  You can enable this by adding 'fuzzy' to 'wildoptions'.

- Yegappan

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAAW7x7kEk4A0TMwPHcaFttftqQjLcO5ttczW%2BUgL_DbLm7OVKA%40mail.gmail.com.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAOmRJreTy0m%3D%2BYcZN3mZ5mtVc540iaOLazSTqpVntGj%2BA4pUNQ%40mail.gmail.com.

Re: version 9.0 and patches

macvim is available at:

https://github.com/macvim-dev

OP didn't mention an OS and for those looking for a (macOS) gui vi.  It compiles to both terminal and gui versions.
(not associated in anyway with  it other than as a user)
On Wednesday, December 14, 2022 at 7:34:36 AM UTC-5 antoine.m...@gmail.com wrote:
On Wed, Dec 14, 2022 at 9:30 AM Christian Brabandt <cbl...@256bit.org> wrote:
> On Di, 13 Dez 2022, Michael.Pearson2 via vim_use wrote:
[...]
> > Is there a cumulative patch for version 9 that will encompass all the
> > patches for all the following CVE's?
>
> No, we do not provide cumulative patches. If you are installing vim,
> best is always to go from the lastest patch in the master branch and
> keep it updated regularly.
>
> If you are using a Distribution with Security Support, it will probably
> take care of those. But you should check with the maintainers separately
> to be sure.

I agree with Christian, and in addition, if you can (or can learn to)
compile your own Vim (it is not outlandishly difficult, it just takes
a little getting used to), the latest source is available on both a
git repository on github, maintained directly by Bram (see
https://www.vim.org/git.php for info) and a Mercurial repository
maintained by Christian at https://hg.256bit.org/vim mirrorring Bram's
git repository (see https://www.vim.org/mercurial.php for details).

I used to have a pair of HowTo pages, about compiling Vim on Windows
and on Linux (and other Unix-like systems), but my ISP (Belgacom
Skynet aka Proximus) has removed all user sites not maintained by
their own engineers, and I wasn't ready to let other people decide how
my user site should look. I still have HTML backups of this user site
but, alas, they are not available on the Web anymore.

Best regards,
Tony.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/8688cb4d-c028-4ddb-84f0-38afd09f9076n%40googlegroups.com.

Re: How to quickly move to a specific buffer?



On Wed, Dec 14, 2022 at 11:09 AM Enan Ajmain <3nan.ajmain@gmail.com> wrote:
On Wed, 14 Dec 2022 08:26:03 +0530
Yegappan Lakshmanan <yegappanl@gmail.com> wrote:
> Starting with Vim9, fuzzy completion of buffer names is supported.

By fuzzy completion, do you mean ':b cdent' should expand to a buffer
'src/cindent.c'? or do you mean I need to use ':b c*dent'?  Because the
latter is slightly different, I wouldn't necessarily call that fuzzy.

I am referring to the former.  You can enable this by adding 'fuzzy' to 'wildoptions'.

- Yegappan

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAAW7x7kEk4A0TMwPHcaFttftqQjLcO5ttczW%2BUgL_DbLm7OVKA%40mail.gmail.com.

Re: How to quickly move to a specific buffer?



On Wed, Dec 14, 2022 at 8:55 AM Steve Litt <slitt@troubleshooters.com> wrote:
Yegappan Lakshmanan said on Wed, 14 Dec 2022 08:26:03 +0530

>Starting with Vim9, fuzzy completion of buffer names is supported.
>
>- Yegappan

I did :h fuzzy but it said nothing about fuzzy completion. How do I
achieve fuzzy completion, and how much of the filename (or something
else) do I have to type in?

You need to add 'fuzzy' to 'wildoptions'.  This enables fuzzy completion for command line completion.

- Yegappan

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAAW7x7%3D5zbAHhr-usRgt2SKqdFH0gohJ%2BSVV33%2BfAYCfPM0ktg%40mail.gmail.com.

Re: version 9.0 and patches

On Wed, Dec 14, 2022 at 9:30 AM Christian Brabandt <cblists@256bit.org> wrote:
> On Di, 13 Dez 2022, Michael.Pearson2 via vim_use wrote:
[...]
> > Is there a cumulative patch for version 9 that will encompass all the
> > patches for all the following CVE's?
>
> No, we do not provide cumulative patches. If you are installing vim,
> best is always to go from the lastest patch in the master branch and
> keep it updated regularly.
>
> If you are using a Distribution with Security Support, it will probably
> take care of those. But you should check with the maintainers separately
> to be sure.

I agree with Christian, and in addition, if you can (or can learn to)
compile your own Vim (it is not outlandishly difficult, it just takes
a little getting used to), the latest source is available on both a
git repository on github, maintained directly by Bram (see
https://www.vim.org/git.php for info) and a Mercurial repository
maintained by Christian at https://hg.256bit.org/vim mirrorring Bram's
git repository (see https://www.vim.org/mercurial.php for details).

I used to have a pair of HowTo pages, about compiling Vim on Windows
and on Linux (and other Unix-like systems), but my ISP (Belgacom
Skynet aka Proximus) has removed all user sites not maintained by
their own engineers, and I wasn't ready to let other people decide how
my user site should look. I still have HTML backups of this user site
but, alas, they are not available on the Web anymore.

Best regards,
Tony.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXt8%3DP%3DH286JSwa0-7uX2gsrAqN6TkOdBHNqa5_9niESAw%40mail.gmail.com.

Re: version 9.0 and patches

On Di, 13 Dez 2022, Michael.Pearson2 via vim_use wrote:

> CVE-2022-4293

The fix is https://github.com/vim/vim/releases/tag/v9.0.0804

> CVE-2022-4292

The fix is https://github.com/vim/vim/releases/tag/v9.0.0882

> CVE-2022-3491

The fix is https://github.com/vim/vim/releases/tag/v9.0.0742

> CVE-2022-3520

The fix is https://github.com/vim/vim/releases/tag/v9.0.0765

> CVE-2022-3591

The fix is https://github.com/vim/vim/releases/tag/v9.0.0789

> Is there a cumulative patch for version 9 that will encompass all the
> patches for all the following CVE's?

No, we do not provide cumulative patches. If you are installing vim,
best is always to go from the lastest patch in the master branch and
keep it updated regularly.

If you are using a Distribution with Security Support, it will probably
take care of those. But you should check with the maintainers separately
to be sure.


Best,
Christian
--
Gib einem Mann einen Fisch und du ernährst ihn für einen Tag.
Lehre einen Mann zu fischen und du ernährst ihn für sein Leben.
-- Konfuzius (551-479 v. Chr.)

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221214083005.GD3184211%40256bit.org.

Re: How to quickly move to a specific buffer?

On 12/13/22 20:09, Steve Litt wrote:
>Hi all,
>
>I typically use :bn and :bp to move between buffers, but I have five
>buffers open on my current project, which requires a heck of a lot of
>keystrokes to move to a specific buffer. So I'd like a command to bring
>up a list of buffers so I can chose a specific one.
>
>I've looked up :h buffers and can't find anything. Is there a way I
>could do this?
>
>Theoretically I could use the gvim menu system to do this, but it
>involves taking my hands off home position to use the arrow keys, and
>also, Alt+b is a difficult hotkey, so I'd much rather have some sort of
>Vim command to do it.

Do you want to do it in a barebone vim (i.e) no plugin way, or you are
opt to use plugin to do that?

Might be a bit offtopic here, I use neovim, so to find a buffer I use
"Telescope buffers". As what I remembered, LeaderF, Coc.nvim, and
fzf.vim might be the alternatives in vim.

And if you want to do it in the cmdline, then ":ls" to show all buffers
and then":b xxx" might be the only viable solution. The default vim's
completion system works not that good, it is neither case-insensitive
nor fuzzable (it works similar to the default bash?). I used nvim-cmp as
my auto-completion framework which also works in cmdline, so when I type
":b xxx" an auto-completion popup invokes and I can just complete it
with fuzzy matching. What first comes in my mind of the alternative of
nvim-cmp in vim is coc.nvim, but there are definetely other
alternatives.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/MW4PR14MB532784D6147EA9230DC8BF95E7E09%40MW4PR14MB5327.namprd14.prod.outlook.com.

Re: How to quickly move to a specific buffer?

On Tue, Dec 13, 2022 at 7:22 PM Steve Litt <slitt@troubleshooters.com> wrote:
Arun said on Tue, 13 Dec 2022 18:22:41 -0800

>Usually, I :split open (maximized) my active files

For me, :split only makes 2 windows, not a window for every buffer.

# vim -o <file1> <file2> ..

If you are already inside vim, you can either manually run ":split <file1>", ":split <file2>" .. OR
    :bufdo split (Close those you do not want)

One nice tip here is that, once you place your buffers in vim to your taste, you can run the command:
    :mksession <session-file>
..to save those windows placement. Later run
    :source <session-file>
..to restore the view. That is a huge time saver sometimes.


> and switch back and
>forth using some helpful mappings (Alt-j and Alt-k). When the number of
>splits are more, I open a tab

I looked up :h tab and found stuff seemingly unrelated. How does one
open a tab?

Either use:
    $ vim -p <file1> <file2> ..
..or inside vime:
    :tabe <file1>

:help tabedit

Regards,
-Arun 

Thanks,

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221213222241.6a9eb820%40mydesk.domain.cxm.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJUkyiG0cDm3h46DVT03NrA8SWSoA%2BNX_quvz7-KmwZj6imDcg%40mail.gmail.com.

Tuesday, December 13, 2022

Re: How to quickly move to a specific buffer?

On Tue, 13 Dec 2022 22:22:41 -0500
Steve Litt <slitt@troubleshooters.com> wrote:
> For me, :split only makes 2 windows, not a window for every buffer.

I don't think you wanted this, because I have never used it, but if you
do want to open windows for each buffer, you can use ':h bufdo'.

:bufdo split
:bufdo vsplit

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221214122625.4ed63c91%40cirdan.

Re: How to quickly move to a specific buffer?

On Wed, 14 Dec 2022 08:26:03 +0530
Yegappan Lakshmanan <yegappanl@gmail.com> wrote:
> Starting with Vim9, fuzzy completion of buffer names is supported.

By fuzzy completion, do you mean ':b cdent' should expand to a buffer
'src/cindent.c'? or do you mean I need to use ':b c*dent'? Because the
latter is slightly different, I wouldn't necessarily call that fuzzy.

--
Enan
3nan.ajmain@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221214113932.27466e4e%40cirdan.

Re: How to quickly move to a specific buffer?

Steve Litt said on Tue, 13 Dec 2022 22:29:15 -0500


>2) F5 is a very inconvenient hotkey. Is there a way I could use
> Shift+Ctrl+n ? How would I change the <F5> to change it to
> Shift+Ctrl+n ?

I figured it out. Shift+Ctrl+n is <s-c-n>. Two consecutive pushes of
Alt+n is <a-n><a-n>. Both of those are better for me than F5, and both
are sufficient for my needs.

So this is the solution I'm going to use.

Thanks,

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221213224925.536a603d%40mydesk.domain.cxm.

Re: How to quickly move to a specific buffer?

Lang Hurst said on Tue, 13 Dec 2022 17:28:39 -0800

>I copied this off the vim website, I think. In my .vimrc
>
> nnoremap <F5> :buffers<CR>:buffer<Space>
>
>Hit F5, just enter the number of the listed buffers.

This is almost exactly what I need, the two exceptions being:

1) It becomes very time consuming if the number of buffers exceeds the
height of the Vim window. However, this will usually not be the case.

2) F5 is a very inconvenient hotkey. Is there a way I could use
Shift+Ctrl+n ? How would I change the <F5> to change it to
Shift+Ctrl+n ?

Thanks,

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221213222915.35051c0d%40mydesk.domain.cxm.

Re: How to quickly move to a specific buffer?

Yegappan Lakshmanan said on Wed, 14 Dec 2022 08:26:03 +0530

>Starting with Vim9, fuzzy completion of buffer names is supported.
>
>- Yegappan

I did :h fuzzy but it said nothing about fuzzy completion. How do I
achieve fuzzy completion, and how much of the filename (or something
else) do I have to type in?

Thanks,

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221213222455.477279ec%40mydesk.domain.cxm.

Re: How to quickly move to a specific buffer?

Arun said on Tue, 13 Dec 2022 18:22:41 -0800

>Usually, I :split open (maximized) my active files

For me, :split only makes 2 windows, not a window for every buffer.

> and switch back and
>forth using some helpful mappings (Alt-j and Alt-k). When the number of
>splits are more, I open a tab

I looked up :h tab and found stuff seemingly unrelated. How does one
open a tab?

Thanks,

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20221213222241.6a9eb820%40mydesk.domain.cxm.

Re: How to quickly move to a specific buffer?


Starting with Vim9, fuzzy completion of buffer names is supported.

- Yegappan

On Wed, Dec 14, 2022 at 8:16 AM Tim Chase <vim@tim.thechases.com> wrote:
On 2022-12-13 20:29, John Passaro wrote:
> and ^6 is not only good for going between two, not if you have
> three and can remember their buffer numbers via :ls, <n>^6 takes
> you to buffer number n.

You've pointed out the critical failure here...my inability to
remember more than one (alternate) buffer-number. ;-)

-tim




--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/Y5k47e50ery1DfMQ%40thechases.com.

--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAAW7x7kMZSVQZOjy_UHgNP0Y6TLPSw%2BLvBqhcmZv77Kzs1EcZw%40mail.gmail.com.