When I saw the length of the Acme thread, I thought "Wow, so much information!" But it turned out to be mostly flamage. Can't we all just get along?{C}

I don't believe in a single best IDE any more than a single best language. What is best depends on both the particular work and the coder's personal tastes. And, as with programming languages, I think it's good to familiarize yourself with different paradigms.

My nutshell evaluation of Acme is that it is for systems-level coding in C on modest-sized projects. It seems very well designed for that purpose but quickly becomes awkward as you move away. It is definitely not suited to working with Java or Lisp, or navigating large directories.

Acme is often compared to vi/emacs as a power-user's tool with a different operating paradigm. It is, but I think people wrongly point to the keyboard/mouse issue as the basic difference. The real difference is that vi/emacs are all about configurability but Acme focuses on integration with the system while not being configurable at all (unless you count hacking the source).

Also, the frequent reference to UTF-8 is a bit misleading. Handling Unicode is about more than just recognizing the code points. It is tricky to properly display the various scripts of the world. For a good treatment of the issues presented in a simple interface, look at the Yudit editor.

Finally, I'm kind of surprised at the lack of interest in controlling fonts. My usual coding font is 12 pt. Dina or Terminus. But if my eyes are really tired, I might switch to 16 pt. Monaco. On the other hand, I sometimes use 8 pt. ProFont to better get an overview. I would think even Plan 9 hackers would appreciate being able to quickly shift around like that.

On Wed, Aug 20, 2008 at 11:12 AM, Wendell xe yahoo.com> wrote:

...

One of the central tenets of Plan 9 is that everything is a file. So
all file based activities are really, really easy.

Most OO programming appears to follow a more DB oriented style (at
least those with horrendous packaging/module mechanisms). That files
are used to store your programs appears to be incidental. Therefore
using a file oriented system when programming something like Java is
painful, to say the least.

Thus, acme is very probably not the right editor, unless you are in
complete control of the code. But I would say the same holds for vi or
emacs. Its just that those two have had a lot of additions poured into
them that were inspired by the IDE world.

Acme is supremely fabulous when you are in complete control or if
you're programming using a language/environment where there are no
strange rules on where your files have to go (the underlying OO DB,
essentially).

On Wed, Aug 20, 2008 at 11:12 PM, Wendell xe yahoo.com> wrote:

I used to feel much the same. Then I went back to coding java at
work, fired up eclipse and was like "... where's my chording? :( :(".
I had to whip up a plumbing rule so I could button 3 stack traces...

On Wed, Aug 20, 2008 at 10:14 AM, sqweek gmail.com> wrote:

On Wed, Aug 20, 2008 at 7:42 PM, David Leimbach gmail.com> wrote:

Double click on the paren selects the area enclosed by the matching paren.

paurea@gmail.com (Gorka Guardiola) writes:

On Thu, Aug 21, 2008 at 2:06 AM, Paul Donnelly
sbcglobal.net>wrote:

On Thu, Aug 21, 2008 at 5:06 PM, Paul Donnelly
sbcglobal.net> wrote:

sqweek@gmail.com (sqweek) writes: