bugGNU Octave - Bugs: bug #57259, parse error in TeX interpreter...

 
 

bug #57259: parse error in TeX interpreter leads to later error in legend()

Submitter:  Rik <rik5>
Submitted:  Mon 18 Nov 2019 10:43:25 PM UTC
   
 
Category:  Octave Function Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 19 Nov 2019 04:17:11 PM UTC, comment #2: 

Don't know which commit did it, but this no longer causes a problem.  Closing report.

Rik <rik5>
Group administrator
Tue 19 Nov 2019 03:45:22 PM UTC, comment #1: 

One of the recent commits must have fixed this.

Pantxo Diribarne <pantxo>
Group Member
Mon 18 Nov 2019 10:43:25 PM UTC, original submission:  

Code to reproduce:


close all
x = 0:0.1:10;
plotyy (x, sin (x), x, cos (x))
legend ("sin(x)" , "cos{x)")
TeX parse error: syntax error
TeX parse error: syntax error
TeX parse error: syntax error
legend ("sin(x)" , "cos(x)")
error: set: unknown axes property __legend_handle__
error: called from
    legend at line 198 column 7


The first call to legend had a typo--a '{' instead of a '('--which caused the TeX parser to throw an error.  The legend, however, was correctly created.  When I went to correct the text by calling legend again I got an error which I don't think is correct.

Rik <rik5>
Group administrator

 

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

Attach Files:
   
   
Comment:
   

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 pantxo (Posted a comment)
  • -email is unavailable- added by rik5 (Submitted the item)
  • -email is unavailable- added by rik5
  •  

    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.

    Only group members can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-11-19 rik5 StatusReady For Test Fixed
        Open/ClosedOpen Closed
    2019-11-19 pantxo StatusConfirmed Ready For Test
    2019-11-18 rik5 Carbon-Copy- Added pantxo

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code