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

[PATCH v3 2/2] var: allow GIT_EDITOR to return null

From
Sean Allred via GitGitGadget <gitgitgadget@gmail.com>
Date
Nov 26, 2022, 14:17 UTC
Message-ID
<3d8bf3662fe92e61805a1d9ffbccf7a17b3d1e8c.1669472277.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.1434.v3.git.1669472277.gitgitgadget@gmail.com>
From: Sean Allred <allred.sean@gmail.com>

The handling to die early when there is no EDITOR is valuable when used in normal code (i.e., editor.c). In git-var, where null/empty-string is a perfectly valid value to return, it doesn't make as much sense.

Remove this handling from `git var GIT_EDITOR` so that it does not fail so noisily when there is no defined editor.

Signed-off-by: Sean Allred <allred.sean@gmail.com>
---
 builtin/var.c      |  7 +-----
 t/t0007-git-var.sh | 62 ++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 63 insertions(+), 6 deletions(-)
diff --git a/builtin/var.c b/builtin/var.c
index 5cbe32ec890..a1a2522126f 100644
--- a/builtin/var.c
+++ b/builtin/var.c
@@ -11,12 +11,7 @@ static const char var_usage[] = "git var (-l | <variable>)";
 
 static const char *editor(int flag)
 {
-	const char *pgm = git_editor();
-
-	if (!pgm && flag & IDENT_STRICT)
-		die("Terminal is dumb, but EDITOR unset");
-
-	return pgm;
+	return git_editor();
 }
 
 static const char *pager(int flag)
diff --git a/t/t0007-git-var.sh b/t/t0007-git-var.sh
index e56f4b9ac59..433d242897c 100755
--- a/t/t0007-git-var.sh
+++ b/t/t0007-git-var.sh
@@ -5,6 +5,12 @@ test_description='basic sanity checks for git var'
 TEST_PASSES_SANITIZE_LEAK=true
 . ./test-lib.sh
 
+sane_unset_all_editors () {
+	sane_unset GIT_EDITOR &&
+	sane_unset VISUAL &&
+	sane_unset EDITOR
+}
+
 test_expect_success 'get GIT_AUTHOR_IDENT' '
 	test_tick &&
 	echo "$GIT_AUTHOR_NAME <$GIT_AUTHOR_EMAIL> $GIT_AUTHOR_DATE" >expect &&
@@ -47,6 +53,62 @@ test_expect_success 'get GIT_DEFAULT_BRANCH with configuration' '
 	)
 '
 
+test_expect_success 'get GIT_EDITOR without configuration' '
+	(
+		sane_unset_all_editors &&
+		test_expect_code 1 git var GIT_EDITOR >out &&
+		test_must_be_empty out
+	)
+'
+
+test_expect_success 'get GIT_EDITOR with configuration' '
+	test_config core.editor foo &&
+	(
+		sane_unset_all_editors &&
+		echo foo >expect &&
+		git var GIT_EDITOR >actual &&
+		test_cmp expect actual
+	)
+'
+
+test_expect_success 'get GIT_EDITOR with environment variable GIT_EDITOR' '
+	(
+		sane_unset_all_editors &&
+		echo bar >expect &&
+		GIT_EDITOR=bar git var GIT_EDITOR >actual &&
+		test_cmp expect actual
+	)
+'
+
+test_expect_success 'get GIT_EDITOR with environment variable EDITOR' '
+	(
+		sane_unset_all_editors &&
+		echo bar >expect &&
+		EDITOR=bar git var GIT_EDITOR >actual &&
+		test_cmp expect actual
+	)
+'
+
+test_expect_success 'get GIT_EDITOR with configuration and environment variable GIT_EDITOR' '
+	test_config core.editor foo &&
+	(
+		sane_unset_all_editors &&
+		echo bar >expect &&
+		GIT_EDITOR=bar git var GIT_EDITOR >actual &&
+		test_cmp expect actual
+	)
+'
+
+test_expect_success 'get GIT_EDITOR with configuration and environment variable EDITOR' '
+	test_config core.editor foo &&
+	(
+		sane_unset_all_editors &&
+		echo foo >expect &&
+		EDITOR=bar git var GIT_EDITOR >actual &&
+		test_cmp expect actual
+	)
+'
+
 # For git var -l, we check only a representative variable;
 # testing the whole output would make our test too brittle with
 # respect to unrelated changes in the test suite's environment.
-- 
gitgitgadget
Previous: Sean Allred via GitGitGadget
Message 15 of 15 in “Improve consistency of git-var”
  1. 0/3 Improve consistency of git-varSean Allred via GitGitGadget, Nov 24, 2022
  2. 1/3 var: do not print usage() with a correct invocationSean Allred via GitGitGadget, Nov 24, 2022
  3. 2/3 var: remove read_varSean Allred via GitGitGadget, Nov 24, 2022
  4. Junio C HamanoNov 25, 2022
  5. 3/3 var: allow GIT_EDITOR to return nullSean Allred via GitGitGadget, Nov 24, 2022
  6. 0/2 Improve consistency of git-varSean Allred via GitGitGadget, Nov 25, 2022
  7. 1/2 var: do not print usage() with a correct invocationSean Allred via GitGitGadget, Nov 25, 2022
  8. Ævar Arnfjörð BjarmasonNov 25, 2022
  9. Sean AllredNov 26, 2022
  10. 2/2 var: allow GIT_EDITOR to return nullSean Allred via GitGitGadget, Nov 25, 2022
  11. Ævar Arnfjörð BjarmasonNov 25, 2022
  12. Sean AllredNov 26, 2022
  13. 0/2 Improve consistency of git-varSean Allred via GitGitGadget, Nov 26, 2022
  14. 1/2 var: do not print usage() with a correct invocationSean Allred via GitGitGadget, Nov 26, 2022
  15. 2/2 var: allow GIT_EDITOR to return nullSean Allred via GitGitGadget, Nov 26, 2022

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.