[cl-typesetting-devel] svn propset?

[Dmitriy Ivanov]

Hello Marc,

 MB> "Peter Seibel" <peter at gigamonkeys.com> wrote:
MB>> On Jul 7, 2005, at 4:23 PM, Marc Battyani wrote:
MB>>
MB> >> "Peter Seibel" <peter at gigamonkeys.com> wrote:
MB> >>
MB> >>
MB> >>> I'm not sure I understand things exactly correctly but it seems
MB> >>> that we could get subversion to take care of fixing line endings
MB> >>> between Mac, Unix, and Windows modes on .lisp files if someone
MB> >>> would do a    find . -name '*.lisp' -exec svn propset svn:eol-style
MB> >>> native {} \; in the cl-pdf and cl-typesetting directories and check
MB> >>> in the change. Anyone with commit access should also, I think, edit
MB> >>> their ~/.subversion/config file to uncomment the line:
MB> >>> enable-auto-props = yes and add a line to the [auto-props] section
MB> >>> like:    *.lisp = svn:eol-style=native This last bit will cause new
MB> >>> .lisp files to automatically be given the svn:eol-style property of
MB> >>> native when they are added. This would make dealing with the cl-pdf
MB> >>> and cl-typesetting sources a bit easier since tools like grep would
MB> >>> work properly on source files.
MB> >>
MB> >> Very good! As I use both Windows and Linux, I have been annoyed by
MB> >> these EOL
MB> >> problems too.
MB> >> I will try to do that tomorrow.
MB>>
MB>> Did this ever happen? svn diff still tells me about a bunch of files
MB>> being eol-style: native which, since I did the propset locally
MB>> suggests that maybe they're still not that way in the repo. Or
MB>> (likely) I just don't understand subversion.
MB>
MB> Hum, I changed the subversion config file on my notebook but forgot to
MB> do it on the server.
MB> I've just done it now (on the .lisp, .asd and .txt files) so tell me if
MB> its better.

I've just checked out cl-pdf and cl-typesetting with the TortoiseSVN 1.2.1
client on Windows. On opening files in the root directories, e.g.
cl-pdf/*.lisp, with Notepad, I see garbage. But I can normally read
cl-pdf/salza/*.lisp with Notepad.

Moreover, the eol-style:native property is missing from all the files.
--
Sincerely,
Dmitriy Ivanov
lisp.ystok.ru