Hi Junio and David.
Rule is in fact quite simple.
If it's a text-file and it contains a LF, a CRLF or a CR, then that's a
line-break. :)
-So everywhere a LF is checked for, a CR should most likely be checked for.
Usually, when checking for CRLF, one is looking for the LF. If a CR precedes
the LF
F and CRLF, such as a text-file,
that contains all 3 kinds of line endings (because 3 different people have been
editing the file).
Love
Jens
On Wed, 26 Sep 2012 12:12:39 +0200, Jens Bauer wrote:
> The implementation would be dependent on on how git is currently
> handling lines.
> Wor
Hi David and Junio.
At first, I was planning to reply that I'd probably not be qualified for that.
But to tell the truth, I have been writing a lot of CR/LF/CRLF code throughout
the years, so maybe I could do it.
Unfortunately, I have to go slow about programming, because I burned myself out
a n
so it generates correct line endings, instead of showing one long
line with a lot of "\r" in them.
[When thinking about all these CR/LF problems, I am grateful that Sinclair
Research did not continue to use the ZX81 characterset in the ZX Spectrum.
Imagine a mess we could have had!
work,
because \r and \n were swapped on the compiler, so I asked the author to use
\15 and \12, which made it fully portable]
It now works even better. I can't and won't complain - thank you. =)
Love
Jens
On Thu, 13 Sep 2012 20:34:08 +0200, Johannes Sixt wrote:
> Am 13.09.2012 17:53,
you're doing. -Git is how all other
open-source projects should be: Well-written and well-defined (oh - and fast!).
:)
Love
Jens
On Thu, 13 Sep 2012 14:23:44 -0400, Jeff King wrote:
> On Thu, Sep 13, 2012 at 08:17:20PM +0200, Jens Bauer wrote:
>
>> In my home directory, I have
diff mypcb.osm
...I get a strange diff. On line 3, one of the files shows a lot of control-m
() lines.
After that, I see lines, all prefixed with a '+', as if they were added.
I think I might be nearly there, just missing some obvious detail somewhere.
Any hints ?
Love
Jens
On Thu,
Hi Jeff and Drew.
Thank you for your quick replies! :)
The diffs look nasty yes; that's my main issue.
It can be worked around in many ways; eg a simple (but time consuming) way:
$ git diff mypcb.osm >mypcb.diff && nano mypcb.diff
-It'd be better to just pipe it into a regex, which changes CR to
Hi everyone.
I'm quite fond of git, and have used it for a while.
Recently, I've started making printed circuit boards (PCBs) using an
application called OsmondPCB (for Mac), and I'd like to use git to track
changes on these.
This application was originally written for the old Mac OS (Mac OS 6 t
9 matches
Mail list logo
