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.