bugGNU TeXmacs - Bugs: bug #60363, Undo and redo corrupt nested...

 
 

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

bug #60363: Undo and redo corrupt nested itemize tags

Submitter:  Jeroen Wouters <jeronim>
Submitted:  Fri 09 Apr 2021 09:18:07 PM UTC
   
 
Category:  Editor Priority:  7 - High
Item Group:  Error Status:  Postponed
Privacy:  Public Assigned to:  vdhoeven
Originator Name:  Open/Closed:  Open
Release:  None Release: 
Fixed Release:  None Fixed Release: 
Keywords: 

Wed 05 May 2021 01:40:59 PM UTC, comment #1: 

This looks like an annoying (although apparently rare) problem.  I will look more closely into it when I will have time.

Joris van der Hoeven <vdhoeven>
Group administrator
Fri 09 Apr 2021 09:18:07 PM UTC, original submission:  

Doing undo and redo while editing nested itemize tags can corrupt nested itemize tags.

The follow is one sequence that leads to corruption:
1) Create two nested itemize tags
2) Enter "a" as the item for the first itemize and "b" as the item of the second level itemize. At this point the itemize looks like


* a
  o b


3) Move the cursor after the character "a" and press Backspace twice to delete the character and the item, to get



  o b


4) press Undo 6 times until everything is gone
5) press Redo 6 times to get back to the state of step 3
6) Press Undo 2 times

At this point the items look like

* aa
  o b

where the character "a" is repeated.

Further undoing and redoing leads to "Error: Exception, future corrupted" being thrown.

Jeroen Wouters <jeronim>
Group Member

 

(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 jeronim (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 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-05-05 vdhoeven CategoryNone Editor
        Priority5 - Normal 7 - High
        Item GroupNone Error
        StatusNone Postponed
        Assigned toNone vdhoeven

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code