Re: Spam Script submissions on vim.org

On Di, 17 Sep 2024, 'Paul' via vim_use wrote:

> FYI there is now only one item in the feed and it is this:
>
> ❗️❗️This feed has exceeded usage limit❗️❗️
>
> The available feed limit is 0.
> The ranking of this feed is 1.
>
> Please update your subscription plan at:
> https://rsseverything.com/subscription
>
> Or manager your feeds in dashboard:
> https://rsseverything.com/dashboard

Ah, it appears we only had 7 free days for testing :/

I guess I have to pay for the service, it's just unclear how many
credits I need. Strange UI with no contact possibilities.

Thanks,
Christian
--
I'd rather be led to hell than managed to heaven.

--
--
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/ZuqOV70Nja2qfYYp%40256bit.org.

Re: Spam Script submissions on vim.org

FYI there is now only one item in the feed and it is this:

❗️❗️This feed has exceeded usage limit❗️❗️

The available feed limit is 0.
The ranking of this feed is 1.

Please update your subscription plan at:
https://rsseverything.com/subscription

Or manager your feeds in dashboard:
https://rsseverything.com/dashboard

-- Delivered by RssEverything service

--
--
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/ZunfYhlwnG3GSjr6%40kitt.default.meeow.uk0.bigv.io.

Re: unable to set "tags" file in front of "tags" option

thanks...

Enan Ajmain schrieb am Samstag, 14. September 2024 um 17:28:25 UTC+2:

On Sat, 14 Sep 2024 02:33:55 -0700 (PDT)
Andreas Otto <aotto1...@gmail.com> wrote:
> Hi, I build my *tags* options like:
>
> source $NHI1_HOME/example/.vimrc
> set tags+=$NHI1_HOME/theKernel/jv/tags
> set tags+=$NHI1_HOME/theLink/jv/tags
> set tags+=$NHI1_HOME/theConfig/jv/tags
> set tags+=$NHI1_HOME/theSq3Lite/jv/tags
>
> with the most specific *tags* files at the end (+=). my problem is that I
> want the most specific *tags* file in the FRONT of the *tags* option.
>
> I'm a little embarrassed to ask such a simple question, but since Vim has
> decided to use a somewhat "unusual" custom development as a "programming
> language", I unfortunately have no choice but to go down this route.
>
> Normally I would assume that something like:
> > set tags=/my/file/to/tags,$tags
> would work, but it just doesn't.
>

Try "^=" to prepend instead of "+=" which appends. From the helpdocs:

:se[t] {option}+={value} *:set+=*
Add the {value} to a number option, or append the
{value} to a string option. When the option is a
comma-separated list, a comma is added, unless the
value was empty.
If the option is a list of flags, superfluous flags
are removed. When adding a flag that was already
present the option value doesn't change.
Also see |:set-args| above.

:se[t] {option}^={value} *:set^=*
Multiply the {value} to a number option, or prepend
the {value} to a string option. When the option is a
comma-separated list, a comma is added, unless the
value was empty.
Also see |:set-args| above.


--
Enan

--
--
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/5c46ae1d-fb3a-4d49-a42e-15abce2a4547n%40googlegroups.com.

Re: unable to set "tags" file in front of "tags" option

On Sat, 14 Sep 2024 02:33:55 -0700 (PDT)
Andreas Otto <aotto1968zwei@gmail.com> wrote:
> Hi, I build my *tags* options like:
>
> source $NHI1_HOME/example/.vimrc
> set tags+=$NHI1_HOME/theKernel/jv/tags
> set tags+=$NHI1_HOME/theLink/jv/tags
> set tags+=$NHI1_HOME/theConfig/jv/tags
> set tags+=$NHI1_HOME/theSq3Lite/jv/tags
>
> with the most specific *tags* files at the end (+=). my problem is that I
> want the most specific *tags* file in the FRONT of the *tags* option.
>
> I'm a little embarrassed to ask such a simple question, but since Vim has
> decided to use a somewhat "unusual" custom development as a "programming
> language", I unfortunately have no choice but to go down this route.
>
> Normally I would assume that something like:
> > set tags=/my/file/to/tags,$tags
> would work, but it just doesn't.
>

Try "^=" to prepend instead of "+=" which appends. From the helpdocs:

:se[t] {option}+={value} *:set+=*
Add the {value} to a number option, or append the
{value} to a string option. When the option is a
comma-separated list, a comma is added, unless the
value was empty.
If the option is a list of flags, superfluous flags
are removed. When adding a flag that was already
present the option value doesn't change.
Also see |:set-args| above.

:se[t] {option}^={value} *:set^=*
Multiply the {value} to a number option, or prepend
the {value} to a string option. When the option is a
comma-separated list, a comma is added, unless the
value was empty.
Also see |:set-args| above.


--
Enan

--
--
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/20240914112814.00004584%40gmail.com.

unable to set "tags" file in front of "tags" option

Hi, I build my tags options like:

source $NHI1_HOME/example/.vimrc
set tags+=$NHI1_HOME/theKernel/jv/tags
set tags+=$NHI1_HOME/theLink/jv/tags
set tags+=$NHI1_HOME/theConfig/jv/tags
set tags+=$NHI1_HOME/theSq3Lite/jv/tags

with the most specific tags files at the end (+=). my problem is that I want the most specific tags file in the FRONT of the tags option.

I'm a little embarrassed to ask such a simple question, but since Vim has decided to use a somewhat "unusual" custom development as a "programming language", I unfortunately have no choice but to go down this route.

Normally I would assume that something like:
> set tags=/my/file/to/tags,$tags
would work, but it just doesn't.

--
--
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/1d9c6cb3-da00-461c-a1fe-bc08de597ed6n%40googlegroups.com.

Re: Spam Script submissions on vim.org

On Tue, Sep 10, 2024 at 06:47:48PM +0200, Christian Brabandt wrote:
>> On Tue, Sep 10, 2024 at 05:59:08PM +0200, Christian Brabandt wrote:
>> > > I used to report these sometimes but the RSS feed at https://feed43.com/vim-scripts.xml stopped working a while ago…
>> >
>> > Where did you see this feed? I have now created:
>> > https://rsseverything.com/feed/bf4677cd-f853-449a-95d7-ca7bce8f8b0d.xml
>> > But don't know where to change it on the website.
>>
>> Thanks. The HTML source has a link rel="alternate" that links to feed43.com.
>
>Ah, okay. Try now.

It works :)

--
--
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/ZuB7c6ZUujOB7UiQ%40kitt.default.meeow.uk0.bigv.io.

Re: Spam Script submissions on vim.org

On Di, 10 Sep 2024, 'Paul' via vim_use wrote:

> On Tue, Sep 10, 2024 at 05:59:08PM +0200, Christian Brabandt wrote:
> > > I used to report these sometimes but the RSS feed at https://feed43.com/vim-scripts.xml stopped working a while ago…
> >
> > Where did you see this feed? I have now created:
> > https://rsseverything.com/feed/bf4677cd-f853-449a-95d7-ca7bce8f8b0d.xml
> > But don't know where to change it on the website.
>
> Thanks. The HTML source has a link rel="alternate" that links to feed43.com.

Ah, okay. Try now.

Thanks,
Christian
--
H. L. Mencken suffers from the hallucination that he is H. L. Mencken --
there is no cure for a disease of that magnitude.
-- Maxwell Bodenheim

--
--
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/ZuB4NOpF3Wot1REq%40256bit.org.

Re: Spam Script submissions on vim.org

On Tue, Sep 10, 2024 at 05:59:08PM +0200, Christian Brabandt wrote:
>> I used to report these sometimes but the RSS feed at https://feed43.com/vim-scripts.xml stopped working a while ago…
>
>Where did you see this feed? I have now created:
>https://rsseverything.com/feed/bf4677cd-f853-449a-95d7-ca7bce8f8b0d.xml
>But don't know where to change it on the website.

Thanks. The HTML source has a link rel="alternate" that links to feed43.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/ZuB2VozaOJnEKKo9%40kitt.default.meeow.uk0.bigv.io.

Re: Spam Script submissions on vim.org

On Mi, 04 Sep 2024, 'Paul' via vim_use wrote:

> I used to report these sometimes but the RSS feed at https://feed43.com/vim-scripts.xml stopped working a while ago…

Where did you see this feed? I have now created:
https://rsseverything.com/feed/bf4677cd-f853-449a-95d7-ca7bce8f8b0d.xml
But don't know where to change it on the website.

Thanks,
Christian
--
I love children. Especially when they cry -- for then someone takes them away.
-- Nancy Mitford

--
--
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/ZuBszN6VMxRR4HH3%40256bit.org.

Re: Spam Script submissions on vim.org

Hi,
please don't share pictures, just the script-ids + user_ids.

I think I have now deleted all of those.

Thanks,
Chris

On Di, 10 Sep 2024, rwmit...@gmail.com wrote:

> More spam.  The help for students isn't using Vim in any obvious way:
>
> spam.png
>
> Here is the start on the main page:
>
> spam.png
> On Thursday, September 5, 2024 at 2:34:25 AM UTC-4 Christian Brabandt wrote:
>
>
> On Mi, 04 Sep 2024, 'Paul' via vim_use wrote:
>
> > I used to report these sometimes but the RSS feed at
> > https://feed43.com/vim-scripts.xml stopped working a while ago…
>
> I am not sure what happened there. I'll have a look at the RSS feed, but
> don't know when I come to it.
>
> Thanks,
> Christian




Mit freundlichen Grüßen
Christian
--
The girl who swears no one has ever made love to her has a right to swear.
-- Sophia Loren

--
--
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/ZuBnHABMG2ajgm9T%40256bit.org.

Re: Spam Script submissions on vim.org

More spam.  The help for students isn't using Vim in any obvious way:

Here is the start on the main page:

On Thursday, September 5, 2024 at 2:34:25 AM UTC-4 Christian Brabandt wrote:

On Mi, 04 Sep 2024, 'Paul' via vim_use wrote:

> I used to report these sometimes but the RSS feed at
> https://feed43.com/vim-scripts.xml stopped working a while ago…

I am not sure what happened there. I'll have a look at the RSS feed, but
don't know when I come to it.

Thanks,
Christian
--
Education is the process of casting false pearls before real swine.
-- Irwin Edman

--
--
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/f1bb8914-50eb-4f8f-8ee4-1248ba6e914dn%40googlegroups.com.

Re: Using mapping

