Wednesday, December 18, 2024

Re: Search anomaly?

On Wed, Dec 18, 2024 at 12:06 PM Christian Brabandt <cblists@256bit.org> wrote:

On Wed, 18 Dec 2024, Arun E wrote:

> With a buffer having just..
>
> aaa
> bbb
> aaa
>
> ..and with the cursor on the first 'a' on the first line, when you search for 'aa', the hit on the first line -- the 'aa' starting at column 2 -- is not found, rather the cursor lands on the 3rd line. Is this a documented behavior? It is
> the same behaviour in vim 8 and 9. I have not tried other versions.
>
> Playing around on it a bit more, I kinda understand why. Vim seems to try to match the "aa" in the current position, and avoid the 'a' in column 2 for subsequent matches. A zero width pattern seems to hit all occurrences (\(aa\)\@=).
>

Yes, I see the same going back to vim74. Interestingly traditional ex-vi
behaves the same, while nvi jumps by each single "a" forward (which is
also confusing: on a line like this:
aaaaaa
and then searching for aa and hitting n
the cursor will move only by a single a forward, while I would expect it
to move by 2 "a")

Ah, I see, thanks for the results on different editors.

Though out of the norm, I like the nvi behavior. Glad to know that vim
also could mimic that.
 

I checked the POSIX specs, but it doesn't mention anything about it (or
I did not find it).

> Anyway, the current behavior is very confusing, perhaps should be
> documented if not done already.

It's hard to find and hard to understand, but :h cpo-c let's you
configure this.

I had a hunch (or maybe I read sometime ago) that it would be in cpo, but thanks for pointing
out exactly where it is. Though I want that behavior, I will just use that on a need
basis. I am sure it is going to break many plugins if I turn it on unconditionally.

Thanks again Christian!

Regards,
-Arun


Best,
Christian
--
"For the most part, Democrats don't question the Republican's right to govern
when they win elections"

Heck, Democrats don't question the Republican's right to govern even when
Democrats win elections.
    -- Moopheus, on scienceblogs.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 visit https://groups.google.com/d/msgid/vim_use/Z2MrRq/NT2kNOoKA%40256bit.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 visit https://groups.google.com/d/msgid/vim_use/CAJUkyiH8dUP1SNPo5GzHb2c878k6rZ3KHZo_bRa%3DWLHdqmPixg%40mail.gmail.com.

Re: Search anomaly?

Don't know if this helps but if you have 
aaaa

Vim will find the first set of aa's and go to the second set of aa's as if it was 'aa aa'.  Assuming because it already included the 2nd a in the first set of aa's.

On Wed, Dec 18, 2024 at 2:22 PM Arun E <aemails@gmail.com> wrote:
Hi,

With a buffer having just..

aaa
bbb
aaa

..and with the cursor on the first 'a' on the first line, when you search for 'aa', the hit on the first line -- the 'aa' starting at column 2 -- is not found, rather the cursor lands on the 3rd line. Is this a documented behavior? It is the same behaviour in vim 8 and 9. I have not tried other versions.

Playing around on it a bit more, I kinda understand why. Vim seems to try to match the "aa" in the current position, and avoid the 'a' in column 2 for subsequent matches. A zero width pattern seems to hit all occurrences (\(aa\)\@=).

Anyway, the current behavior is very confusing, perhaps should be documented if not done already.

Regards,
-Arun

--
--
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 visit https://groups.google.com/d/msgid/vim_use/CAJUkyiFUkaBcKLXDh-CBNSZGYqATaUOMYz2tOqAQuOzD4uNFRA%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 visit https://groups.google.com/d/msgid/vim_use/CANrhvDEiFh%2BSdRFS9XhyXBaa7bQFnwW7BUsJYTKgHZ1NQGNREQ%40mail.gmail.com.

Re: Search anomaly?

On Wed, 18 Dec 2024, Arun E wrote:

> With a buffer having just..
>
> aaa
> bbb
> aaa
>
> ..and with the cursor on the first 'a' on the first line, when you search for 'aa', the hit on the first line -- the 'aa' starting at column 2 -- is not found, rather the cursor lands on the 3rd line. Is this a documented behavior? It is
> the same behaviour in vim 8 and 9. I have not tried other versions.
>
> Playing around on it a bit more, I kinda understand why. Vim seems to try to match the "aa" in the current position, and avoid the 'a' in column 2 for subsequent matches. A zero width pattern seems to hit all occurrences (\(aa\)\@=).
>

Yes, I see the same going back to vim74. Interestingly traditional ex-vi
behaves the same, while nvi jumps by each single "a" forward (which is
also confusing: on a line like this:
aaaaaa
and then searching for aa and hitting n
the cursor will move only by a single a forward, while I would expect it
to move by 2 "a")

I checked the POSIX specs, but it doesn't mention anything about it (or
I did not find it).

> Anyway, the current behavior is very confusing, perhaps should be
> documented if not done already.

It's hard to find and hard to understand, but :h cpo-c let's you
configure this.

Best,
Christian
--
"For the most part, Democrats don't question the Republican's right to govern
when they win elections"

Heck, Democrats don't question the Republican's right to govern even when
Democrats win elections.
-- Moopheus, on scienceblogs.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 visit https://groups.google.com/d/msgid/vim_use/Z2MrRq/NT2kNOoKA%40256bit.org.

Search anomaly?

Hi,

With a buffer having just..

aaa
bbb
aaa

..and with the cursor on the first 'a' on the first line, when you search for 'aa', the hit on the first line -- the 'aa' starting at column 2 -- is not found, rather the cursor lands on the 3rd line. Is this a documented behavior? It is the same behaviour in vim 8 and 9. I have not tried other versions.

Playing around on it a bit more, I kinda understand why. Vim seems to try to match the "aa" in the current position, and avoid the 'a' in column 2 for subsequent matches. A zero width pattern seems to hit all occurrences (\(aa\)\@=).

Anyway, the current behavior is very confusing, perhaps should be documented if not done already.

Regards,
-Arun

--
--
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 visit https://groups.google.com/d/msgid/vim_use/CAJUkyiFUkaBcKLXDh-CBNSZGYqATaUOMYz2tOqAQuOzD4uNFRA%40mail.gmail.com.

Monday, December 16, 2024

Re: What would be an easy way for me to learn Vim9script?

Good afternoon,

A free Vim9script tutorial is apparently a lacuna to be filled;
there are some assorted observations such as [0] and [1], but
something more systematic I could only find [2] which only shows 
the source code which is mostly wrong as it declares vim9script but uses 
legacy vimscript if one looks for example at 05_dictionaries.vim. 
Ideal to get converts up to speed would be the readership of this mailing list
contributing to this pull request [3] for LearnXinYMinutes. 

   Enno

[3] https://github.com/adambard/learnxinyminutes-docs/pull/5215

Le samedi 14 décembre 2024 à 23:21:10 UTC+1, Steve Litt a écrit :
Hi all,

What would be an easy way for me to learn to use Vim9script? I have a
lot of things to do so this would need to be relatively quick.

Thanks,

SteveT

Steve Litt
http://444domains.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 visit https://groups.google.com/d/msgid/vim_use/c2de4d8b-7f20-4ce8-8a72-7dc8ee001e7an%40googlegroups.com.

Saturday, December 14, 2024

What would be an easy way for me to learn Vim9script?

Hi all,

What would be an easy way for me to learn to use Vim9script? I have a
lot of things to do so this would need to be relatively quick.

Thanks,

SteveT

Steve Litt
http://444domains.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 visit https://groups.google.com/d/msgid/vim_use/20241214172058.101d7b39%40mydesk.domain.cxm.

Re: An std-lib for Vim9script

Igbanam Ogbuluijah said on Thu, 12 Dec 2024 09:04:14 +0000

>Hi everyone,
>
>What do we think about getting a standard library (std-lib) of sorts
>for vim9script?

In every language, I'm a big fan of *well curated, language community
supported* standard libraries. If it's well thought out, easy to use,
easy to document, and mostly bug free, I like the idea.

>Would Vim9script be looking to expand these into a formal std-lib?
>Also, if I wanted to contribute a library to Vim9script, where in the
>codebase should I be looking into?

