** Changed in: lyx (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003419
Title:
Lyx does not preserve DOS/Unix line endings
To manage notifications abou
This bug should be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003419
Title:
Lyx does not preserve DOS/Unix line endings
To manage notifications about this bug go to:
https://bugs.launch
Just go bet by this issue too.
Using https://bitbucket.org for version control management, and it was not
happy with the line ending changes.
Had to do manual convertion, and might have to do everytime window uses
commit...
--
You received this bug notification because you are a member of Ubunt
In my opinion, this bug should be closed. There is a known solution and the
enhancement request was marked as 'wontfix' in LyX:
http://www.lyx.org/trac/ticket/8676
** Bug watch added: www.lyx.org/trac/ #8676
http://www.lyx.org/trac/ticket/8676
--
You received this bug notification because yo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lyx (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003419
Title:
Lyx do
Thanks, that works for me.
But I am not sure your argument holds.
Firstly, IMO a .lyx file is a machine controlled file format which
should probably not be edited by hand. At least that is what I think
naive users should never do. But it is diff/merge friendly, except for
the line endings.
Secon
The correct solution to this problem is to use
svn propset svn:eol native
This way windows users will see a file with CR+LF, and unix users will
see plain LF.
I agree that LyX could implement what you describe, but that would be a
problem for (say windows) users who use an editor (say notepa