On Tue, 3 Sep 2024 19:45:18 +0300
M <matthewtarasov@gmail.com> wrote:
> Christian Brabandt <cblists@256bit.org>:
>
> >
> > On Di, 03 Sep 2024, Enan Ajmain wrote:
> >
> > > Hi everyone,
> > >
> > > ":h using-<Plug>" explains the usecase of <Plug> in quite an obscure
> > > manner. Using examples from perspectives of plugin authors _and_ plugin
> > > users would be more helpful. It should specially inform the user that
> > > any mapping using the "<Plug>" keyword should be a recursive mapping.
> > >
> > > I think the doc should be updated. Maybe we can follow this vi.SO
> > > answer: https://vi.stackexchange.com/a/31013.
> >
> > Can you think of a concrete doc patch please?
>
> Actually, it's not written like this, because it's not like this. In a
> sense that any occurence of <plug>thing is always treated as recursive.
> So users (finally ;-) don't have to remember about it. I can't say when it
> was done exactly but more than a few months at least.

You're right. In both my Windows and Linux machines, I use the
(almost-) latest vim built from source. Recently I added a
non-recursive "<Plug>" mapping in my vimrc and it worked fine. But then
I saw that it didn't work in my WSL vim. Now I realize the version of
vim in WSL is 8.2. I guess there isn't any further need for the doc to
be updated. But if I do draft a doc patch, I'll open a PR.

--
Enan

> Yet if you believe that the docs should be improved, as Christian
> suggested, you can submit your patch.
> If registered on github then you can also create a pull request at
> https://github.com/vim/vim/pulls
> Both source code and documentation improvements are always welcome.
>
> Kind regards,
> Matvey
>

--
--
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/20240905024842.000015a7%40gmail.com.

Re: Spam Script submissions on vim.org

On Mi, 04 Sep 2024, 'Paul' via vim_use wrote:

> I used to report these sometimes but the RSS feed at
> https://feed43.com/vim-scripts.xml stopped working a while ago…

I am not sure what happened there. I'll have a look at the RSS feed, but
don't know when I come to it.

Thanks,
Christian
--
Education is the process of casting false pearls before real swine.
-- Irwin Edman

--
--
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/ZtlQ5GvQiZY4m8ji%40256bit.org.

Re: Spam Script submissions on vim.org

On Thu, Aug 29, 2024 at 05:23:18PM +0200, Christian Brabandt wrote:
>On Do, 29 Aug 2024, rwmit...@gmail.com wrote:
>
>> There are currently two obvious spam scripts submitted to vim.org.  Who has the ability to remove them and require pre-approval for first time submitters?
>
>Please share the links (script id and userid) and I'll take care. I have
>just today deleted an obvious spammer and his script. You can always
>contact me off-list and I'll take care of it.

I used to report these sometimes but the RSS feed at https://feed43.com/vim-scripts.xml stopped working a while ago…

--
--
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/ZtgjlPg4z-LfhHtd%40kitt.default.meeow.uk0.bigv.io.

Re: Using mapping

вт, 3 сент. 2024 г. в 18:48, Christian Brabandt <cblists@256bit.org>:

On Di, 03 Sep 2024, Enan Ajmain wrote:

> Hi everyone,
>
> ":h using-<Plug>" explains the usecase of <Plug> in quite an obscure
> manner.  Using examples from perspectives of plugin authors _and_ plugin
> users would be more helpful.  It should specially inform the user that
> any mapping using the "<Plug>" keyword should be a recursive mapping.
>
> I think the doc should be updated.  Maybe we can follow this vi.SO
> answer: https://vi.stackexchange.com/a/31013.

Can you think of a concrete doc patch please?

Thanks,
Christian
--
So many men, so many opinions; every one his own way.
                -- Publius Terentius Afer (Terence)

--
--
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/ZtcvulbSY8BEIuKw%40256bit.org.

 

Hello,

Actually, it's not written like this,  because it's not like this. In a sense that any occurence of <plug>thing is always treated as recursive.

So users (finally ;-) don't have to remember about it. I can't say when it was done exactly but more than a few months at least.

Yet if you believe that the docs should be improved, as Christian suggested, you can submit your patch.

If registered on github then you can also create a pull request at https://github.com/vim/vim/pulls

Both source code and documentation improvements are always welcome.

Kind regards,

Matvey

--
--
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/CAFsTB%2BLmZ5Q5Dmvq7Jg%3DJmk%2BD_CjUbEaBVcyjiKc%2BD7sPoWQ7Q%40mail.gmail.com.

Re: Using mapping

On Di, 03 Sep 2024, Enan Ajmain wrote:

> Hi everyone,
>
> ":h using-<Plug>" explains the usecase of <Plug> in quite an obscure
> manner. Using examples from perspectives of plugin authors _and_ plugin
> users would be more helpful. It should specially inform the user that
> any mapping using the "<Plug>" keyword should be a recursive mapping.
>
> I think the doc should be updated. Maybe we can follow this vi.SO
> answer: https://vi.stackexchange.com/a/31013.

Can you think of a concrete doc patch please?

Thanks,
Christian
--
So many men, so many opinions; every one his own way.
-- Publius Terentius Afer (Terence)

--
--
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/ZtcvulbSY8BEIuKw%40256bit.org.

Using mapping

Hi everyone,

":h using-<Plug>" explains the usecase of <Plug> in quite an obscure
manner. Using examples from perspectives of plugin authors _and_ plugin
users would be more helpful. It should specially inform the user that
any mapping using the "<Plug>" keyword should be a recursive mapping.

I think the doc should be updated. Maybe we can follow this vi.SO
answer: https://vi.stackexchange.com/a/31013.

--
Enan

--
--
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/20240903021804.00004af7%40gmail.com.

Re: Spam Script submissions on vim.org

On Do, 29 Aug 2024, rwmit...@gmail.com wrote:

> https://www.vim.org/scripts/script.php?script_id=6122   Assignment Help, no
> obvious connection to Vim
> https://www.vim.org/scripts/script.php?script_id=6121 VIM CHORE - doesn't tell
> anything about what it does

Say goodbye ;)

Let me know if you notice any more.


Thanks,
Christian
--
Even if you aren't in doubt, consider the mental welfare of the person who
has to maintain the code after you, and who will probably put parens in
the wrong place. -- Larry Wall in the perl man page

--
--
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/ZtC8kfP38kt/STfK%40256bit.org.

Re: Spam Script submissions on vim.org

https://www.vim.org/scripts/script.php?script_id=6122   Assignment Help, no obvious connection to Vim

https://www.vim.org/scripts/script.php?script_id=6121 VIM CHORE - doesn't tell anything about what it does

On Thursday, August 29, 2024 at 11:23:31 AM UTC-4 Christian Brabandt wrote:

On Do, 29 Aug 2024, rwmit...@gmail.com wrote:

> There are currently two obvious spam scripts submitted to vim.org.  Who has the ability to remove them and require pre-approval for first time submitters?

Please share the links (script id and userid) and I'll take care. I have
just today deleted an obvious spammer and his script. You can always
contact me off-list and I'll take care of it.


Thanks,
Chris
--
When the blind lead the blind they will both fall over the cliff.
-- Chinese proverb

--
--
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/821a9d1e-7bee-4f6c-aba6-ee64e07ecf6dn%40googlegroups.com.

Re: Spam Script submissions on vim.org

On Do, 29 Aug 2024, rwmit...@gmail.com wrote:

> There are currently two obvious spam scripts submitted to vim.org.  Who has the ability to remove them and require pre-approval for first time submitters?

Please share the links (script id and userid) and I'll take care. I have
just today deleted an obvious spammer and his script. You can always
contact me off-list and I'll take care of it.


Thanks,
Chris
--
When the blind lead the blind they will both fall over the cliff.
-- Chinese proverb

--
--
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/ZtCSZrep82zoAbKl%40256bit.org.

Spam Script submissions on vim.org

There are currently two obvious spam scripts submitted to vim.org.  Who has the ability to remove them and require pre-approval for first time submitters?

--
--
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/9b55afad-3af3-4a86-b7b7-82e2892121bdn%40googlegroups.com.

Re: Annoying Vim Problem

I am saving the file before leaving.

This does not happen all the time, but sometimes it happens.

On Sat, Aug 24, 2024 at 4:38 PM Igbanam Ogbuluijah <xigbanam@gmail.com> wrote:

Ensure you're saving the file to disk on BufLeave. Or try :w before you switch buffers.

Igbanam

On Sat, Aug 24, 2024 at 2:22 PM Riza Dindir <riza.dindir@gmail.com> wrote:

Hello

When I switch from one buffer to the other, the buffer that I have switched to is changed so that a previous edit is being replayed. To explain a bit more.

I have a file a.txt and edited that file (changing first 2 characters characters in line 2 to uppercase)

file: a.txt

line 1

LIne 2

I switch to some other buffer (or close the editor and open it again) , do some editing and come back to buffer a.txt. When I do that the first 2 characters on line 2 are lowercase.

This has been bothering me for a while now. Has anybody seen this kind of behavior before? Does this have something to do with the .viminfo file maybe.

Regards

--
--
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/f9e5e0fb-a9d0-43d3-994f-a445fc28904cn%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/CAOmRJrdNiUOzMrWAWv16OL9NxZxWdm7be4b4bLaEg9BPf5M0-g%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/CA%2Bek4BFMCttzsTUcAaNKNysdZYuu_KmSGQ1eCa2dH9uLd%3Dx0WQ%40mail.gmail.com.

Re: Annoying Vim Problem

On Sat, Aug 24, 2024 at 3:22 PM Riza Dindir <riza.dindir@gmail.com> wrote:
>
> Hello
>
> When I switch from one buffer to the other, the buffer that I have switched to is changed so that a previous edit is being replayed. To explain a bit more.
>
> I have a file a.txt and edited that file (changing first 2 characters characters in line 2 to uppercase)
>
> file: a.txt
>
> line 1
> LIne 2
>
> I switch to some other buffer (or close the editor and open it again) , do some editing and come back to buffer a.txt. When I do that the first 2 characters on line 2 are lowercase.
>
> This has been bothering me for a while now. Has anybody seen this kind of behavior before? Does this have something to do with the .viminfo file maybe.
>
> Regards

I think it has to do with how you leave a.txt. If either you haven't
set 'autowrite' or 'autowriteall', or you quit it with an exclamation
mark (:q! to quit Vim or :e! b.txt to edit b.txt in the window where
you had edited a.txt) then any changes in a.txt are lost. If you quit
a.txt without an exclamation mark, then Vim may save the contents
depending on the settings of 'autowrite' and 'autowriteall', or else
it will refuse to leave a.txt with a mesage telling you that you want
to abandon the changes (i.e. lose them) you can repeat the command
with an exclamation mark; but beware that if you do, any unsaved
changes in a.txt will be lost.

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/CAJkCKXv3ruY0PjhAaVag9TrryLtfEotp%2BENB3PRQ%3Do5UcqJEiQ%40mail.gmail.com.

Re: Annoying Vim Problem

Ensure you're saving the file to disk on BufLeave. Or try :w before you switch buffers.

Igbanam

On Sat, Aug 24, 2024 at 2:22 PM Riza Dindir <riza.dindir@gmail.com> wrote:

Hello

When I switch from one buffer to the other, the buffer that I have switched to is changed so that a previous edit is being replayed. To explain a bit more.

