Re: Issues with emacs

["Pascal J. Bourguignon" <pjb@informatimago.com>]

rusi <rustompmody@gmail.com> writes:

> On Jun 18, 7:32 am, S Boucher <st...@yahoo.com> wrote:
>> I've been using emacs since as far back as 18.59.  Still use it daily.
>>
>> However, I often wonder where Emacs is heading.
>
> Ive been collecting some posts on this list that seemingly are
> questions about emacs but in fact point to deficiencies. Does one,
> two, hundred deficiencies make for a 'dying breed?'  Perhaps not and
> the question of S Boucher needs to be dealt with more conceptually/
> philosophically.  Unfortunately such a discussion invariably
> degenerates into flaming/trolling.  So heres my bottom up list


Some are contradictory.  Eg. reproaching lisp-2 and wanting more CL
support (of course, they're not made by the same people).

lisp-2 is a good thing IMO.  
http://www.nhplace.com/kent/Papers/Technical-Issues.html


What's bad, is that the promise of having different embedded languages
in emacs failed so far.  IMO because of lack of lexical binding/closures
(but this is resolved in emacs-24), and to a lesser degree, lack of a
usable namespace system (in this case, the obarray mechanism is there to
be used by language implementors).  But with emacs-24, it could be
possible to implement a scheme, a javascript and finish the emacs-cl
implementation, java, etc, so that people could use and program emacs in
their favorite programming language.



> * Intro
>   Started [2011-01-08 Sat] Idea is to keep a record of emacs mailing
>   list queries that are really emacs problems
> * Problems
> *** No package management
>     http://lists.gnu.org/archive/html/help-gnu-emacs/2011-01/msg00293.html
> *** Low grade dependency management in elisp
>     http://groups.google.com/group/gnu.emacs.help/browse_thread/thread/1070abe0f19e5476#
>     (change to other mailinglist)
> *** CL badly integrated
>     http://lists.gnu.org/archive/html/help-gnu-emacs/2011-01/msg00288.html
> *** Horizontal scrolling
>     http://groups.google.com/group/gnu.emacs.help/browse_thread/thread/686c0fa47a48a7e2#
> *** elisp is a lisp-2
>     http://lists.gnu.org/archive/html/help-gnu-emacs/2011-01/msg00270.html
> *** Poor customizability of Tabstop behavior
>     http://lists.gnu.org/archive/html/help-gnu-emacs/2011-01/msg00043.html
> *** JDE does not work
>     http://lists.gnu.org/archive/html/help-gnu-emacs/2010-12/msg03183.html
> *** Poor Project Management
>     http://lists.gnu.org/archive/html/help-gnu-emacs/2010-12/msg02878.html
> *** Half baked server
>     http://groups.google.com/group/gnu.emacs.help/browse_thread/thread/f1c59047b8f4b294#
> *** Spurious choices
> ***** email
>       http://lists.gnu.org/archive/html/help-gnu-emacs/2010-12/msg03080.html
> ***** folding
>       http://lists.gnu.org/archive/html/help-gnu-emacs/2010-12/msg02939.html
> ***** Template
> ***** Python
>       http://lists.gnu.org/archive/html/help-gnu-emacs/2010-12/msg02534.html
> ***** merge/diff
>       http://groups.google.com/group/gnu.emacs.help/browse_thread/thread/819655b0b5a81bba#
> *** Obsolete
> ***** read-from-minibuffer vs read-string
>       http://groups.google.com/group/gnu.emacs.help/browse_thread/thread/5925179885835e1d#

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.