git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] clean up some code around editors

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Aug 6, 2025, 10:07 UTC
Message-ID
<350146ae-b909-4d9f-91f3-64bc2ddfcd60@gmail.com>
In-Reply-To
<20250805024044.30024-1-ben.knoble+github@gmail.com>
Hi Ben
On 05/08/2025 03:40, D. Ben Knoble wrote:
Show 7 quoted lines
> 
> These patches clean up some old code in the editor tests and subsystem
> that does not use our modern idioms. Patrick previously argued the test
> cleanup doesn't go far enough, and he may be right, but I think the
> preserving the semantics of the test for overrides /and/ automatically
> resetting the environment is tricky, unless we can use a subshell for
> the whole thing?

I think we could do it if we put the loop inside a subshell that was inside test_expect_success(). That would mean we'd have a single test for all the various combinations. That script could certainly use more cleanup to stop running git outside of test_expect_success() and use things like test_must_fail(), write_script(), test_commit_message() etc. but I think that can always come later. The first patch here is a welcome improvement even if it does not fix all the issues in that test file. The second patch looks good too.

Thanks for re-submitting these
Phillip
Show 57 quoted lines
> v1: https://lore.kernel.org/git/20250520193506.95199-1-ben.knoble+github@gmail.com/
> Published-as: https://github.com/benknoble/tree/editor-cleanup
> 
> D. Ben Knoble (2):
>    t7005: sanitize test environment for subsequent tests
>    editor: use standard strvec API to receive environment for external
>      editors
> 
>   builtin/commit.c  |  2 +-
>   editor.c          | 10 +++++-----
>   editor.h          |  7 ++++---
>   t/t7005-editor.sh |  7 +++----
>   4 files changed, 13 insertions(+), 13 deletions(-)
> 
> Diff-intervalle :
> 1:  da4fcc237b ! 1:  a37db65107 t7005: sanitize test environment for subsequent tests
>      @@ Commit message
>           Some of the editor tests manipulate the environment or config in ways
>           that affect future tests (because they test a sequence of overrides),
>           but those modifications are visible to future tests and create a footgun
>      -    for them. Use test_config and undo environment modifications once
>      -    finished.
>      +    for them.
>      +
>      +    We can't make the environment-munging override tests undo their
>      +    modifications because they rely on editor variables overriding other
>      +    previously-set editor variables.
>      +
>      +    Use test_config and undo environment modifications once finished.
>       
>           Signed-off-by: D. Ben Knoble <ben.knoble+github@gmail.com>
>       
> 2:  7b3b6b08f0 ! 2:  5450c99f59 editor: use standard strvec API to receive environment for external editors
>      @@ Commit message
>           Going back to the introduction of the env parameter for the editor in
>           8babab95af (builtin-commit.c: export GIT_INDEX_FILE for launch_editor as
>           well., 2007-11-26), we pass a constant array of strings: as the
>      -    surrounding APIs evolved to use strvecs, the editor code did not.
>      +    surrounding APIs evolved to use strvecs (see 8d7aa4ba6a
>      +    (builtin/commit.c: remove the PATH_MAX limitation via dynamic
>      +    allocation, 2017-01-13) and later 46b225f153 (Merge branch 'jk/strvec',
>      +    2020-08-10)), the editor code did not.
>       
>           There is only one caller of all 3 editor APIs that does not pass a NULL
>           environment (the same caller for which this parameter was added), and
>           it already has a strvec available to use.
>       
>      -    Signed-off-by: D. Ben Knoble <ben.knoble+github@gmail.com>
>           Helped-by: Johannes Schindelin <johannes.schindelin@gmx.de>
>      +    Signed-off-by: D. Ben Knoble <ben.knoble+github@gmail.com>
>       
>        ## builtin/commit.c ##
>       @@ builtin/commit.c: static int prepare_to_commit(const char *index_file, const char *prefix,
> 3:  cb48533115 < -:  ---------- run-command: prep_childenv on all platforms
> 4:  d2e54fdf75 < -:  ---------- drop git_exec_path() from non-Git commands' PATH
> 
> base-commit: 112648dd6bdd8e4f485cd0ae11636807959d48be
Previous: D. Ben KnobleNext: D. Ben Knoble
Message 30 of 73 in “Drop git-exec-path from non-Git child programs”
  1. 0/4 Drop git-exec-path from non-Git child programsD. Ben Knoble, May 20, 2025
  2. 1/4 t7005: sanitize test environment for subsequent testsD. Ben Knoble, May 20, 2025
  3. Patrick SteinhardtMay 21, 2025
  4. D. Ben KnobleMay 21, 2025
  5. 2/4 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, May 20, 2025
  6. Patrick SteinhardtMay 21, 2025
  7. D. Ben KnobleMay 21, 2025
  8. Patrick SteinhardtMay 21, 2025
  9. Junio C HamanoMay 21, 2025
  10. Junio C HamanoMay 21, 2025
  11. 3/4 run-command: prep_childenv on all platformsD. Ben Knoble, May 20, 2025
  12. Patrick SteinhardtMay 21, 2025
  13. Phillip WoodMay 21, 2025
  14. D. Ben KnobleMay 21, 2025
  15. 4/4 drop git_exec_path() from non-Git commands' PATHD. Ben Knoble, May 20, 2025
  16. Junio C HamanoMay 20, 2025
  17. D. Ben KnobleMay 21, 2025
  18. Patrick SteinhardtMay 21, 2025
  19. Phillip WoodMay 21, 2025
  20. Patrick SteinhardtMay 21, 2025
  21. Phillip WoodMay 21, 2025
  22. Patrick SteinhardtMay 26, 2025
  23. Justin ToblerMay 21, 2025
  24. Patrick SteinhardtMay 26, 2025
  25. D. Ben KnobleMay 21, 2025
  26. Junio C HamanoMay 21, 2025
  27. Phillip WoodMay 22, 2025
  28. D. Ben KnobleAug 5, 2025
  29. 0/2 clean up some code around editorsD. Ben Knoble, Aug 5, 2025
  30. Phillip WoodAug 6, 2025
  31. 1/2 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 5, 2025
  32. 2/2 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, Aug 5, 2025
  33. 0/3 clean up some code around editorsD. Ben Knoble, Aug 10, 2025
  34. D. Ben KnobleAug 10, 2025
  35. Ben KnobleAug 10, 2025
  36. 0/4 clean up some code around editorsD. Ben Knoble, Aug 11, 2025
  37. Ben KnobleAug 11, 2025
  38. Eric SunshineAug 12, 2025
  39. D. Ben KnobleAug 12, 2025
  40. Junio C HamanoAug 12, 2025
  41. Eric SunshineAug 12, 2025
  42. Junio C HamanoAug 12, 2025
  43. Eric SunshineAug 12, 2025
  44. 0/3 clean up some code around editorsD. Ben Knoble, Aug 12, 2025
  45. Phillip WoodAug 13, 2025
  46. Junio C HamanoAug 13, 2025
  47. D. Ben KnobleAug 13, 2025
  48. 0/3 clean up some code around editorsD. Ben Knoble, Aug 13, 2025
  49. Phillip WoodAug 15, 2025
  50. 1/3 t7005: use modern test styleD. Ben Knoble, Aug 13, 2025
  51. 2/3 t7005: stop abusing --exec-pathD. Ben Knoble, Aug 13, 2025
  52. 3/3 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 13, 2025
  53. 1/3 t7005: use modern test styleD. Ben Knoble, Aug 12, 2025
  54. 2/3 t7005: stop abusing --exec-pathD. Ben Knoble, Aug 12, 2025
  55. 3/3 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 12, 2025
  56. 1/4 t7005: use modern test styleD. Ben Knoble, Aug 11, 2025
  57. 2/4 t7005: stop abusing --exec-pathD. Ben Knoble, Aug 11, 2025
  58. 3/4 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 11, 2025
  59. Eric SunshineAug 11, 2025
  60. D. Ben KnobleAug 12, 2025
  61. Eric SunshineAug 12, 2025
  62. 4/4 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, Aug 11, 2025
  63. Eric SunshineAug 11, 2025
  64. Junio C HamanoAug 11, 2025
  65. 1/3 t7005: use modern test styleD. Ben Knoble, Aug 10, 2025
  66. Phillip WoodAug 10, 2025
  67. Phillip WoodAug 11, 2025
  68. 2/3 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 10, 2025
  69. Phillip WoodAug 10, 2025
  70. Ben KnobleAug 10, 2025
  71. Eric SunshineAug 10, 2025
  72. Phillip WoodAug 11, 2025
  73. 3/3 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, Aug 10, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.