I have a file a.txt and edited that file (changing first 2 characters characters in line 2 to uppercase)

file: a.txt

line 1

LIne 2

I switch to some other buffer (or close the editor and open it again) , do some editing and come back to buffer a.txt. When I do that the first 2 characters on line 2 are lowercase.

This has been bothering me for a while now. Has anybody seen this kind of behavior before? Does this have something to do with the .viminfo file maybe.

Regards

--
--
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/f9e5e0fb-a9d0-43d3-994f-a445fc28904cn%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/CAOmRJrdNiUOzMrWAWv16OL9NxZxWdm7be4b4bLaEg9BPf5M0-g%40mail.gmail.com.

Annoying Vim Problem

Hello

When I switch from one buffer to the other, the buffer that I have switched to is changed so that a previous edit is being replayed. To explain a bit more.

I have a file a.txt and edited that file (changing first 2 characters characters in line 2 to uppercase)

file: a.txt

line 1

LIne 2

I switch to some other buffer (or close the editor and open it again) , do some editing and come back to buffer a.txt. When I do that the first 2 characters on line 2 are lowercase.

This has been bothering me for a while now. Has anybody seen this kind of behavior before? Does this have something to do with the .viminfo file maybe.

Regards

--
--
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/f9e5e0fb-a9d0-43d3-994f-a445fc28904cn%40googlegroups.com.

Annoying vim problem

Hello

When I switch from one buffer to the other, the buffer that I have switched to is changed so that a previous edit is being replayed. To explain a bit more.

I have a file a.txt and edited that file (changing first 2 characters characters in line 2 to uppercase)

file: a.txt

line 1

LIne 2

I switch to some other buffer (or close the editor and open it again) , do some editing and come back to buffer a.txt. When I do that the first 2 characters on line 2 are lowercase.

This has been bothering me for a while now. Has anybody seen this kind of behavior before? Does this have something to do with the .viminfo file maybe.

Regards

--
--
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/CA%2Bek4BEUBqt6HvV-weePLS0L3sHnkYzt0VbT8eeb40xakSQEyw%40mail.gmail.com.

Re: How to get matchit to work with heredocs in Perl files

Good morning,

you could try adding

" /usr/local/share/vim/vim91/ftplugin/html.vim (lines 33-43)
" HTML: thanks to Johannes Zellner and Benji Fisher.
if exists("loaded_matchit") && !exists("b:match_words")
  let b:match_ignorecase = 1
  let b:match_words = '<!--:-->,' ..
\       '<:>,' ..
\       '<\@<=[ou]l\>[^>]*\%(>\|$\):<\@<=li\>:<\@<=/[ou]l>,' ..
\       '<\@<=dl\>[^>]*\%(>\|$\):<\@<=d[td]\>:<\@<=/dl>,' ..
\       '<\@<=\([^/!][^ \t>]*\)[^>]*\%(>\|$\):<\@<=/\1>'
  let b:html_set_match_words = 1
  let b:undo_ftplugin ..= " | unlet! b:match_ignorecase b:match_words b:html_set_match_words"
endif

to your ~/.vim/ftplugin/perl.vim file (respectively %USERPROFILE%\vimfiles instead of ~/.vim on 

Microsoft Windows).

   Enno

Le samedi 10 août 2024 à 00:21:22 UTC+2, DwigtArmyOfChampions a écrit :

I have matchit loaded and I create a PHP file hello.php that contains the following text:

<?php

$html = <<<"HTML"
<table>
  <tr>
    <td>I AM THE TABLE.</td>
  </tr>
</table>
HTML;

print "$html\n";

exit();

If I put my cursor on the HTMLtags in the heredoc if I hit the percent key(%) I can toggle between the opening and closing tags for table, tr, and td. Cool!

So, if I create a Perl file hello.pl that contains the following text:

#!/usr/bin/perl

use strict;
use warnings;

print "Hello world!\n";

my $html = <<"HTML";
<table>
  <tr>
    <td>I AM THE TABLE.</td>
  </tr>
</table>
HTML

exit();

If I try to toggle the HTML tags similar to what I did in the PHP file, it does NOT work. How do I get the heredo toggling to work with Perl files?

--
--
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/cef2f237-8f3f-40ad-9a87-190655e0d303n%40googlegroups.com.

How to get matchit to work with heredocs in Perl files

I have matchit loaded and I create a PHP file hello.php that contains the following text:

<?php

$html = <<<"HTML"
<table>
  <tr>
    <td>I AM THE TABLE.</td>
  </tr>
</table>
HTML;

print "$html\n";

exit();

If I put my cursor on the HTMLtags in the heredoc if I hit the percent key(%) I can toggle between the opening and closing tags for table, tr, and td. Cool!

So, if I create a Perl file hello.pl that contains the following text:

#!/usr/bin/perl

use strict;
use warnings;

print "Hello world!\n";

my $html = <<"HTML";
<table>
  <tr>
    <td>I AM THE TABLE.</td>
  </tr>
</table>
HTML

exit();

If I try to toggle the HTML tags similar to what I did in the PHP file, it does NOT work. How do I get the heredo toggling to work with Perl files?

--
--
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/e255684a-b7d5-419d-a9fe-576f8d4cf94en%40googlegroups.com.

Re: Change in completion behaviour?

On Di, 30 Jul 2024, Salman Halim wrote:

> Do you still need to know the patch that introduced it in the first
> place or are we past that now?

We are past that. (For the curious, it was patch v9.1.0598)

