ThingsusefultodoforGNUEmacs:*Primitiveforrandomaccessinsertionofpartofafile.*MakingI/Ostreamsforfiles,sothatreadandprin1canbeusedonfilesdirectly.TheI/Ostreamitselfwouldserveasafunctiontoreadorwriteonecharacter.*Ifafileyoucan't write is in a directory you can write, make sure it works to modify and save this file.* Make dired'scommandshandlecorrectlythecasewherelshaslistedseveralsubdirectories' contents. It needs to be able to tell which directory each file is really in, by searching backward for the line which identifies the start of a directory.* Add more dired commands, such as sorting (use the sort utility through call-process-region).* Make display.c record inverse-video-ness on a character by character basis. Then make non-full-screen-width mode lines inverse video, and display the marked location in inverse video.* VMS code to list a file directory. Make dired work.Long range: Ideas for extending GNU Emacs to deal with arbitrary character sets.I would like GNU Emacs to be extended to handle all the world'salphabetsandwordsigns.Idon't expect to have time to do such a thing in the nextfew years, so here are my ideas on the best way to do it.* Each graphic is represented by a sequence of ordinary 8-bit characters.* All the characters that make up such a sequence have codes >= 0200.* The first character of such a sequence is between 0200 and 0237.* The remaining characters of such a sequence are all 0240 or higher.* The first character of the sequence determines the number of charactersin the sequence. Thus, 0200...0207 could start two-character sequences,0210...0227 could start three-character sequences, and 0230 could startfour-character sequences. (Codes 0231...0237 would be reserved.)* Several common alphabets, and some mathematical symbols, would gettwo-character sequences. (Probably Greek, Russian, Hebrew(?), Arabic(?),Korean, and Japanese kana). The remaining alphabets, and some versions ofChinese, would get three-character sequences. Other sets of Chinesecharacters would get four-character sequences.Each country that uses Chinese characters has its own standard characterset, and it is not easy to correlate them to avoid overlap. So there mayneed to be several sets of Chinese characters. That is why they need somuch code space.True support for Hebrew and Arabic requires dealing with the problem ofwriting direction for mixed text; I don'tknowwhattodoforthat.*Thefunctionsthatusesyntaxtablewoulddeterminethesyntaxofasequencefromitsfirstcharacter.*Functionsinindent.cforcomputingwidthsandcolumnswoulddeterminethewidthofasequencefromitsfirstcharacter.Sowoulddisplayroutines.*Onlyafewothereditingroutineswouldneedanychange.Inparticular,searchingandregexpmatchingmightnotneedanychange.*Mostoftheworkrequiredwouldbeinredisplay.TheonlycasethatneedstobesupportediswithXwindows,sinceordinaryterminalscan'tdisplayallthesecharactersanyway.*Theremightneedtobecodetotranslatefilesfromthisformattowhateverformatistypicallystoredondisk.Iwouldbeveryunhappywithhalf-measures,suchassupportforJapaneseonly.