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.