Thanks,
Christian
--
Do you know the difference between education and experience? Education
is what you get when you read the fine print; experience is what you get
when you don't.
-- Pete Seeger

--
--
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/ZqjoxOq14WzdtSTE%40256bit.org.

Re: Change in completion behaviour?

On Tue, Jul 30, 2024 at 2:21 AM Christian Brabandt <cblists@256bit.org> wrote:

Hi Salman,

I don't see what would be the benefit of having individual patches on
individual benefits. It's true, we only use a linear history with a
single branch master. You can easily checkout individual patches using
tags, e.g. git checkout v9.1.0591 Then you can use git bisect with those
tags, e.g. git checkout master && git bisect bad && git checkout
v9.1.0500 && git bisect good and then follow gits advise to checkout
individual commits, build vim and verify the good or bad behaviour.

I read what I had written a second time and you're right, I said 'branch' when I meant to say 'tag'.

 

The issue was also recently reported at
https://github.com/vim/vim/issues/15370 and fixed by
https://github.com/vim/vim/releases/tag/v9.1.0634

Do you still need to know the patch that introduced it in the first place or are we past that now?

Thank you,

Salman

--
--
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/CANuxnEfe9Fox%3D_c4ECUKYjnYfO%3DtbgNU8z5V144zdKQ3%3Dr6doA%40mail.gmail.com.

Re: Change in completion behaviour?

Hi Salman,

On Mo, 29 Jul 2024, Salman Halim wrote:

> On Mon, Jul 29, 2024 at 8:54 PM Salman Halim <salmanhalim@gmail.com>
> wrote:
> Sorry for the delayed response; I was hoping that the patches were
> in individual branches in git so I could just use 'git bisect' to
> figure out which patch introduced it. From what I can see,
> however, there is only the master branch ('git branch -a').
>
> Would you be able to please tell me how I might go back to a
> previous patch version? I'm willing to do a manual binary search.

I don't see what would be the benefit of having individual patches on
individual benefits. It's true, we only use a linear history with a
single branch master. You can easily checkout individual patches using
tags, e.g. git checkout v9.1.0591 Then you can use git bisect with those
tags, e.g. git checkout master && git bisect bad && git checkout
v9.1.0500 && git bisect good and then follow gits advise to checkout
individual commits, build vim and verify the good or bad behaviour.

> I just grabbed Vim 9.1 patch 643 and it seems to be working again.
> Somewhere between patch 608 and 643, it got addressed, possibly as a
> side effect, possibly because you figured it out. Either way, it's
> working now.

The issue was also recently reported at
https://github.com/vim/vim/issues/15370 and fixed by
https://github.com/vim/vim/releases/tag/v9.1.0634

Thanks,
Christian
--
NEVER swerve to hit a lawyer riding a bicycle -- it might be your bicycle.

--
--
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/ZqiGei/YFmXZDSBo%40256bit.org.

Re: Change in completion behaviour?

On Mon, Jul 29, 2024 at 8:54 PM Salman Halim <salmanhalim@gmail.com> wrote:

> Note that 'sal<c-n>' does work. It's ctrl-P that doesn't.

I don't remember changing this intentionally. Can you pinpoint which
patch changed that behaviour?

Thanks,
Christian

Sorry for the delayed response; I was hoping that the patches were in individual branches in git so I could just use 'git bisect' to figure out which patch introduced it. From what I can see, however, there is only the master branch ('git branch -a').

Would you be able to please tell me how I might go back to a previous patch version? I'm willing to do a manual binary search.

Thank you,

Salman

I just grabbed Vim 9.1 patch 643 and it seems to be working again. Somewhere between patch 608 and 643, it got addressed, possibly as a side effect, possibly because you figured it out. Either way, it's working now.

Thanks very much!

Salman

--
--
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/CANuxnEfAh%2B0VEb%3DT-yNemWHfnkcLJwYb9LatBeVjUi4UpFOqQg%40mail.gmail.com.

Re: Change in completion behaviour?

> Note that 'sal<c-n>' does work. It's ctrl-P that doesn't.

I don't remember changing this intentionally. Can you pinpoint which
patch changed that behaviour?

Thanks,
Christian

Sorry for the delayed response; I was hoping that the patches were in individual branches in git so I could just use 'git bisect' to figure out which patch introduced it. From what I can see, however, there is only the master branch ('git branch -a').

Would you be able to please tell me how I might go back to a previous patch version? I'm willing to do a manual binary search.

Thank you,

Salman

--
--
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/CANuxnEfDD-Hg%2BiB7L_f%3DGZSpgDJ5GVDWhZkBtFnsXZ1fDV8drw%40mail.gmail.com.

Re: Change in completion behaviour?

On Do, 25 Jul 2024, Salman Halim wrote:

> Hello,
>
> I upgraded my GVim (on Windows) from a patch in the 400's to 608 recently and noticed that my completion behaviour has changed: simply hitting <c-p> after typing the beginning of a word that is used in another window used to find it, but
> doesn't any more.
>
> I do not have a mapping for Ctrl-P.
>
> My 'complete' option is (and has been):
>
>
> let &complete=".,w,b,kspell"
>
>
> Is anybody else seeing this change?
>
> A specific example:
>
>
> I have an open window in which I have the text 'SalmanHalim'. I go into another window (different file) and type 'sal<c-p>'. 
>
>
> Note that 'sal<c-n>' does work. It's ctrl-P that doesn't.

I don't remember changing this intentionally. Can you pinpoint which
patch changed that behaviour?

