Skip to content

vimhelp: add an option to split codeblocks #588

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.

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Fat-Zer
Copy link
Contributor

@Fat-Zer Fat-Zer commented Jul 4, 2025

This introduces an option to split codeblocks as discussed in 1. The
default behaviour used to be to always split them. The new is to not,
unless requested via the option split_codeblocks.

Besides that the PR includes:

  • [vimhelp] some refactoring
  • [vimhelp] some new warnings
  • [vimhelp] minor documentation mistake fixes
  • small fixes to Testhelper
  • small TransTractor fixes

Fat-Zer added 4 commits July 4, 2025 21:26
As the comment above the list says it prevents ancestors from croaking
on the "debug" and "verbose" options if they don't utilise those.
This introduces an option to split codeblocks as discussed in [1]. The
default behaviour used to be to always split them. The new is to not,
unless requested via the option split_codeblocks.

Besides that the commit includes:
* some refactoring
* some new warnings

[1]: mquinson#551
* fix a typo in "translate" and its documentation
* move chdir out of update-po in case it gets skipped
@mquinson
Copy link
Owner

mquinson commented Jul 4, 2025

shit! I said maybe one hour ago that we were in string freeze for the translators. Maybe we could rush this changes in before anyone reads my mail?

@mquinson
Copy link
Owner

mquinson commented Jul 4, 2025

After reviewing the code, I have the feeling that it's a bit too large to rush it in. Maybe we should do 2 releases of po4a soon. One with what's already in master, and one with this PR and the fix to some of the bugs. We may hope that I'll find more time soon to fix them...

@Fat-Zer
Copy link
Contributor Author

Fat-Zer commented Jul 4, 2025

Yep, sure... There is a one big commit and a couple of minor vaguely related fixes; I can split them off into dedicated PRs if that eases the review...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants