bugGNU TeXmacs - Bugs: bug #59567, LaTeX->TeXmacs problem with...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #59567: LaTeX->TeXmacs problem with inline verbatim and < chars.

Submitter:  Pierre-Henri Jondot <phjondot>
Submitted:  Sat 28 Nov 2020 08:17:33 AM UTC
   
 
Category:  None Priority:  5 - Normal
Item Group:  Error Status:  Fixed
Privacy:  Public Assigned to:  vdhoeven
Originator Name:  Open/Closed:  Closed
Release:  None Release:  1.99.16
Fixed Release:  None Fixed Release: 
Keywords: 

Tue 02 Mar 2021 08:17:54 PM UTC, comment #1: 

Fixed in revision 13361.

Joris van der Hoeven <vdhoeven>
Group administrator
Sat 28 Nov 2020 08:17:33 AM UTC, original submission:  

Hi,

While importing LaTeX file in TeXmacs with some inline verbatim such as :
\verb|0<=I<len(L)| or \verb|L[k]<=L[p]| the result got a little weird with wrong fonts.

And I got Warning and  Error messages :
Warning: Precorrecting [ 11 ] in L[k]<=L[p]
Error: Exception, bad path

It seemed I could still work with TeXmacs, but not really edit/correct those verbatim parts. When I tried, I actually had to force quit TeXmacs.

Looking at the .tm files, and comparing with inline verbatim composed within TeXmacs, it seems the LaTeX imported files translated < with escaping it : \< instead of what seems the expected \<less\> from what I could guess.

so \verb|0<=l<len(L)| became <verbatim|0\<=i\<len(L)> instead of <verbatim|0\<less\>=I\<less\>len(L)>

This bug does not appear with verbatim latex environment, only inline \verb one it seems.

Pierre-Henri Jondot <phjondot>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by vdhoeven (Posted a comment)
  • -email is unavailable- added by phjondot (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-03-02 vdhoeven StatusNone Fixed
        Assigned toNone vdhoeven
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code