From: Robert Strandh on
Robert Uhl <eadmund42(a)NOSPAMgmail.com> writes:

> IIRC, doesn't the Climacs project wish to avoid the path of emacs and
> instead focus simply on being a text editor? This wouldn't really jive
> with Mr. Lord's desire for a general-purpose application framework...

In my opinion, Emacs provides a framework for applications simply
because no other such framework existed at the time. Now we have
CLIM/McCLIM, which does a great job supplying such a framework.
--
Robert Strandh

---------------------------------------------------------------------
Greenspun's Tenth Rule of Programming: any sufficiently complicated C
or Fortran program contains an ad hoc informally-specified bug-ridden
slow implementation of half of Common Lisp.
---------------------------------------------------------------------
From: Tim X on
Robert Uhl <eadmund42(a)NOSPAMgmail.com> writes:

> Christophe Rhodes <csr21(a)cam.ac.uk> writes:
>>
>> "Tom Lord" <lord(a)emf.net> writes:
>>
>>> An obvious thing is an improved lisp (performance, dialect, modules,
>>> threads). One side effect should be less code not written in lisp.
>>
>> If Common Lisp is an improved lisp from your point of view, can I
>> encourage you to look at the Climacs project?
>
> IIRC, doesn't the Climacs project wish to avoid the path of emacs and
> instead focus simply on being a text editor? This wouldn't really jive
> with Mr. Lord's desire for a general-purpose application framework...

I thought a big part of the aim of the project was to create an editor
which was able to take things like text highlighting to the 'next
level'. That is, instead of being restricted to working purely on a
regexp syntax level, start to be able to work on a semantic and
interpreted level to provide a more advanced environment able to give
the programmer more sophisticated support. Much of this can only be
achieved with an editor that has a lisp interpreter 'built-in".

Tim

--
tcross (at) rapttech dot com dot au
From: Xah Lee on
Folks,

Please consider this, and talk to emacs developers about it.

If emacs do these things, perhaps emacs's user base will increase 5
fold in the next couple of years. Emacs oldtimers and elisp hackers
wouldn't have to change their working habits a bit. And, the increased
user base will be tremendous help in the continued emacs development
and growth.

Xah
xah(a)xahlee.org
∑ http://xahlee.org/


Xah Lee wrote:
> Things emacs need to change for modern world:
>
> * Change the keyboard shortcut of Copy & Paste to meta-C and meta-V
> as to be the same with all modern applications.
> * Change the undo behavior so that there is a Undo and Redo, as the
> same with all modern applications.
> * Get rid of the *scratch* buffer.
> * Make longlines-mode the default editor behavior for any file.
>
> Things emacs should do now, even though it eventually will do.
>
> * When opening a HTML document, automatically provide highlighting
> of HTML, CSS, and Javascript codes. Similarly for other multi-language
> files such as PHP, JSP, et al. This behavior must be automatic without
> requiring user to customize emacs.
>
> Possible Documentation Change Proposals
>
> * Reduce the use of the word “buffer” in the emacs
> documentation. Call it “opened file” or “unsaved document”.
> * Switch the terminology of Window and Frame so it is more
> standard. That is, Emacs's “Window” should be called Panes or
> Frames. While Emacs's “Frame” should be termed Window.
> * Change the terminology of keybinding to “keyboard shortcut”
> in emacs documentation. Use the term keybinding or binding only in a
> technical context, such as in elisp documentation.

From: Greg Menke on

Why should we "consider" this when setting up your idiosyncratic
preferences is a trivial matter of modifying your own .emacs file?

And where is the data to back up your "5 fold" increase?

Gregm


"Xah Lee" <xah(a)xahlee.org> writes:

> Folks,
>
> Please consider this, and talk to emacs developers about it.
>
> If emacs do these things, perhaps emacs's user base will increase 5
> fold in the next couple of years. Emacs oldtimers and elisp hackers
> wouldn't have to change their working habits a bit. And, the increased
> user base will be tremendous help in the continued emacs development
> and growth.
>
> Xah
> xah(a)xahlee.org
> ? http://xahlee.org/
>
>
> Xah Lee wrote:
> > Things emacs need to change for modern world:
> >
> > * Change the keyboard shortcut of Copy & Paste to meta-C and meta-V
> > as to be the same with all modern applications.
> > * Change the undo behavior so that there is a Undo and Redo, as the
> > same with all modern applications.
> > * Get rid of the *scratch* buffer.
> > * Make longlines-mode the default editor behavior for any file.
> >
> > Things emacs should do now, even though it eventually will do.
> >
> > * When opening a HTML document, automatically provide highlighting
> > of HTML, CSS, and Javascript codes. Similarly for other multi-language
> > files such as PHP, JSP, et al. This behavior must be automatic without
> > requiring user to customize emacs.
> >
> > Possible Documentation Change Proposals
> >
> > * Reduce the use of the word ?buffer? in the emacs
> > documentation. Call it ?opened file? or ?unsaved document?.
> > * Switch the terminology of Window and Frame so it is more
> > standard. That is, Emacs's ?Window? should be called Panes or
> > Frames. While Emacs's ?Frame? should be termed Window.
> > * Change the terminology of keybinding to ?keyboard shortcut?
> > in emacs documentation. Use the term keybinding or binding only in a
> > technical context, such as in elisp documentation.
From: Rob Thorpe on
Greg Menke wrote:
> Why should we "consider" this when setting up your idiosyncratic
> preferences is a trivial matter of modifying your own .emacs file?

The problem is the default themselves being inappropriate. An
experienced user can easily change the default once they are
experienced. The problem is the unusable defaults presented to the new
user, who by virtue of being a beginner is unable to change them.

In this I agree with Xah, though I disagree with some of the things he
thinks need changing.

> And where is the data to back up your "5 fold" increase?

I don't think it would help that much either.