Thanks,
Christian
--
We lie loudest when we lie to ourselves.
-- Eric Hoffer

--
--
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/ZqKyHlI/hrdHZNLG%40256bit.org.

Change in completion behaviour?

Hello,

I upgraded my GVim (on Windows) from a patch in the 400's to 608 recently and noticed that my completion behaviour has changed: simply hitting <c-p> after typing the beginning of a word that is used in another window used to find it, but doesn't any more.

I do not have a mapping for Ctrl-P.

My 'complete' option is (and has been):

let &complete=".,w,b,kspell"

Is anybody else seeing this change?

A specific example:

I have an open window in which I have the text 'SalmanHalim'. I go into another window (different file) and type 'sal<c-p>'. 

Note that 'sal<c-n>' does work. It's ctrl-P that doesn't.

Thank you very much.

--

 
Salman

I, too, shall something make and glory in the making.

--
--
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/CANuxnEdQdNDucb2aeFHHM8JjJ%3DGQTPa_gjTvFeRaNJVyq%3DwZYA%40mail.gmail.com.

Re: Assistance Needed for Upgrading Vim 7.4 to the Latest Version

On Di, 16 Jul 2024, Srivatsan Ramesh wrote:

> Hello Vim Support Team,

We are not a professional support team here. We help people seeking
advise, but there will be no guaranteed working solution for your use
case (or even a guaranteed answer).

> We are currently using Vim version 7.4 on our RHEL6 systems and would
> like to upgrade to the latest available version. Could you please
> provide us with detailed instructions on how to perform this upgrade?
>
> Specifically, we would like guidance on the following:
>
> Pre-requisites: Are there any specific pre-requisites or dependencies
> that need to be installed before upgrading?
>
> Backup: What are the recommended steps to backup our current settings
> and configurations before performing the upgrade?
>
> Upgrade Process: A step-by-step guide on how to upgrade from Vim 7.4
> to the latest version, including any necessary commands or scripts.
>
> Post-Upgrade Configuration: Any additional configurations or settings
> adjustments that may be needed after the upgrade to ensure everything
> functions correctly.
>
> Your assistance in this matter would be greatly appreciated, we want
> to ensure a smooth transition to the latest version.
>
> Thank you for your time and support.

I don't think we can give you detailed answers to those very specific
questions on your environment. But I will give you some general advises:

I would suggest you migrate to a newer operating system, since RHEL6 is
EOL. Chances are good, it comes with a newer version of Vim.

If you want to migrate to the lastest version, I'd recommend to compile
your own version, since the latest version changes every day by a few
minor release numbers. At the time of writing we are at 9.1.0593 but I
am sure tomorrow by this time we may be closer to the 9.1.600 release.

You shouldn't need to worry about incompatible changes, chances are that
your configuration files will still work, although it is a big step from
7.4 to 9.1

If you want to see what changed since version 7.4, I recommend to read
the following help sections from an updated Vim:

:h version-8
:h version-8.1
:h version-8.2
:h version-9.0
:h version-9.1

There are a log of new features along with very many bug fixes and
security updates as well as many runtime file updates.

You can also try out the latest version using the appimage we provide,
see https://github.com/vim/vim-appimage/releases
Those are basically self-contained Vim executables that should run on
any recent system. However in your case, I fear that those won't run on
such an old system (because the underlying base system is just too old).

If you run into specific problems, please let us know and we may be help
a bit better.

Thanks,
Christian
--
In this world some people are going to like me and some are not. So, I may
as well be me. Then I know if someone likes me, they like me.

--
--
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/ZpbTby4Hhl5P37wF%40256bit.org.

Assistance Needed for Upgrading Vim 7.4 to the Latest Version

Hello Vim Support Team,

We are currently using Vim version 7.4 on our RHEL6 systems and would like to upgrade to the latest available version. Could you please provide us with detailed instructions on how to perform this upgrade?

Specifically, we would like guidance on the following:

Pre-requisites: Are there any specific pre-requisites or dependencies that need to be installed before upgrading?

Backup: What are the recommended steps to backup our current settings and configurations before performing the upgrade?

Upgrade Process: A step-by-step guide on how to upgrade from Vim 7.4 to the latest version, including any necessary commands or scripts.

Post-Upgrade Configuration: Any additional configurations or settings adjustments that may be needed after the upgrade to ensure everything functions correctly.

Your assistance in this matter would be greatly appreciated, we want to ensure a smooth transition to the latest version.

Thank you for your time and support.

Regards,

Srivatsan R

--
--
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/c0415e03-ecd5-44c4-9799-02297e491018n%40googlegroups.com.

Re: Configuration file does not support #

On 2024-06-27, 李坏之 <ogouo168@gmail.com> wrote:
> Why does an error occur when changing the comment of the vim9.1
> configuration file to #? 9.1 does not support #

Not sure I understand your question, but before `vim9script` you should
use the legacy comment symbol " (double quote). For example:

" vim: set sw=2 ts=2 sts=0 et fdm=marker :nospell:
" Here, legacy comments must be used
" In general, before `vim9script`, legacy syntax is assumed

if !has('vim9script')
" Still legacy Vim script syntax
echomsg 'Vim 9 script is not available')
finish
endif

vim9script

# Now, Vim 9 script syntax is assumed
# The comment delimiter must be #

Hope this helps,
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 on the web visit https://groups.google.com/d/msgid/vim_use/v5kj3s%24vbo%241%40ciao.gmane.io.

Configuration file does not support #

