From: John Keeping <john@keeping.me.uk>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: git@vger.kernel.org
Subject: Re: Followup: Managing EXCEL with git - diff problem.
Date: Tue, 7 Apr 2015 14:26:28 +0100 [thread overview]
Message-ID: <20150407132628.GI21452@serenity.lan> (raw)
In-Reply-To: <02d801d07132$159f76a0$40de63e0$@nexbridge.com>
On Tue, Apr 07, 2015 at 08:55:11AM -0400, Randall S. Becker wrote:
> There was a discussion a while back on how to manage EXCEL content in git.
> This involved a simple trick of modifying the file extension from .xlsx to
> .zip and unpacking the file - resulting in a whole bunch of XML files. Git
> is happy with that part and the content can be managed - slightly.
>
> Unfortunately, EXCEL stores its XML content in single lines. Git has no
> problem with that either, as far as managing the content, but the lines can
> be really long. However, after about 20K in size, while the config:
>
> alias.wdiff=diff --color-words
>
> The ability of git to report differences goes away - as in no output from
> git diff. This occurs on Windows and Linux under git 2.3.3 and git 2.3.0.
> I'm not sure whether this is a user error, a usage error, or an actual
> problem.
>
> I had originally raised this as a SourceTree problem figuring it might be
> there: https://jira.atlassian.com/browse/SRCTREEWIN-3145
>
> Any advice (preferably no teasing - :-) - I am considering smudging but
> would rather avoid that)?
Perhaps try defining a specific diff driver for these files (see
git-attributes(5)). There is an xmldiff program [0] that might be able
to generate more useful diffs.
[0] http://www.logilab.org/project/xmldiff
prev parent reply other threads:[~2015-04-07 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 12:55 Followup: Managing EXCEL with git - diff problem Randall S. Becker
2015-04-07 13:26 ` John Keeping [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=20150407132628.GI21452@serenity.lan \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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).