From: Felipe Contreras <felipe.contreras@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] config: Use parseopt.
Date: Sun, 15 Feb 2009 14:51:45 +0200 [thread overview]
Message-ID: <94a0d4530902150451w2467bee2q225643f15ffffac1@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0902151329370.10279@pacific.mpi-cbg.de>
[-- Attachment #1: Type: text/plain, Size: 2781 bytes --]
On Sun, Feb 15, 2009 at 2:33 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Sun, 15 Feb 2009, Felipe Contreras wrote:
>
>> On Sun, Feb 15, 2009 at 1:26 PM, Johannes Schindelin
>> <Johannes.Schindelin@gmx.de> wrote:
>> > Hi,
>> >
>> > On Sun, 15 Feb 2009, Felipe Contreras wrote:
>> >
>> >> On Sun, Feb 15, 2009 at 12:32 AM, Johannes Schindelin
>> >> <Johannes.Schindelin@gmx.de> wrote:
>> >> > Hi,
>> >> >
>> >> > On Sat, 14 Feb 2009, Felipe Contreras wrote:
>> >> >
>> >> >> On Sat, Feb 14, 2009 at 9:59 PM, Johannes Schindelin
>> >> >> <Johannes.Schindelin@gmx.de> wrote:
>> >> >>
>> >> >> > On Sat, 14 Feb 2009, Felipe Contreras wrote:
>> >> >> >
>> >> >> >> + else if (actions & ACTION_EDIT) {
>> >> >> >> + const char *config_filename;
>> >> >> >> + if (config_exclusive_filename)
>> >> >> >> + config_filename = config_exclusive_filename;
>> >> >> >> + else
>> >> >> >> + config_filename = git_path("config");
>> >> >> >
>> >> >> > Why not reuse config_exclusive_filename here?
>> >> >>
>> >> >> You mean:
>> >> >> if (!config_exclusive_filename)
>> >> >> config_exclusive_filename = git_path("config");
>> >> >
>> >> > Yes.
>> >>
>> >> I'm not sure about this one. At least git_config should be moved before
>> >> that code, otherwise it will only try to read core.editor from the
>> >> exclusive_filename and that's not what we want.
>> >
>> > Ah! I did not think about core.editor, of course, but that is what got
>> > you started with git-config, after all.
>> >
>> > However, the next line sets config_exclusive_filename, does it not?
>>
>> Huh? Which line?
>
> Ah, I misremembered. Your current patch shows this:
>
> + else if (actions & ACTION_EDIT) {
> + const char *config_filename;
> + if (config_exclusive_filename)
> + config_filename = config_exclusive_filename;
> + else
> + config_filename = git_path("config");
> + git_config(git_default_config, NULL);
> + launch_editor(config_filename, NULL, NULL);
> + }
>
> ... which makes me believe that the point about moving git_config() before
> setting config_exclusive_filename is rather weak :-)
>
> + else if (actions & ACTION_EDIT) {
> + git_config(git_default_config, NULL);
> + launch_editor(config_exclusive_filename ?
> + config_exclusive_filename : git_path("config"),
> + NULL, NULL);
> + }
>
> (This has whitespace issues, as I copy-pasted it using kterm's clipboard
> functions.)
I thought on that before but now it makes more sense to me. Attaching the patch.
--
Felipe Contreras
[-- Attachment #2: 0001-config-Cleanup-editor-action.patch --]
[-- Type: application/octet-stream, Size: 1142 bytes --]
From 4b3db3d13261849cd7d561dc20bddb375f1430c8 Mon Sep 17 00:00:00 2001
From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Sun, 15 Feb 2009 14:46:58 +0200
Subject: [PATCH] config: Cleanup editor action.
Copy-paste from Johannes Schindelin.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
builtin-config.c | 9 +++------
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/builtin-config.c b/builtin-config.c
index 2c1ad71..bd7bac4 100644
--- a/builtin-config.c
+++ b/builtin-config.c
@@ -370,13 +370,10 @@ int cmd_config(int argc, const char **argv, const char *unused_prefix)
}
else if (actions & ACTION_EDIT) {
check_argc(argc, 0, 0);
- const char *config_filename;
- if (config_exclusive_filename)
- config_filename = config_exclusive_filename;
- else
- config_filename = git_path("config");
git_config(git_default_config, NULL);
- launch_editor(config_filename, NULL, NULL);
+ launch_editor(config_exclusive_filename ?
+ config_exclusive_filename : git_path("config"),
+ NULL, NULL);
}
else if (actions & ACTION_ADD) {
check_argc(argc, 2, 2);
--
1.6.1.3
next prev parent reply other threads:[~2009-02-15 12:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 2:05 [PATCH] config: Use parseopt Felipe Contreras
2009-02-14 9:28 ` Junio C Hamano
2009-02-14 9:35 ` Junio C Hamano
2009-02-14 10:41 ` Felipe Contreras
2009-02-14 10:37 ` Felipe Contreras
2009-02-14 11:40 ` Johannes Schindelin
2009-02-14 12:03 ` [PATCH v2] " Felipe Contreras
2009-02-14 15:21 ` Jeff King
2009-02-14 15:24 ` Felipe Contreras
2009-02-14 19:59 ` Johannes Schindelin
2009-02-14 20:19 ` Junio C Hamano
2009-02-14 21:08 ` human readable diffs, was " Johannes Schindelin
2009-02-14 20:31 ` Felipe Contreras
2009-02-14 22:32 ` Johannes Schindelin
2009-02-14 22:36 ` Jakub Narebski
2009-02-14 22:54 ` Johannes Schindelin
2009-02-15 9:04 ` Felipe Contreras
2009-02-15 11:26 ` Johannes Schindelin
2009-02-15 12:07 ` Felipe Contreras
2009-02-15 12:33 ` Johannes Schindelin
2009-02-15 12:51 ` Felipe Contreras [this message]
2009-02-15 13:38 ` Felipe Contreras
2009-02-15 19:31 ` Junio C Hamano
2009-02-15 19:41 ` Johannes Schindelin
2009-02-15 21:22 ` Junio C Hamano
2009-02-15 21:29 ` Johannes Schindelin
2009-02-17 0:50 ` Felipe Contreras
2009-02-15 19:36 ` Junio C Hamano
2009-02-14 12:15 ` [PATCH] " Felipe Contreras
2009-02-14 19:11 ` Johannes Schindelin
2009-02-14 19:14 ` Felipe Contreras
2009-02-14 19:24 ` Johannes Schindelin
2009-02-14 19:26 ` Johannes Schindelin
2009-02-14 21:13 ` Felipe Contreras
2009-02-14 19:29 ` Junio C Hamano
2009-02-14 20:09 ` Felipe Contreras
2009-02-14 20:35 ` Junio C Hamano
2009-02-14 21:01 ` Felipe Contreras
2009-02-14 21:10 ` Junio C Hamano
2009-02-14 21:24 ` Felipe Contreras
2009-02-14 21:15 ` Johannes Schindelin
2009-02-15 2:22 ` Junio C Hamano
2009-02-14 11:52 ` Jakub Narebski
2009-02-14 12:06 ` Felipe Contreras
2009-02-14 15:17 ` Jeff King
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=94a0d4530902150451w2467bee2q225643f15ffffac1@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).