On Thu, 31 May 2012 14:49:38 -0400 erik quanstrom <quans...@quanstro.net> wrote:
> > Some people would love warp-to-location for Undo/Redo, some I'm sure > > would hate it. Some people can't stand that up/down arrow keys scroll > > the page rather than move the cursor (I'm not one). Acme might benefit > > from a config file in $home/lib/acme.conf or something. Yeah yeah, [...] > > i think the key here is that acme has reached the stage where if there were > version numbers, we'd be restricted to fiddling the 5th digit. acme is great, > but i think in terms of developing new ideas, it's time to move on. > > i'd like to see a new editor that builds on acme. the feature i'd like to see > is support for images and layouts. the design element i'd like to see is > lots of little programs rather than one big acme. so edit/win, edit/edit, > edit/dir might all be little programs that do part of what acme currently > does. I'd like to see acme split up. We already have page, we already have a shell window. What I want to see is a 1-file editor, 1-dir file lister (very simple), and a 1-page web browser. Put those with an acme-style rio (we can call it canal), and give all the apps right-click plumb and middle-click execute as appropriate. That would be my ideal project environment. We may be talking about the same thing but where you're saying "a new editor" I'm approaching it with the idea of enhancing the system and removing the need for a complex editor altogether. On a related note, what is the point of multi-file editors? I can see their use with a primitive OS, but given ed and a shell with loops... well I'd like to see what remains easier in a multi-file editor. -- This is obviously some strange usage of the word "simple" that I was previously unaware of.
