resolve conflicts

akkartik

Jan 23, 2025, 12:06 AM

3Q5JBAVZ7J2ORP4DCZJFFQ4X2KZTMUKAC3HLBZRJHCOZEJAZXGEAC

Dependencies

• [2] JM2PAF73 remove warning about persistence from Readme
• [3] 3LEFSNGD give up on supporting the OS paste operation
• [4] VCF6NJ5R document a gotcha
• [5] A2TQYJ6J .
• [6] 2DVVKKVA flesh out Readme
• [7] ZT6T2H7N update known issues
• [8] ALOY4663 .
• [9] IDGP4BJZ new known issue with drawings
• [10] TCNHUMIW one more known issue
• [11] FS2ITYYH record a known issue
• [12] 253TWKDA clean up
• [13] IXHSSD6U document a gotcha
• [14] YBPCBFOY stop recommending the terminal
• [15] ZTMRQZSW Readme

Change contents

• resurrect zombie in README.md at line 60
  [5.13]→[5.21:475](∅→∅),[5.13]→[5.21:475](∅→∅),[5.475]→[4.21:185](∅→∅),[5.475]→[4.21:185](∅→∅),[4.185]→[5.475:476](∅→∅),[5.475]→[5.475:476](∅→∅),[5.475]→[5.475:476](∅→∅)
  + * This approach puts one top-level definition per file, and so obscures the

  + order in which definitions are loaded. In particular, initializing a global

  + table to contain other global definitions will fail if you originally

  + authored the other global definitions after the table.

  +

  + I never initialize global tables with other definitions. That kind of thing

  + happens in `on.initialize` (akin to `love.load`; see reference.md) or

  + `on.code_change`.

  +

  + * Don't start the driver app while multiple freewheeling apps are running. If

  + you have a driver app running with one app, shut it down before you switch

  + apps.

  +
• resolve order conflict in README.md at line 60
  [3.119]

  [5.21]