From: Junio C Hamano <gitster@pobox.com>
To: Rogan Dawes <rogan@dawes.za.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Allow git-mergetool to handle paths with a leading space
Date: Sun, 06 Jan 2008 03:48:03 -0800 [thread overview]
Message-ID: <7v3atb5g5o.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <4780B2BD.6020109@dawes.za.net> (Rogan Dawes's message of "Sun, 06 Jan 2008 12:51:41 +0200")
Rogan Dawes <rogan@dawes.za.net> writes:
>>> I am working on a project which has the root directory constructed
>>> with a leading space. i.e. ./ dir/. "read" skips the leading space
>>> char, and ends up with an incorrect filename, which can then not be
>>> found. Setting IFS=\n solves this problem.
>>
>> Does the project have a file that has letter 'n' (en) in its name?
>> Have you tested your patch while having a conflict in that file?
>
> Yes, it works correctly.
I am curious and puzzled...
$ echo 'ann1' | (IFS=\n read i; echo "<$i>")
<ann1>
$ echo 'ann1' | (IFS=\n read i j; echo "<$i>")
<a>
$ echo 'n1' | (IFS=\n read i j; echo "<$i>")
<>
Ok, "\n" is a funny way to say IFS does not matter as long as it
is set to a non whitespace letter.
It is VERY misleading as it looks as if the issue is fixed by
setting IFS to a single LF alone (excluding SP and HT from the
usual set), but that is not the patch is doing. It is setting
it to a single 'n'.
I think you still will lose backslash by using read, but I guess
you would not care about that too much.
If you really cared, you would do something like this, but you
would also need similar surgery in merge_file function itself
that parses text form of ls-files output that tries to verify
and extract paths, which I did not bother to touch in this
demonstration patch.
git-mergetool.sh | 33 ++++++++++++++++++++++-----------
1 files changed, 22 insertions(+), 11 deletions(-)
diff --git a/git-mergetool.sh b/git-mergetool.sh
index 2f31fa2..b7c5098 100755
--- a/git-mergetool.sh
+++ b/git-mergetool.sh
@@ -388,17 +388,28 @@ fi
if test $# -eq 0 ; then
- files=`git ls-files -u | sed -e 's/^[^ ]* //' | sort -u`
- if test -z "$files" ; then
- echo "No files need merging"
- exit 0
- fi
- echo Merging the files: $files
- git ls-files -u | sed -e 's/^[^ ]* //' | sort -u | while read i
- do
- printf "\n"
- merge_file "$i" < /dev/tty > /dev/tty
- done
+ doit=$(perl -e '
+ $/ = "\0";
+ my (%seen, @file);
+ my $ls_files;
+ open($ls_files, "-|", qw(git ls-files -u -z));
+ while (<$ls_files>) {
+ chomp;
+ s/^[^ ]* //;
+ $seen{$_}++;
+ }
+ @file = sort keys %seen;
+ if (!@file) {
+ print "echo No files need merging\n";
+ print "exit 0\n";
+ }
+ for (@file) {
+ s|'\''|'\''\\'\'''\''|g;
+ print "echo\n";
+ print "merge_file '\''$_'\'' </dev/tty >/dev/tty\n";
+ }
+ ')
+ eval "$doit"
else
while test $# -gt 0; do
printf "\n"
next prev parent reply other threads:[~2008-01-06 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 9:25 [PATCH] Allow git-mergetool to handle paths with a leading space Rogan Dawes
2008-01-06 10:18 ` Junio C Hamano
2008-01-06 10:51 ` Rogan Dawes
2008-01-06 11:48 ` Junio C Hamano [this message]
2008-01-07 7:37 ` Rogan Dawes
2008-01-07 9:09 ` Junio C Hamano
2008-01-08 1:19 ` Theodore Tso
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=7v3atb5g5o.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rogan@dawes.za.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;
as well as URLs for NNTP newsgroup(s).