Skip to content

Update develop.{txt,jax} #2332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 5, 2025
+18 −3
Merged

Update develop.{txt,jax} #2332

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e45b334
Update develop.{txt,jax}
h-east Sep 29, 2025
e4f3692
Update original
h-east Oct 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion doc/develop.jax
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
*develop.txt* For Vim バージョン 9.1. Last change: 2025 Sep 07
*develop.txt* For Vim バージョン 9.1. Last change: 2025 Sep 29


VIMリファレンスマニュアル by Bram Moolenaar
Expand Down Expand Up @@ -421,6 +421,13 @@ editorconfig プラグイン |editorconfig-install| と一緒に使用し、推
些細な変更でない場合は、必ず github でプルリクエストを作成すること。これによ
り、テストスイートがトリガーされる。

PR は理想的には 1 つの論理的変更に対する 1 つのコミットを含めるべきである。た
だし、複数の論理的かつ独立した変更を 1 つの PR にまとめたい場合は、複数のコミッ
トを含めることができる。これにより、長い PR のレビューも容易になる。各コミット
メッセージには、変更の理由を必ず記載すること。これはレビュープロセスに非常に役
立つ。各コミットが異なる論理的変更を扱う場合、それらは Vim のリポジトリ内で別々
のパッチとして適用されることになる。

*style-clang-format*
sound.c と sign.c は、配布された .clang-format ファイルに従って、
`clang-format` フォーマッタを使用して (半) 自動的にフォーマットできる。他のソー
Expand Down
12 changes: 10 additions & 2 deletions en/develop.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
*develop.txt* For Vim version 9.1. Last change: 2025 Sep 07
*develop.txt* For Vim version 9.1. Last change: 2025 Sep 29


VIM REFERENCE MANUAL by Bram Moolenaar
Expand Down Expand Up @@ -388,7 +388,7 @@ unreliable, fails on major platforms (e.g., macOS), and is only part of the
new release workflow. In practice, contributors edit the relevant `.pro` files
by hand when adding, removing, or modifying a function signatures.

This system has been in place since at least v1.24, when Vim’s functions were
This system has been in place since at least v1.24, when Vim's functions were
still written in K&R style.

==============================================================================
Expand Down Expand Up @@ -424,6 +424,14 @@ The basic steps to make changes to the code:
For any non-trivial change, please always create a pull request on github,
since this triggers the test suite.

A PR should ideally contain a single commit for a single logical change.
However, you can include several commits if you want to group multiple logical,
atomic changes in one PR. This can also make longer PRs easier to review. Be
sure to describe the reasoning for your changes in each commit message, as
this greatly helps with the review process. In cases where each commit
handles different logical changes, they will also be applied as separate
patches in Vim's repository.

*style-clang-format*
sound.c and sign.c can be (semi-) automatically formatted using the
`clang-format` formatter according to the distributed .clang-format file.
Expand Down