It's *very* important that any standard library be well curated. This
means not everything goes in the standard library, just stuff that
works, works well, makes programming easier, and is relatively bug
free. Therefore I think the standard library should most likely be a
subset of the library additions.

In summary, if you make it easier for me to learn and use Vim9script,
I'm a huge fan. I might even rewrite VimOutliner in Vim9script, because
truth be told, the old Vimscript was, in my opinion, horrible.

SteveT

Steve Litt

http://444domains.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 visit https://groups.google.com/d/msgid/vim_use/20241214171945.7559e481%40mydesk.domain.cxm.

Friday, December 13, 2024

Re: An std-lib for Vim9script

That explains why I couldn't find it anywhere in the Vim repo. 

First off… thank you for creating those. I think they would be find contributions to Vimscript as a language. I know these are mainly in their alpha stages today, but if there are any discussions concerning why this should be added to Vimscript somewhere, please let me know. I'd be happy to chime in.


Igbanam


On Fri, Dec 13, 2024 at 9:54 PM Lifepillar <lifepillar@lifepillar.me> wrote:
>>     Would Vim9script be looking to expand these into a formal std-lib?

I've created the vim-devel package, which the scripts you mention are
part of, partly to become more proficient with Vim 9 script and partly
to create and collect some reusable components for my scripts. I'd like
to make it clear that at the moment that repo is a personal initiative,
and mostly experimental in nature (although I am actively using those
libraries, and I'm open to collaboration on that repo).

Let's see how much traction your proposal gets. In any case, several key
questions need to be answered, in primis: what can improve the
programming ux enough for enough people to justify putting it into
a "standard library"?

Life.

--
--
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 visit https://groups.google.com/d/msgid/vim_use/vjiadn%24jtd%241%40ciao.gmane.io.

--
--
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 visit https://groups.google.com/d/msgid/vim_use/CAOmRJrfMd7tQFf3GcQCboL0LYMQVWjYhRWsObFJQyapgOTnVhw%40mail.gmail.com.

Re: An std-lib for Vim9script

>> Would Vim9script be looking to expand these into a formal std-lib?

I've created the vim-devel package, which the scripts you mention are
part of, partly to become more proficient with Vim 9 script and partly
to create and collect some reusable components for my scripts. I'd like
to make it clear that at the moment that repo is a personal initiative,
and mostly experimental in nature (although I am actively using those
libraries, and I'm open to collaboration on that repo).

Let's see how much traction your proposal gets. In any case, several key
questions need to be answered, in primis: what can improve the
programming ux enough for enough people to justify putting it into
a "standard library"?

Life.

--
--
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 visit https://groups.google.com/d/msgid/vim_use/vjiadn%24jtd%241%40ciao.gmane.io.

Re: An std-lib for Vim9script

On Thu, 12 Dec 2024, Yegappan Lakshmanan wrote:

> Would Vim9script be looking to expand these into a formal std-lib?
> Also, if I wanted to contribute a library to Vim9script, where in
> the codebase should I be looking into?
>
> These scripts can be placed under
> the runtime/pack/dist/opt/stdlib/autoload directory and can be
> imported by plugins.

We could also use runtime/autoload/dist/vim.vim because it is already
used.

Thanks,
Christian
--
Sentient plasmoids are a gas.

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z1xhJAWArNXgj6bW%40256bit.org.

Thursday, December 12, 2024

Re: An std-lib for Vim9script

Hi,

On Thu, Dec 12, 2024 at 1:04 AM Igbanam Ogbuluijah <xigbanam@gmail.com> wrote:
Hi everyone,

What do we think about getting a standard library (std-lib) of sorts for vim9script?

While using Vim9script for Advent of Code this year — definitely not the reason vim9script was created for, but — I realized some interesting library additions like :h libreactive, :h libtinytest; there are more. I think these are fantastic.

Would Vim9script be looking to expand these into a formal std-lib? Also, if I wanted to contribute a library to Vim9script, where in the codebase should I be looking into?


These scripts can be placed under the runtime/pack/dist/opt/stdlib/autoload directory and can be imported by plugins.

Regards,
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 visit https://groups.google.com/d/msgid/vim_use/CAAW7x7nBCeuYV7%2BeP4TDysZT9QkwUdb5H%3DRUPsGih1xk7Ug4qw%40mail.gmail.com.

An std-lib for Vim9script

Hi everyone,

What do we think about getting a standard library (std-lib) of sorts for vim9script?

While using Vim9script for Advent of Code this year — definitely not the reason vim9script was created for, but — I realized some interesting library additions like :h libreactive, :h libtinytest; there are more. I think these are fantastic.

Would Vim9script be looking to expand these into a formal std-lib? Also, if I wanted to contribute a library to Vim9script, where in the codebase should I be looking into?

Thanks!


Igbanam

--
--
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 visit https://groups.google.com/d/msgid/vim_use/CAOmRJrfXXtmh4ipAnpjKLF0eoLhRTL2oU5k8RtYwnbZR_1w7Pg%40mail.gmail.com.

Wednesday, December 11, 2024

New Zealand Donations to this recipient aren't supported in this country

I have donated irregularly over the years, using Paypal IIRC.  But today, I get the above, whether I click the Paypal button or the credit card button.

Is there a way for me to donate?

--
--
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 visit https://groups.google.com/d/msgid/vim_use/2b8617a5-5cdd-488d-ab8f-c93675a0ec1en%40googlegroups.com.

Monday, December 9, 2024

Re: How to scroll the "info" popup window (documentation window)?

I don't know of a particularly easy way, but here for the LSP plug-in I worked a similar restriction by some mappings.

Le vendredi 6 décembre 2024 à 19:12:28 UTC+1, Girish a écrit :
I can get it to scroll now by obtaining window-id of popup (popup_findinfo()) and scrolling using win_execute(). Maybe there is an easier way.

On Friday, 6 December 2024 at 18:43:31 UTC+1 Girish wrote:
In insert mode completion, when an item is selected in the menu it may open an additional window to show documentation for the symbol (in LSP for example). How to scroll this window without mouse?

--
--
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 visit https://groups.google.com/d/msgid/vim_use/d0952d2a-def7-4fa7-be64-5baa0efd628en%40googlegroups.com.

Friday, December 6, 2024

Re: How to scroll the "info" popup window (documentation window)?

I can get it to scroll now by obtaining window-id of popup (popup_findinfo()) and scrolling using win_execute(). Maybe there is an easier way.

On Friday, 6 December 2024 at 18:43:31 UTC+1 Girish wrote:
In insert mode completion, when an item is selected in the menu it may open an additional window to show documentation for the symbol (in LSP for example). How to scroll this window without mouse?

--
--
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 visit https://groups.google.com/d/msgid/vim_use/a0add50b-ff82-40b8-bc3b-e606ea3c2bfcn%40googlegroups.com.

How to scroll the "info" popup window (documentation window)?

In insert mode completion, when an item is selected in the menu it may open an additional window to show documentation for the symbol (in LSP for example). How to scroll this window without mouse?

--
--
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 visit https://groups.google.com/d/msgid/vim_use/1dc09e4b-ea01-487f-b933-d1affb885fdbn%40googlegroups.com.

Tuesday, December 3, 2024

Re: Windows Vim download version on website

On Tue, 03 Dec 2024, TS wrote:

> Christian Brabandt <cblists@256bit.org> said (on 2024/12/03):
> > Scroll down a bit to https://www.vim.org/download.php#pc you should see
> > your download link there.
>
> Ah, I see it now, and the bit now added to the top. Thank you.
> I really don't want to sound demanding, but out of genuine
> curiosity, why retain the vulnerable 9.1.0000 links at all? I
> would fear most users might navigate the page like I did:
> - "popular", "Windows", "Unix", "Mac"
> okay, I'm on Windows...
> - "32-bit installer", "64-bit installer", "32-bit zip", "64-bit zip"
> okay, I'm 64-bit, so click 64-bit installer
>
> Or similarly for "okay, I'll go with what's popular,
> current-stable sounds good... not sure why there's multiple
> stable links but I'll just grab the first x64 one".

Yeah you are right. I have updated it again and only included the
v9.1.0821 versions.

Thanks,
Christian
--
There's nothing like good food, good wine, and a bad girl.

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z095hLgBNQWn7aAs%40256bit.org.

Re: Windows Vim download version on website

Christian Brabandt <cblists@256bit.org> said (on 2024/12/03):
> Scroll down a bit to https://www.vim.org/download.php#pc you should see
> your download link there.

Ah, I see it now, and the bit now added to the top. Thank you.
I really don't want to sound demanding, but out of genuine
curiosity, why retain the vulnerable 9.1.0000 links at all? I
would fear most users might navigate the page like I did:
- "popular", "Windows", "Unix", "Mac"
okay, I'm on Windows...
- "32-bit installer", "64-bit installer", "32-bit zip", "64-bit zip"
okay, I'm 64-bit, so click 64-bit installer

Or similarly for "okay, I'll go with what's popular,
current-stable sounds good... not sure why there's multiple
stable links but I'll just grab the first x64 one".

The user ends up with a vulnerable install, without realizing.
Wouldn't it make more sense to bury the vulnerable installer
links behind a "archive" or "previous releases" or let users
find them from the directory links?

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z08-BSAUdEfZmX8H%40dot.t41t.com.

Re: Windows Vim download version on website

On Tue, 03 Dec 2024, TS wrote:

> Thanks for the update. I don't see any change to the page yet;
> is there a delay? In the wiget repository I see 9.1.0821 along
> with 9.1.0818, 9.1.0718, 9.1.0618, etc. but the top of
> download.php still says:
>
> The current stable version is gvim_9.1.0000_x64.exe (64bit installer) and gvim_9.1.0000_x86.exe (32bit installer).
> A zip package (32bit and 64bit) is also available: gvim_9.1.0000_x86.zip and gvim_9.1.0000_x64.zip

Scroll down a bit to https://www.vim.org/download.php#pc you should see
your download link there.

Thanks,
Christian
--
Fifty flippant frogs
Walked by on flippered feet
And with their slime they made the time
Unnaturally fleet.

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z08j5c/0pCYCLA/u%40256bit.org.

Re: Windows Vim download version on website

> On Mon, 02 Dec 2024, TS wrote:
>> The version of Vim for Windows offered for download on
>> https://www.vim.org/download.php is 9.1.0. This has some known
>> vulnerabilities...

Christian Brabandt <cblists@256bit.org> said (on 2024/12/02):
> I have updated the links to include the latest stable release from
> the winget package repository:
> https://github.com/microsoft/winget-pkgs/tree/master/manifests/v/vim/vim/
>
> Note: there will be new stable releases at the winget repository
> approximately all 100 minor patch numbers. So expect there to be a new
> releases within the next weeks.

Thanks for the update. I don't see any change to the page yet;
is there a delay? In the wiget repository I see 9.1.0821 along
with 9.1.0818, 9.1.0718, 9.1.0618, etc. but the top of
download.php still says:

The current stable version is gvim_9.1.0000_x64.exe (64bit installer) and gvim_9.1.0000_x86.exe (32bit installer).
A zip package (32bit and 64bit) is also available: gvim_9.1.0000_x86.zip and gvim_9.1.0000_x64.zip

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z08gHsA-XfQ0N1IN%40dot.t41t.com.

Monday, December 2, 2024

Re: Windows Vim download version on website

On Mon, 02 Dec 2024, TS wrote:

> The version of Vim for Windows offered for download on
> https://www.vim.org/download.php is 9.1.0. This has some known
> vulnerabilities (like CVE-2024-45306, CVE-2024-41965, ...).
> Can the "current stable version" be updated to something not
> vulnerable? Or is there a reason the website is still
> prominently distributing a vulnerable version?
>
> I realize there are also links to nightly builds. I would
> prefer to use something "stable" though, so I'm hesitant to
> take a nightly build at random just to avoid being vulnerable.

I have updated the links to include the latest stable release from
the winget package repository:
https://github.com/microsoft/winget-pkgs/tree/master/manifests/v/vim/vim/

Note: there will be new stable releases at the winget repository
approximately all 100 minor patch numbers. So expect there to be a new
releases within the next weeks.

Thanks,
Christian
--
Dare to be naive.
-- R. Buckminster Fuller

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z04LQ6smlB%2BEmqfl%40256bit.org.

Windows Vim download version on website

The version of Vim for Windows offered for download on
https://www.vim.org/download.php is 9.1.0. This has some known
vulnerabilities (like CVE-2024-45306, CVE-2024-41965, ...).
Can the "current stable version" be updated to something not
vulnerable? Or is there a reason the website is still
prominently distributing a vulnerable version?

I realize there are also links to nightly builds. I would
prefer to use something "stable" though, so I'm hesitant to
take a nightly build at random just to avoid being vulnerable.

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z04H5HbyZbC8cTF9%40dot.t41t.com.

Re: Why change the defaults ?

Hi,

On Sun, 01 Dec 2024, Tony Mechelynck wrote:

> At the moment, there are several sets of "default" option settings in Vim :
> - "compatible" defaults (or "vi defaults") used when the -C switch
> is used on the command-line or when you have no vimrc but an exrc
> - - These are there to mimic the behaviour of legacy Vi (with the
> exception of what Bram regarded as "bugs" in the POSIX description of
> Vim). Therefore IMHO they MUST NOT be changed ;
> - "POSIX" defaults, used in addition to the "vi defaults" when
> $VIM_POSIX is set. These try to make Vim even more like legacy Vi than
> just setting 'compatible', even to the point of imitating its
> POSIX-entrenched "bugs". For the same reason as above, IMHO they MUST
> NOT be changed ;
> - "nocompatible" defaults. They are used, for example, if you have
> an empty vimrc, or if you put -N -u NONE on the command-line ;
> - "defaults.vim" settings. These are set by $VIMRUNTIME/defaults.vim
> when no vimrc is found.
> - - They are also set if you source either defaults.vim or
> vimrc_example.vim somewhere near the beginning of your vimrc, or if
> you have -u DEFAULTS on the command-line even if you have a vimrc
> (which in that case won't be sourced).
>
> I see several threads proposing to make this or that "defaults.vim"
> setting the Vim default for everybody. IMHO this is unwise, because it
> is not backward-compatible. If you want those settings even though you
> have a vimrc, source the defaults.vim or the vimrc_example.vim from
> it. If there are _other_ settings set by the defaults.vim which you
> _don't_ want, well, reverse them when Vim comes back to your vimrc
> after sourcing them. This is the time-honored backward-compatible way
> to do it and if you do it this way instead of changing everyone's
> defaults, no one will be surprised.
>
> For instance the defaults.vim contains a line which says
> filetype plugin indent on
> My preferences go to filetype detection on, filetype plugins on,
> filetype indent off. No problem : after sourcing
> $VIMRUNTIME/vimrc_example.vim (which calls the defaults.vim nowadays)
> my vimrc has a line
> filetype indent off
> and voilà.

As far as what I am concerned, I don't plan to make changes to the
defaults, except for gradually moving (non-controversial) defaults from
defaults.vim to the C code, because this seemed to be what Bram wanted
to achieve. But it still causes a bit of discussion.

Independently of this, there has been a bit of discussion on whether or
not we should handle defaults.vim a bit more consistently, such that
there is no inconsistency between:
- users not having a configuration file at all
- users creating a simple (empty) vimrc file (where suddenly Vim would
behave slightly differently)

This has been a major source of discussion/confusion/hate for people in
the past. I don't know how to improve this situation yet.

Thanks,
Christian
--
Here I am in the POSTERIOR OLFACTORY LOBULE but I don't see CARL SAGAN
anywhere!!

--
--
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 visit https://groups.google.com/d/msgid/vim_use/Z03d/1W/X1CVejeh%40256bit.org.

Sunday, December 1, 2024

Re: Why change the defaults ?

Tony Mechelynck said on Sun, 1 Dec 2024 21:04:09 +0100

>I see several threads aguing in favour of a change of Vim's defaults.
>I believe that such changes are unwise, and here is why :

I agree for an additional reason: Software should be changed only when
there's a compelling reason to change it. Anything less than compelling
is just churn.

>
>I see several threads proposing to make this or that "defaults.vim"
>setting the Vim default for everybody. IMHO this is unwise, because it
>is not backward-compatible. If you want those settings even though you
>have a vimrc, source the defaults.vim or the vimrc_example.vim from
>it. If there are _other_ settings set by the defaults.vim which you
>_don't_ want, well, reverse them when Vim comes back to your vimrc
>after sourcing them. This is the time-honored backward-compatible way
>to do it and if you do it this way instead of changing everyone's
>defaults, no one will be surprised.

The preceding paragraph is obviously the best way to satisfy everyone.
Those who are satisfied with the way things are now keep using Vim as
always. Those who want to adopt the new defaults in-toto source
defaults.vim. Those who want to make their own Vim interface source
something like my_defaults.vim.

SteveT

Steve Litt

http://444domains.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 visit https://groups.google.com/d/msgid/vim_use/20241201152258.34dd141f%40mydesk.domain.cxm.

Re: Is there a way to configure gvim to change background and foreground colors of selected text?

Steve Litt said on Sun, 1 Dec 2024 14:58:03 -0500

>Is there a way to configure gvim to change background and foreground
>colors of selected text? If so, how do I do it?

I solved this problem by placing the following line in my .gvimrc:

highlight Visual guifg=yellow guibg=black

Thanks,

SteveT

--
--
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 visit https://groups.google.com/d/msgid/vim_use/20241201150756.0689ee0f%40mydesk.domain.cxm.

Why change the defaults ?

I see several threads aguing in favour of a change of Vim's defaults.
I believe that such changes are unwise, and here is why :

At the moment, there are several sets of "default" option settings in Vim :
- "compatible" defaults (or "vi defaults") used when the -C switch
is used on the command-line or when you have no vimrc but an exrc
- - These are there to mimic the behaviour of legacy Vi (with the
exception of what Bram regarded as "bugs" in the POSIX description of
Vim). Therefore IMHO they MUST NOT be changed ;
- "POSIX" defaults, used in addition to the "vi defaults" when
$VIM_POSIX is set. These try to make Vim even more like legacy Vi than
just setting 'compatible', even to the point of imitating its
POSIX-entrenched "bugs". For the same reason as above, IMHO they MUST
NOT be changed ;
- "nocompatible" defaults. They are used, for example, if you have
an empty vimrc, or if you put -N -u NONE on the command-line ;
- "defaults.vim" settings. These are set by $VIMRUNTIME/defaults.vim
when no vimrc is found.
- - They are also set if you source either defaults.vim or
vimrc_example.vim somewhere near the beginning of your vimrc, or if
you have -u DEFAULTS on the command-line even if you have a vimrc
(which in that case won't be sourced).

I see several threads proposing to make this or that "defaults.vim"
setting the Vim default for everybody. IMHO this is unwise, because it
is not backward-compatible. If you want those settings even though you
have a vimrc, source the defaults.vim or the vimrc_example.vim from
it. If there are _other_ settings set by the defaults.vim which you
_don't_ want, well, reverse them when Vim comes back to your vimrc
after sourcing them. This is the time-honored backward-compatible way
to do it and if you do it this way instead of changing everyone's
defaults, no one will be surprised.

For instance the defaults.vim contains a line which says
filetype plugin indent on
My preferences go to filetype detection on, filetype plugins on,
filetype indent off. No problem : after sourcing
$VIMRUNTIME/vimrc_example.vim (which calls the defaults.vim nowadays)
my vimrc has a line
filetype indent off
and voilà.

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 visit https://groups.google.com/d/msgid/vim_use/CAJkCKXuTaXJT4_QNGseAPwPQZAZBbc%3D_%3DNkRjGJxp446RCXbXg%40mail.gmail.com.

Is there a way to configure gvim to change background and foreground colors of selected text?

Is there a way to configure gvim to change background and foreground
colors of selected text? If so, how do I do it?

Thanks,

SteveT

Steve Litt
http://444domains.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 visit https://groups.google.com/d/msgid/vim_use/20241201145803.4b5e2ad3%40mydesk.domain.cxm.