> "Justin" == Justin Patrin <[EMAIL PROTECTED]> writes:
Justin> What conversions do you mean? Any decent text editor
Justin> should be able to deal with any line ending and not mess
Justin> with it. Of course, I use emacs which does the right thing
Justin> with any of the three
On Tue, Nov 28, 2006 at 07:43:51AM -0500, [EMAIL PROTECTED] wrote:
>
> Which suggests one option is to
> * recognise line-ends of any variety
> * ignore the line-end type when merging lines
> * but then, for lines that haven't changed except for line ending,
I mean, lines that got line-end
On Mon, Nov 27, 2006 at 01:28:42PM -0800, Justin Patrin wrote:
> On 11/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >Some OS's make it hard for rank beginners (though possibly experienced
> >on other systems) to find out how to do the necessary conversions. But
> >that is not a version co
In message <[EMAIL PROTECTED]> on Mon, 27 Nov 2006 20:19:34 -0600, "Kelly F.
Hickel" <[EMAIL PROTECTED]> said:
kfh> Richard, we have a version of cvs that runs on VMS. It's been 10
kfh> years since I worked with RMS, but IIRC a C program could open a
kfh> file in text mode, printf a string like
On 11/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Mon, Nov 27, 2006 at 10:22:25AM -0800, Justin Patrin wrote:
> On 11/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >On Mon, Nov 27, 2006 at 11:52:53AM +, Bruce Stephens wrote:
> >> Richard Levitte - VMS Whacker <[EMAIL PROTEC
>
> On Mon, Nov 27, 2006 at 10:59:13PM +0100, Richard Levitte - VMS
Whacker
> wrote:
> > And yet, we're still speaking about systems where the only
difference
> > is a character or two. On a record oriented filesystem, you MUST
> > convert text files to actual separate records (lines), or anythin
"Justin Patrin" <[EMAIL PROTECTED]> writes:
[...]
> As a heavy user of version control systems (CVS, SVN, and MTN
> mostly) I'm also against any automatic conversion of text line
> endings. While I understand that "some editors" and "some programs"
> don't like certain line endings, in the genera
On Mon, Nov 27, 2006 at 10:59:13PM +0100, Richard Levitte - VMS Whacker wrote:
> And yet, we're still speaking about systems where the only difference
> is a character or two. On a record oriented filesystem, you MUST
> convert text files to actual separate records (lines), or anything
> that deal
In message <[EMAIL PROTECTED]> on Mon, 27 Nov 2006 10:22:25 -0800, "Justin
Patrin" <[EMAIL PROTECTED]> said:
papercrane> As a heavy user of version control systems (CVS, SVN, and
papercrane> MTN mostly) I'm also against any automatic conversion of
papercrane> text line endings. While I understand
On Mon, Nov 27, 2006 at 10:22:25AM -0800, Justin Patrin wrote:
> On 11/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >On Mon, Nov 27, 2006 at 11:52:53AM +, Bruce Stephens wrote:
> >> Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> writes:
> >>
> >> [...]
> >>
> >> > That leads me back
On 11/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Mon, Nov 27, 2006 at 11:52:53AM +, Bruce Stephens wrote:
> Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > That leads me back to thinking that we still need to mark files that
> > are getting changed, and t
On Mon, Nov 27, 2006 at 11:52:53AM +, Bruce Stephens wrote:
> Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > That leads me back to thinking that we still need to mark files that
> > are getting changed, and that something automatic should happen to
> > them, so a fi
Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> writes:
[...]
> That leads me back to thinking that we still need to mark files that
> are getting changed, and that something automatic should happen to
> them, so a file will look the same checked out as before it got
> checked in.
I'm sure we
In message <[EMAIL PROTECTED]> on Mon, 27 Nov 2006 08:49:26 +0100, Ulf
Ochsenfahrt <[EMAIL PROTECTED]> said:
ulf> Just to clear this up. No I'm not saying that the conversion
ulf> stuff should be removed. I don't mind it being there for people
ulf> to use, as long as its not enabled by default, w
Richard Levitte - VMS Whacker wrote:
In message <[EMAIL PROTECTED]> on Mon, 27 Nov 2006 00:37:12 +, Bruce Stephens
<[EMAIL PROTECTED]> said:
monotone> Brian May <[EMAIL PROTECTED]> writes:
monotone>
monotone> >> "Richard" == Richard Levitte <- VMS Whacker <[EMAIL PROTECTED]>> writes:
In message <[EMAIL PROTECTED]> on Mon, 27 Nov 2006 00:37:12 +, Bruce
Stephens <[EMAIL PROTECTED]> said:
monotone> Brian May <[EMAIL PROTECTED]> writes:
monotone>
monotone> >> "Richard" == Richard Levitte <- VMS Whacker <[EMAIL
PROTECTED]>> writes:
monotone> >
monotone> > Richard> So
Brian May <[EMAIL PROTECTED]> writes:
>> "Richard" == Richard Levitte <- VMS Whacker <[EMAIL PROTECTED]>> writes:
>
> Richard> So, what I hear you say is that we should remove all the
> conversion
> Richard> stuff that exists today. Is that correct?
>
> What conversion stuff exists t
Nuno Lucas wrote:
> On 11/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> If we use an internal line ending standard, we should consider the
>> possibility of using the standard newline character NEL, "Next Line",
>> 0x85, unicode U+0085.
> You are forgetting I can (and actually I am) versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Patrin schreef:
> On 11/21/06, Derek Scherger <[EMAIL PROTECTED]> wrote:
>> So, would this be better as a (shared and versioned) project policy
>> entry with line ending styles specified by file name patterns. It seems
>> like it would handle t
19 matches
Mail list logo
