Re: [Libusb-devel] >=autoconf-2.63 no grokmultiline AC_CONFIG_FILES?

[Segher B. <se...@ke...>]

>>> >>> Maybe you should check out _all_ text files as LF?
>>> >
>>> > Eh, Linux editors/viewers seem smart enough.
>>>
>>> Most tools do not work, or don't work correctly, with CRLF line endings
>>> on unix systems.  Even many editors/viewers do not (vim/emacs/less work
>>> more or less though).
>
> What other editors or viewers do you need, aside from 2 of those 3?  Fwiw,
> I
> specifically had emacs and less in mind.

Classic "more" does not work correctly.  "cat" does not work.  "vi" does
not work (and neither does vim in some configurations, and sometimes it
guesses wrong (when you have unicode on the first line, in some cases,
for example)).  "grep" does not work.  "diff" does not work.  "patch"
makes a mess.

>>> > Some Windows
>>> > editors/viewers/difftools are particularly brain-dead with regard to
> line
>>> > endings.
>>>
>>> And, presumably, you want to use those?  Hrm.
>
> Yes, because if it weren't for this line-ending issue, they'd be the clear
> winner over anything else I've tried.  I'm primarily thinking of notepad
> and
> windiff.

Won't notepad mutilate all files with a UTF marker at the start?

> Notepad loads in a split-second (not even noticeable, and not
> something I can say for vi or emacs, but analogous to nano), plus notepad
> is
> associated with a lot of files by default on Windows.  Obviously, you
> don't
> use it to make serious source code edits, but, by definition, any serious
> edits make the load time a negligible overhead.  I primarily have viewing
> in
> mind here, with either a viewer or editor.

So you want all source code (and other text files) to be checked out in
CRLF; and the MSVC files as binary.  And you do not care about Makefiles
and configure.ac etc.?

It sounds to me like the default config of msysgit should work fine for
you.


Segher