Hi Avi, all.
Well, filing out using DVS adds lf to my line endings.
Avi, you said before that this comes from working with CVS, which requires it.
Is there some way us non-CVS users can avoid this, hmm, feature? ;-)
Maybe a PackageInfo subclass for CVS users (that minority that includes the DVS author - yes I know that's pretty damn cheeky)? or something?
Daniel
On Thu, 31 Oct 2002 danielv@netvision.net.il wrote:
Hi Avi, all.
Well, filing out using DVS adds lf to my line endings.
Avi, you said before that this comes from working with CVS, which requires it.
Is there some way us non-CVS users can avoid this, hmm, feature? ;-)
Ok, yes, I need to provide an option for that (although it should go at the PackageManager level, not the PackageInfo level).
As a quick hack, just modify FilePackageDumper>>storePackage: to suit yourself (eg,
storePackage: aPackage stream := fileStream. super storePackage: aPackage
would do nicely).
Avi
Quoting Avi Bryant avi@beta4.com:
On Thu, 31 Oct 2002 danielv@netvision.net.il wrote:
Hi Avi, all.
Well, filing out using DVS adds lf to my line endings.
Avi, you said before that this comes from working with CVS, which requires it.
CVS does not require lfs. It is up to the CVS client executable to convert the local line ending on the client OS to lfs when talking to the server, and vice versa.
regards, Göran
Göran Hultgren, goran.hultgren@bluefish.se GSM: +46 70 3933950, http://www.bluefish.se "Department of Redundancy department." -- ThinkGeek
On Thu, 31 Oct 2002, [ISO-8859-1] G�ran Hultgren wrote:
Quoting Avi Bryant avi@beta4.com:
On Thu, 31 Oct 2002 danielv@netvision.net.il wrote:
Hi Avi, all.
Well, filing out using DVS adds lf to my line endings.
Avi, you said before that this comes from working with CVS, which requires it.
CVS does not require lfs. It is up to the CVS client executable to convert the local line ending on the client OS to lfs when talking to the server, and vice versa.
True. Better to say, Unix and Windows require LFs (since those CVS clients are assuming the files they get have LFs in them). On the Mac it wouldn't be necessary.
Avi
Avi Bryant avi@beta4.com wrote:
On Thu, 31 Oct 2002, [ISO-8859-1] Göran Hultgren wrote:
Quoting Avi Bryant avi@beta4.com:
On Thu, 31 Oct 2002 danielv@netvision.net.il wrote:
Hi Avi, all.
Well, filing out using DVS adds lf to my line endings.
Avi, you said before that this comes from working with CVS, which requires it.
CVS does not require lfs. It is up to the CVS client executable to convert the local line ending on the client OS to lfs when talking to the server, and vice versa.
True. Better to say, Unix and Windows require LFs (since those CVS clients are assuming the files they get have LFs in them). On the Mac it wouldn't be necessary.
I thought the Win CVS client converts from/to CRLFs.
Avi
regards, Göran
danielv@netvision.net.il wrote:
Hi Avi, all.
Well, filing out using DVS adds lf to my line endings.
Avi, you said before that this comes from working with CVS, which requires it.
Is there some way us non-CVS users can avoid this, hmm, feature? ;-)
How about using CrLfFileStream? I'm not sure why people *don't* turn this on. If you leave it off, then you are implicitly saying that "Squeak text files" are the same as "OS text files", which is only true on Mac's. If you just turn on CrLfFileStream, then all of your text files will start working properly.
IMHO, CrLfFileStream should be the default file class in Squeak. It's proven its worth and stability, and people who don't use it keep painfully reinventing it.
Lex
On Sunday 03 November 2002 04:24 pm, Lex Spoon wrote:
How about using CrLfFileStream? I'm not sure why people *don't* turn this on. If you leave it off, then you are implicitly saying that "Squeak text files" are the same as "OS text files", which is only true on Mac's. If you just turn on CrLfFileStream, then all of your text files will start working properly.
Last I tried this, there was some brokenness (I forget where, though). I posted some changes to the list to fix these.
squeak-dev@lists.squeakfoundation.org