Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Fix hexdump command used for mercurial dirstate parsing
- X-seq: zsh-workers 39775
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: Frank Terbeck <ft@xxxxxxxxxxxxxxxxxxx>
- Subject: Re: [PATCH] Fix hexdump command used for mercurial dirstate parsing
- Date: Sun, 30 Oct 2016 15:55:30 +0000
- Cc: Reed Riley <john.reed.riley@xxxxxxxxx>, zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=8yx1EWdjpaGlJG9 dw/Rpr4ZzwSE=; b=WJ4hgDQkh2qNa6X0oWw97bhDLz5oSxjhrMbDOicKU4SpSS4 NMYQmxmSqYUxQkC2PxFAnWdJQaHfRYCalByY0wSa8szMg93boOHqwo4HdUVGuvbj tCJLTDHE80bn2GLQSJscUGTo/SjkmeGDsZZSSgQcbtMC9bem4cXuOdQUNljM=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=8yx1EWdjpaGlJG 9dw/Rpr4ZzwSE=; b=H3swFCou/iTn0eV3Hw9g05bcy1ZTNEo32KRxx6CR/02Rg4 iI9iqIJFCgRoZAsoT6aibkflqPVW0QmNM7OhfPmXiDZ/zzat6PyJxCg6F+pogdnR JTnecBwQyJlPGZ0OVVTednU22ExFN2RzI/KtMPMrFQReTor78ZHxJLdEhGztY=
- In-reply-to: <87y416drcq.fsf@ft.bewatermyfriend.org>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20161030024723.62832-1-john.reed.riley@gmail.com> <87y416drcq.fsf@ft.bewatermyfriend.org>
Frank Terbeck wrote on Sun, Oct 30, 2016 at 12:11:01 +0100:
> "xxd" is a command shipped with vim. Adding such a dependency is out of
> the question for me.
That's my fault. Reed's original patch used hexdump; I suggested to
just use xxd if hexdump gives trouble.
> It would be conceivable to make the command that is called in these
> places configurable via styles. But that is a separate issue to the
> one that fixes our use of hexdump.
Couldn't we replace hexdump by a pure zsh solution? We simply need to
read 20 octets and print their hexadecimal values.
Cheers,
Daniel
Messages sorted by:
Reverse Date,
Date,
Thread,
Author