Why does an error occur when changing the comment of the vim9.1 configuration file to #? 9.1 does not support #

--
--
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/5706f749-f601-467c-86dd-b800f6f54efan%40googlegroups.com.

Re: ":b {bufname}" tab-completion uses whole filepath

On 2024-06-14, Enan Ajmain <3nan.ajmain@gmail.com> wrote:
> I use ':b' quite often. And I use a substring of the bufname to jump to
> that buffer. Works quite well.
>
> But a problem is that the substring I provide isn't only matched with
> the buffer names but also the filenames. See these examples:
>
> :ls
> 1 #h "example\predict.py" line 25
> 2 a "deeplog\deeplog.py" line 0
> 4 %a "example\train.py" line 37
> :b deep<tab>
>
> Then when I type ":b deep<tab>", the matches shown are:
>
> E:\projects\log-parsing\deeplog\example\predict.py
> deeplog\deeplog.py
> E:\projects\log-parsing\deeplog\example\train.py
>
> We can see that vim is matching the filepaths instead of only the buffer
> names. Can I change this behavior? Preferably with vimscripting, --

If you don't mind using a (lightweight) plugin, you can do it with my
Zeef¹ plugin. Zeef has a buffer switcher, which may or may not work for
you, but simplifying the creation of one tailored to your own specific
needs is the very purpose of the plugin. This is an example:

vim9script
import autoload 'zeef.vim'

def SwitchToBuffer(items: list<string>)
execute 'buffer' matchstr(items[0], '^\s*\zs\d\+')
enddef

zeef.Open(
execute('ls')->split("\n"),
SwitchToBuffer,
'Choose buffer',
{multi: false},
)

Hope this helps,
Life.

¹ https://github.com/lifepillar/vim-zeef



--
--
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/v599m0%248b7%241%40ciao.gmane.io.

Re: partial syntax in vim

On 2024-06-17, Andreas Otto <aotto1968zwei@gmail.com> wrote:
> Hi is it possible to change the syntax for a limit part of a file?

Yes. See :help syn-include and :help mysyntaxfile-add.

> example: tcl file with bash syntax used with "pseudo code" vim: push … vim:

I do not recommend using comments with `vim:` because they are
interpreted specially by Vim. Just use (for instance):

if {checkNotIgnore("DIFF")} {
File_Exec_BASH {
# syntax=bash
[...]
# pop syntax
} <@stdin >@stdout 2>@stderr
}

Create ~/.vim/after/syntax/tcl.vim with this content:

unlet b:current_syntax
syn include @Bash syntax/bash.vim
syn region tclBash matchgroup=Comment start=/^\s*# syntax=bash/ end=/^\s*# pop syntax/ contains=@Bash
let b:current_syntax = "tcl"

Hope this helps,
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 on the web visit https://groups.google.com/d/msgid/vim_use/v598nh%2433u%241%40ciao.gmane.io.

partial syntax in vim

Hi is it possible to change the syntax for a limit part of a file?

example: tcl file with bash syntax used with "pseudo code" vim: push … vim: pop

if {checkNotIgnore("DIFF")} {
  File_Exec_BASH {
    # vim: push syntax=bash
    set -ue

    [[ "$(yes_or_no.bash 'want to exit?')" == "y" ]] && exit

    declare -a files=($(find . -name .vimrc 2>/dev/null))

    git diff "${files[@]}"

    if [[ $(git status --porcelain "${files[@]}") ]] ; then
      if [[ "$(yes_or_no.bash 'commit changes?')" = "y" ]] ; then
        git commit -m lng_Shortcut.tcl "${files[@]}"
      fi
      :
    fi
    exit 0
    # vim: pop syntax
  } <@stdin >@stdout 2>@stderr
}

--
--
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/abc1d980-74a7-4192-a288-6ad802758888n%40googlegroups.com.

Re: ":b {bufname}" tab-completion uses whole filepath

On Fr, 14 Jun 2024, Enan Ajmain wrote:

> On Fri, 14 Jun 2024 22:52:10 +0200
> Christian Brabandt <cblists@256bit.org> wrote:
> >
> > You could try the following mapping:
> >
> > :cnoremap <expr> B getcmdtype()==#':'&&getcmdpos()==1?'b */':'B'
> >
> > And then type :B which would expand to :b */ on the commandline and then
> > whatever you type would be anchored to the directory separator.
>
> I think the cnoremap only maps 'B' to expand to "b */" if it's at the
> start of the commandline. But what's "b */" supposed to do? I added
> this mapping and then typed "deep" (so the whole commandline became "b
> */deep" and then pressed tab. It didn't do anything. No completion.

Ah Windows, I didn't think about it. So unless you use shellslash,
you'll need to change the mapping to use a backslash instead:

:cnoremap <expr> B getcmdtype()==#':'&&getcmdpos()==1?'b *\':'B'

> Could you explain the logic behind "anchored to the directory
> separator"?

The idea is, that you want everything that you typed to be matched after
a directory separator. So instead of :b deeplog<tab> which presents you
with 3 different files, anchor the pattern to the directory separator:
\deeplog.py which Vim shall then only complete if it matches the
directory separator followed by whatever you enter.

> Note that I also tried "b *\" and "b *\\" since I'm in Windows.

Try if :b *\<pattern><tab> works for you.


Thanks,
Christian
--
Unfair animal names:

-- tsetse fly -- bullhead
-- booby -- duck-billed platypus
-- sapsucker -- Clarence
-- Gary Larson

--
--
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/Zm2eN1txfljI05dC%40256bit.org.