Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] editor.c: Libify launch_editor()
Date: Fri, 18 Jul 2008 14:07:57 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0807181405510.3932@eeepc-johanness> (raw)
In-Reply-To: <1216380408-21671-1-git-send-email-s-beyer@gmx.net>

Hi,

On Fri, 18 Jul 2008, Stephan Beyer wrote:

> This patch removes exit()/die() calls and builtin-specific messages from 
> launch_editor(), so that it can be used as a general libgit.a function 
> to launch an editor.

Thanks.  Now we have to convince Junio that it is a good idea :-)

> diff --git a/builtin-commit.c b/builtin-commit.c
> index ed3fe3f..64f69f3 100644
> --- a/builtin-commit.c
> +++ b/builtin-commit.c
> @@ -647,7 +647,9 @@ static int prepare_to_commit(const char *index_file, const char *prefix)
>  		char index[PATH_MAX];
>  		const char *env[2] = { index, NULL };
>  		snprintf(index, sizeof(index), "GIT_INDEX_FILE=%s", index_file);
> -		launch_editor(git_path(commit_editmsg), NULL, env);
> +		if (launch_editor(git_path(commit_editmsg), NULL, env))
> +			die("running editor failed.\n"
> +			"Please supply the message using either -m or -F option.");

In the error case, run_editor() already said more than "running editor 
failed.", right?  Maybe you just want to skip that line and keep the 
second?

> diff --git a/editor.c b/editor.c
> index 483b62d..5d7f5f9 100644
> --- a/editor.c
> +++ b/editor.c
> @@ -17,9 +17,8 @@ void launch_editor(const char *path, struct strbuf *buffer, const char *const *e
>  	terminal = getenv("TERM");
>  	if (!editor && (!terminal || !strcmp(terminal, "dumb"))) {
>  		fprintf(stderr,
> -		"Terminal is dumb but no VISUAL nor EDITOR defined.\n"
> -		"Please supply the message using either -m or -F option.\n");
> -		exit(1);
> +		"Terminal is dumb but no VISUAL nor EDITOR defined.\n");
> +		return 1;

Why not "return error()"?

Rest looks obviously correct to me!

Thanks,
Dscho

  reply	other threads:[~2008-07-18 12:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  0:36 [PATCH] Move launch_editor() from builtin-tag.c to editor.c Stephan Beyer
2008-07-18  1:14 ` Johannes Schindelin
2008-07-18  1:26   ` Stephan Beyer
2008-07-18 11:26   ` [PATCH] editor.c: Libify launch_editor() Stephan Beyer
2008-07-18 12:07     ` Johannes Schindelin [this message]
2008-07-18 12:35       ` [PATCH v2] " Stephan Beyer
2008-07-23 23:09       ` [PATCH] " Stephan Beyer
2008-07-24  1:48         ` Stephan Beyer
2008-07-25  8:36       ` Junio C Hamano
2008-07-25 10:28         ` Johannes Schindelin
2008-07-25 14:15           ` Stephan Beyer
2008-07-25 14:36             ` Johannes Schindelin
2008-07-25 16:28               ` [PATCH 1/2] Move launch_editor() from builtin-tag.c to editor.c Stephan Beyer
2008-07-25 16:28                 ` [PATCH 2/2] editor.c: Libify launch_editor() Stephan Beyer
2008-07-25 17:16                   ` Stephan Beyer
2008-07-26  3:00                 ` [PATCH 1/2] Move launch_editor() from builtin-tag.c to editor.c Johannes Schindelin
2008-07-26  3:14                   ` Stephan Beyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.1.00.0807181405510.3932@eeepc-johanness \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=s-beyer@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox