Closed dragly closed 8 years ago
FYI, latex.py had \r\n newlines (file edited on Windows?). Changed to Unix \n.
That's strange. It was opened in Atom on Ubuntu and only one line was changed.
I think the \r\n was there from before. Looking at the git history it seems like the \r\n were introduced in 3df1df8e from 3b5b9e7.
Very, very strange...that commit is from 2015 and I haven't seen any \r\n in that file in the meantime...And Atom on Ubuntu should be \r-safe... Anyway, we have a much better escape syntax for lst environments! :)
On 2 March 2016 at 15:41, Svenn-Arne Dragly notifications@github.com wrote:
That's strange. It was opened in Atom on Ubuntu and only one line was changed.
I think the \r\n was there from before. Looking at the git history it seems like the \r\n were introduced in 3df1df8 https://github.com/hplgit/doconce/commit/3df1df8e03f6ec4f9e9b03d802b7271be3fac097 from 3b5b9e7 https://github.com/hplgit/doconce/commit/3b5b9e72cc9ff00fc94db626afd3b80f004a035a .
— Reply to this email directly or view it on GitHub https://github.com/hplgit/doconce/pull/69#issuecomment-191263772.
Code or text files containing pipes '|' are garbled when formatted by lstlistings. This is caused by the escapeinside setting in lstset. Because pipes are so common in code and data files, I would suggest using more obscure escape characters or sequences.
This pull request changes the escape sequence to (@* and *@) such that this example would work: