On 03/06/2010 4:14 PM, Ben M. wrote:
Thanks everyone for the feedback.
I'm using Mercurial, and unfortunately the eol support is rather screwy.
It's easy to make a case either way: that LyX should produce
consistent output, or that LyX is not responsible for line endings.
I'm having problems be
Thanks everyone for the feedback.
I'm using Mercurial, and unfortunately the eol support is rather screwy.
It's easy to make a case either way: that LyX should produce
consistent output, or that LyX is not responsible for line endings.
I'm having problems because of inconsistency, which I feel is
On 03/06/2010 4:57 AM, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Another nice possibility IMO is to set the property svn:eol-style to native
on the lyx file (if you use svn).
i even think this is the correct solution.
pavel
Me too. This is a platform/versioning problem, not a LyX one.
Abdelrazak Younes wrote:
> All editors under Wndows except for notepad handles LF only eol. I'd bet
> that an advanced user that is able to edit a LyX file would not use notepad
> for that anyway...
ok
pavel
Jean-Marc LASGOUTTES wrote:
> >> Another nice possibility IMO is to set the property svn:eol-style to
> >> native
> >> on the lyx file (if you use svn).
> >
> > i even think this is the correct solution.
>
> Could/should LyX help to do that, or is it trying to be too clever?
its doable in the s
Pavel Sanda writes:
> Jean-Marc Lasgouttes wrote:
>> Another nice possibility IMO is to set the property svn:eol-style to native
>> on the lyx file (if you use svn).
>
> i even think this is the correct solution.
Could/should LyX help to do that, or is it trying to be too clever?
JMarc
On 06/03/2010 11:23 AM, Pavel Sanda wrote:
Abdelrazak Younes wrote:
Well, IMO, the lyx file format should not change from one platform to the
other. The problem comes I guess from MSVC which converts '\n' to CR-LF
instead of simply LF.
but that means win users are not able to reasonab
Abdelrazak Younes wrote:
> Well, IMO, the lyx file format should not change from one platform to the
> other. The problem comes I guess from MSVC which converts '\n' to CR-LF
> instead of simply LF.
but that means win users are not able to reasonably view/edit .lyx file
directly anymore?
pavel
On 06/03/2010 10:57 AM, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Another nice possibility IMO is to set the property svn:eol-style to native
on the lyx file (if you use svn).
i even think this is the correct solution.
Well, IMO, the lyx file format should not change from o
Jean-Marc Lasgouttes wrote:
> Another nice possibility IMO is to set the property svn:eol-style to native
> on the lyx file (if you use svn).
i even think this is the correct solution.
pavel
Le 3 juin 10 à 04:08, Ben M. a écrit :
For version control purposes, it would be much nicer for me if LyX
instead *preserved* the EOL encoding on save. Would it be sensible to
provide a yes/no option such as "Preserve end-of-line encoding"?
Another nice possibility IMO is to set the property s
LyX seems to always use the native EOL encoding when saving.
Specifically, if I use Windows to open a Unix-encoded .lyx file, then
after saving it will have Windows-style CR/LF endings.
For version control purposes, it would be much nicer for me if LyX
instead *preserved* the EOL encoding on save.
12 matches
Mail list logo
