From: janis_papanagnou+ng@hotmail.com   
      
   On 08.03.2024 12:48, Anthony Howe wrote:   
   > On 2024-03-07 22:59, Janis Papanagnou wrote:   
   >   
   > In Nvi multiple undo /redo is possible, it just extends historical   
   > behaviour in a way that doesn't conflict :   
   >   
   >     u . . . u .    Undo 4 back, redo 2 forward.   
      
   I see.   
      
   >   
   >> I've read somewhere that Vim even allows to navigate undo trees, but   
   >> that's something I never looked into.   
   >   
   > Never understood what an undo tree is vs a linear undo/redo would look   
   > like. Linear undo history makes sense and just about every editor   
   > supports it.   
      
   I associated that term with undos and new text repeatedly applied   
   so that a simple linear stack structure would not suffice to get   
   any intermediate change back.   
      
   But if one is so chaotic in writing and undoing text I wonder how   
   he would use that feature and still keeping his mind to navigate   
   such an undo tree. (Never needed it myself but maybe it's of use   
   to someone.)   
      
   >   
   >>> * vi macros.  [...]   
   >>   
   >> Oh, interesting and good to know. Have you any details what exactly   
   >> was the problem?   
   >   
   > Ugh.  That was like 1993.  [...]   
      
   Nevermind.   
      
   >>   
   >> I worked also colorless in the past for a long time; my stance was   
   >> that programs and data should be well structured and formatted and   
   >> legibly written so that syntax colors are not really necessary.   
   >   
   > Yep.  I agree.   
      
   I want to add that the habit was likely also influenced by the   
   fact that we printed source code on paper in B/W, so there was   
   a strong incentive to not rely on colors.   
      
   >   
   > [...]  Huge number of options is not   
   > a uniquely vi issue.  It plagues software in general and being able to   
   > satisfy many tastes, [...]   
      
   I agree.   
      
   >   
   > I think if you're going to clone an editor, you have to keep the   
   > historical aspect of it, even if it is not perfect.  Some extensions   
   > might be nice, sometimes one goes a little overboard, kinda like how   
   > "NetHack" has everything and the kitchen sink (it has sinks) in a rogue   
   > game.   
      
   You know the more recent roguelike variants (mostly also based   
   on Nethack)? - Nethack was still overseeable compared to some   
   of these. ;-)   
      
   Janis   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)