Re: [Gnome-devtools] Emacs

["Masatake YAMATO" <masata-y is aist-nara ac jp>]

Thank you for your answers.

al584493 mail mty itesm mx:
> another main anti-emacs reason is that, normal coders, dont want to use 
> emacs, are afraid of emacs, and dont have the time for emacs, they just 
> dont belive in the advantages of emacs. Some of them are are afraid of 
> Visual Bashit (I would hehehehehe). They need something simpler, 
> something they can learn to use in 2 minutes.

I see. But above reason is not interested to me.
What I want to know is that anti-emacs reason of people who knows the
advantages of emacs:)

Chris Phelps wrote:
> Here is my list of reasons for making CodeCommander:
> 
> 1. No good GTK based editors for anything other than html and C (I
> started before gnomacs project)
gnomacs project? 
Emacs based on gtk/gdk?

> 2. I find the Emacs buffer system to be ugly and a pain in the ass.
I'd like to know this item more.

> 3. Emacs is huge (both in disk and ram size)
Yes but, now we can get larger size disk and ram. 
If I can use really intelligent editor, I'll pay for disk and ram.
I use my computer for writing programs, so if I lack disk and ram 
space, I'll remove gnome first. If one uses ones computer for other
than writing programs, one will remove emacs before remove gnome.

> 4. I find elisp to be ugly and a pain in the ass.
I see. I love sexp, but I know someone hate it.

> 5. I needed *something* to do.
:)

Mark wrote:
> I'm part of the gtkeditor project so I will comment breifly. My
> motivation is taking editing far beyond that of programs like emacs. 
Very interesting. You know how to use high performance CPU.

> I
> don't use emacs, but as I understand it uses regular expessions, scripts
> (elisp), and bindings as a method of extending it to handle different
> languages. These features alone have proven to be very powerful. 
Yes!

> What I
> hope to acomplish in the future is an editor that truely knows about the
> language (syntax and semantics), that can point out errors in the
> program structure before compilation (saving a lot of time), can assist
> in writing code through knowledge of how the program should look (pretty
> printing) and how it could look (completions, and hints).
Very interesting. But at last I think you will implement gcc on the
top of gtkeditor:) But I wonder why you don't implementat such interesting
features on the top of Emacs? 

I think gtkeditor is not good name for such a big project.
At first time I see the project name "gtkeditor", I assume that
gtkeditor is a new widget like gtkbutton, gtklabel, gtkmenu.

See
http://gnome.dti.ad.jp/mailing-lists/archives/gtk-list/2000-February/0454.shtml

I like Emacs because it provides LAZY integrated development
environment.  I can control many other programs(gdb, gcc, shell...) 
with Emacs.  Different from other IDE, Emacs doesn't force using GUI
on its user.  Further more, gtk-emacs will provide GUI option.

Masatake