<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Text is linear as it appears, but it is actually structured, and might be even more flexible. <div class=""><br class=""></div><div class=""> In expressing structured ideas, I don't think it's easy to beat the ergonomics of text typing with certain graphics manipulation techniques, that'll be significant discovery in civilization of human beings once realized.<div class=""><br class=""></div><div class="">The Chinese word for civilization 文明 literally reads text and enlighten.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 2020-12-01, at 10:06, Mig Mit <<a href="mailto:migmit@gmail.com" class="">migmit@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">Please DO store code as ascii text. At the very least that would allow the use of external tools — sed, diff, git, whatever. Non-ascii representations were tried multiple times, and largely failed, in particular because of terrible interaction with other tools.<div class=""><br class=""></div><div class="">Also, please make sure your IDE is a good text editor. Because that's what the code is — not AST, but text. Until it is finished (to a certain lax definition of "finished") it is likely to not even be representable in AST form.<br class=""><br class=""><div dir="ltr" class="">Sent from my iPad</div><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On 2020. Dec 1., at 2:02, MarLinn <<a href="mailto:monkleyon@gmail.com" class="">monkleyon@gmail.com</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class=""><p class="">Most importantly: A good IDE is not a text editor, but an AST
editor. If the AST happens to be presented as text, that's a
choice of visualisation, nothing more. Better to start with a
graph-like visualisation to free the mind, then think through the
possible interactions. Maybe add the typical text-like
visualisation later. But don't start there or you'll just
re-invent notepad for the nth time.</p><p class="">Maybe don't even <i class="">store</i> the code as ascii text.<br class="">
</p>
<br class="">
<span class="">_______________________________________________</span><br class=""><span class="">Haskell-Cafe mailing list</span><br class=""><span class="">To (un)subscribe, modify options or view archives go to:</span><br class=""><span class=""><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe</a></span><br class=""><span class="">Only members subscribed via the mailman list are allowed to post.</span></div></blockquote></div></div>_______________________________________________<br class="">Haskell-Cafe mailing list<br class="">To (un)subscribe, modify options or view archives go to:<br class=""><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe</a><br class="">Only members subscribed via the mailman list are allowed to post.</div></blockquote></div><br class=""></div></div></body></html>