Editing Gosling Emacs (section)

==Features==

Gosling Emacs was especially noteworthy because of the effective redisplay code,<ref>{{citation
| url=http://portal.acm.org/citation.cfm?id=806463
| publisher=Proceedings of the ACM SIGPLAN Symposium on Text Manipulation
| title=A Redisplay Algorithm
| first=James
| last=Gosling
| journal=ACM SIGPLAN Notices
| date=June 1981| volume=16
| issue=6
| pages=123–129
| doi=10.1145/872730.806463
| url-access=subscription
}}</ref> which used a [[dynamic programming]] technique to solve the classical [[string-to-string correction problem]]. The algorithm was quite sophisticated; that section of the source was headed by a [[Skull and crossbones (poison)|skull-and-crossbones]] in [[ASCII art]],<ref>{{cite web |url=https://donhopkins.com/home/archive/emacs/skull-and-crossbones.txt |title=Ultra-hot screen management package |author=<!--Not stated--> |date=n.d. |website= |publisher= |access-date=February 12, 2022}}</ref> warning any would-be improver that even if they thought they understood how the display code worked, they probably did not<!-- borges -->.<ref name="rms-slashdot">{{citation
| url       = http://features.slashdot.org/story/13/01/06/163248/richard-stallman-answers-your-questions
| title     = Richard Stallman Answers Your Questions
| first     = Richard
| last      = Stallman
| author-link = Richard M. Stallman
| editor    = samzenpus
| publisher = [[Slashdot]]
| date      = 7 January 2013
| quote     = The last piece of Gosmacs code that I replaced was the serial terminal scrolling optimizer, a few pages of Gosling's code which was proceeded by a comment with a skull and crossbones, meaning that it was so hard to understand that it was poison. I had to replace it, but worried that the job would be hard. I found a simpler algorithm and got it to work in a few hours, producing code that was shorter, faster, clearer, and more extensible. Then I made it use the terminal commands to insert or delete multiple lines as a single operation, which made screen updating far more efficient.}}</ref>