[vim/vim] Add a place holder section for version 9.2 (PR #14060)

124 views
Skip to first unread message

Yegappan Lakshmanan

unread,
Feb 19, 2024, 7:53:11 PM2/19/24
to vim/vim, Subscribed

Add a version 9.2 section to version9.txt. As new features are added, this section should be updated.
This will make it easier to release the 9.2 version later. Otherwise, we need to go through thousands
of commits to get this information before the 9.2 release.


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/14060

Commit Summary

  • e94356b Add a place holder section for version 9.2

File Changes

(1 file)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/14060@github.com>

Yegappan Lakshmanan

unread,
Feb 19, 2024, 8:05:47 PM2/19/24
to vim/vim, Push

@yegappan pushed 1 commit.

  • d7707a8 Add new functions and autocmds


View it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/14060/push/17165957998@github.com>

Maxim Kim

unread,
Feb 19, 2024, 9:52:23 PM2/19/24
to vim/vim, Subscribed

Should we have Breaking changes section as well?

one that comes to my mind is default colorscheme visual highlight now has defined foreground which breaks colorschemes that were relying on Visual guifg=NONE.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/14060/c1953402254@github.com>

Yegappan Lakshmanan

unread,
Feb 19, 2024, 10:09:04 PM2/19/24
to vim/vim, Push

@yegappan pushed 1 commit.


View it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/14060/push/17167003968@github.com>

Yegappan Lakshmanan

unread,
Feb 19, 2024, 10:09:31 PM2/19/24
to vim...@googlegroups.com, reply+ACY5DGAXK6VXKA3FKI...@reply.github.com, vim/vim, Subscribed
Hi,

On Mon, Feb 19, 2024 at 6:52 PM Maxim Kim <vim-dev...@256bit.org> wrote:

Should we have Breaking changes section as well?

one that comes to my mind is default colorscheme visual highlight now has defined foreground which breaks colorschemes that were relying on Visual guifg=NONE.



Yes.  I have updated the PR to include the "incompatible changes" section.

Regards,
Yegappan 

vim-dev ML

unread,
Feb 19, 2024, 10:09:47 PM2/19/24
to vim/vim, vim-dev ML, Your activity

Hi,

On Mon, Feb 19, 2024 at 6:52 PM Maxim Kim ***@***.***> wrote:

> Should we have Breaking changes section as well?
>
> one that comes to my mind is default colorscheme visual highlight now has
> defined foreground which breaks colorschemes that were relying on Visual
> guifg=NONE.
>
>
>
Yes. I have updated the PR to include the "incompatible changes" section.

Regards,
Yegappan


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/14060/c1953414353@github.com>

Yegappan Lakshmanan

unread,
Feb 19, 2024, 10:44:13 PM2/19/24
to vim/vim, vim-dev ML, Push

@yegappan pushed 1 commit.


View it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/14060/push/17167291370@github.com>

Yegappan Lakshmanan

unread,
Feb 20, 2024, 10:37:56 AM2/20/24
to vim/vim, vim-dev ML, Push

@yegappan pushed 1 commit.


View it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/14060/push/17177438544@github.com>

Christian Brabandt

unread,
Feb 20, 2024, 1:48:42 PM2/20/24
to vim/vim, vim-dev ML, Comment

Merged #14060 into master.


Reply to this email directly, view it on GitHub.

You are receiving this because you commented.Message ID: <vim/vim/pull/14060/issue_event/11866025889@github.com>

Reply all
Reply to author
Forward
0 new messages