From: Paul Campbell <pcampbell@kemitix.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Adam Tkac <atkac@redhat.com>,
"David A. Greene" <greened@obbligato.org>,
"Jesper L. Nielsen" <lyager@gmail.com>,
Michael Schubert <mschub@elegosoft.com>,
Techlive Zheng <techlivezheng@gmail.com>
Subject: Re: [PATCH] contrib/subtree: remove contradicting use options on echo wrapper
Date: Fri, 15 Feb 2013 23:18:42 +0000 [thread overview]
Message-ID: <CALeLG_mzBj7q2Vd6vLPTQWexKQB2bEDvh2NT9i9_m8atuiZFcA@mail.gmail.com> (raw)
In-Reply-To: <7vtxpdfbhx.fsf@alter.siamese.dyndns.org>
On Fri, Feb 15, 2013 at 10:39 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Paul Campbell <pcampbell@kemitix.net> writes:
>
>> Remove redundant -n option and raw ^M in call to echo.
>>
>> Call to 'say' function, a wrapper of 'echo', passed the parameter -n, then
>> included a raw ^M newline in the end of the last parameter. Yet the -n option
>> is meant to suppress the addition of new line by echo.
>>
>> Signed-off-by: Paul Campbell <pcampbell@kemitix.net>
>
> I generally do not comment on comment on contrib/ material, and I am
> not familiar with subtree myself, but
>
> for count in $(seq 0 $total)
> do
> echo -n "$count/$total^M"
> ... do heavy lifting ...
> done
> echo "Done "
>
> is an idiomatic way to implement a progress meter without scrolling
> more important message you gave earlier to the user before entering
> the loop away. The message appears, carrige-return moves the cursor
> to the beginning of the line without going to the next line, and the
> next iteration overwrites the previous count. Finally, the progress
> meter is overwritten with the "Done" message. Alternatively you can
> wrap it up with
>
> echo
> echo Done
>
> if you want to leave the final progress "100/100" before saying "Done."
>
> Isn't that what this piece of code trying to do?
>
>> ---
>> contrib/subtree/git-subtree.sh | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/contrib/subtree/git-subtree.sh b/contrib/subtree/git-subtree.sh
>> index 8a23f58..51146bd 100755
>> --- a/contrib/subtree/git-subtree.sh
>> +++ b/contrib/subtree/git-subtree.sh
>> @@ -592,7 +592,7 @@ cmd_split()
>> eval "$grl" |
>> while read rev parents; do
>> revcount=$(($revcount + 1))
>> - say -n "$revcount/$revmax ($createcount)
>> "
>> + say "$revcount/$revmax ($createcount)"
>> debug "Processing commit: $rev"
>> exists=$(cache_get $rev)
>> if [ -n "$exists" ]; then
[Apologies for resending this Junio. Forgot to hit reply all.]
Ah. I've not seen that done in shell before. In other languages I've
seen and used '\r' for this purpose, rather than a raw ^M.
I was getting frustrated with it as my apparently braindead text
editor was converting it to a normal unix newline, which would then
keep getting picked up by git diff.
Please ignore my patch.
--
Paul [W] Campbell
prev parent reply other threads:[~2013-02-15 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 22:20 [PATCH] contrib/subtree: remove contradicting use options on echo wrapper Paul Campbell
2013-02-15 22:39 ` Junio C Hamano
2013-02-15 23:18 ` Paul Campbell [this message]
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=CALeLG_mzBj7q2Vd6vLPTQWexKQB2bEDvh2NT9i9_m8atuiZFcA@mail.gmail.com \
--to=pcampbell@kemitix.net \
--cc=atkac@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=greened@obbligato.org \
--cc=lyager@gmail.com \
--cc=mschub@elegosoft.com \
--cc=techlivezheng@gmail.com \
/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).