News for hackers. Stuff that matters.
Re:Bzr is dying; Emacs needs to move by bachback on Thursday January 02, 2014 @07:27AM (#6999293)
wow.

please, please, you Emacs/LISP gurus out there: make a working modern package manager and integrate the browser like lighttable does. and perhaps rewrite emacs from scratch so that the source code makes sense in today's world not in 1980's world.

unfortunately lighttable is staying closed for much too long, but something like it is desperately needed.

Re:Bzr is dying; Emacs needs to move by davexunit on Thursday January 02, 2014 @08:28AM (#6999465)
>make a working modern package manager

package.el works great.

>integrate the browser

That may actually be possible in the future, see http://www.emacswiki.org/emacs/EmacsXWidgets

>perhaps rewrite emacs from scratch

That is just silly. The current Elisp interpreter might be replaced with an Elisp implementation on top of the Guile VM. That would be quite the big upgrade, technically speaking.

>unfortunately lighttable is staying closed for much too long

I agree, I don't have much faith in the "it will be free eventually, just trust us" development model. If the project really wanted to be community friendly then the source code would have been free from the beginning.

Re:Bzr is dying; Emacs needs to move by sixthloginorso on Thursday January 02, 2014 @09:17AM (#6999639)
This XWidgets project for Emacs has a rather unfortunate name, given that there is already a well-known GUI toolkit named wxWidgets.
Re:Bzr is dying; Emacs needs to move by __david__ on Thursday January 02, 2014 @02:41PM (#7001731)
> make a working modern package manager

    M-x packages-list-packages
> and integrate the browser like lighttable does.

    M-x eww
> and perhaps rewrite emacs from scratch

Would you like a pony, too?

> so that the source code makes sense in today's world not in 1980's world.

I've actually found that Emacs's source it very readable (even the C lisp engine stuff). Do you object to the lisp or to the C?

Re:Bzr is dying; Emacs needs to move by tobiasu on Thursday January 02, 2014 @07:42AM (#6999343)
The command preceding this outburst was:

$ sudo braindump bachback.core|tail

;-)

Re:Bzr is dying; Emacs needs to move by bachback on Thursday January 02, 2014 @08:21AM (#6999444)
haha. I've actually spend time trying to read emacs's source code. I guess the downvoters haven't.
Re:Bzr is dying; Emacs needs to move by ElliotH on Thursday January 02, 2014 @08:26AM (#6999459)
Emacs has a package manager, it works fine. I particularly like that I can script it to install my packages on first run.
Re:Bzr is dying; Emacs needs to move by bachback on Thursday January 02, 2014 @08:34AM (#6999483)
works fine = work fine for me after I have spend x hours looking around the net, writing elisp myself. that's the whole problem with lisp. it is not communal, because it does not enforce standards.
Re:Bzr is dying; Emacs needs to move by davexunit on Thursday January 02, 2014 @09:07AM (#6999603)
(package-initialize)

Wow, now you have access to the package manager.

Emacs is meant to be customized heavily by its users and the language to do so is Elisp. If you are afraid of that then I don't know what to tell you.

You are quick to condemn all Lisps with an assertion that doesn't make sense to me.

Re:Bzr is dying; Emacs needs to move by sixthloginorso on Thursday January 02, 2014 @09:11AM (#6999623)
I don't understand, what's wrong with package-list-packages? It has concise descriptions, MELPA is kept very well updated, and and installing plugins is a breeze, no elisp configuration is necessary for like 90% of the packages you install.
Re:Bzr is dying; Emacs needs to move by ElliotH on Thursday January 02, 2014 @09:05AM (#6999600)
M-x package-refresh-contents

M-x package-install

<package name>

That's with a blank .emacs file on Emacs 24 on a brand new user account I created just to test that for you.

EDIT: (ofc the auto-installing my favourite packages stuff is elisp I wrote)

Re:Bzr is dying; Emacs needs to move by filipncs on Thursday January 02, 2014 @08:01AM (#6999390)
Rumor has it that LightTable will be open sourced very soon, but I doubt it will ever take the place of Emacs.
Re:Bzr is dying; Emacs needs to move by agumonkey on Thursday January 02, 2014 @08:50AM (#6999540)
I doubt it will too, but I hope it gets a nice "marketshare" so people try to experiment and find new ideas. Emacs will probably benefit a lot from cross-pollinisation too (it excels at absorbing new ideas).
Re:Bzr is dying; Emacs needs to move by rmrfrmrf on Thursday January 02, 2014 @08:54AM (#6999562)
LightTable is truly terrible. Adobe beat that team with Brackets without even really trying, and all of the gimmicks it promised have been available in vim and subl for a while. They should do something else with their time.
Re:Bzr is dying; Emacs needs to move by bachback on Thursday January 02, 2014 @09:58AM (#6999810)
not true at all. it has this thing called the browser in it, as well as a completely live hooks and a modular system. this here http://www.youtube.com/watch?v=gtXpOD6jFls is impossible in any other editor.
Re:Bzr is dying; Emacs needs to move by rbanffy on Thursday January 02, 2014 @09:11AM (#6999620)
> rewrite emacs from scratch

You obviously have no idea of how huge undertaking would this be. You are free to write your new editor and call it Fnbdt.

Re:Bzr is dying; Emacs needs to move by swah on Thursday January 02, 2014 @07:52AM (#6999375)
I agree - Emacs has to be rewritten on top of a modern rendering engine!
Re:Bzr is dying; Emacs needs to move by saalweachter on Thursday January 02, 2014 @08:34AM (#6999488)
They did. It is called 'Eclipse'.
Re:Bzr is dying; Emacs needs to move by sixthloginorso on Thursday January 02, 2014 @09:13AM (#6999628)
Just not the same. Adding functionality to Eclipse is a "project". In Emacs, it's just some code and an eval-last-sexp away.
Re:Bzr is dying; Emacs needs to move by rbanffy on Thursday January 02, 2014 @09:09AM (#6999613)
Then do it.
Re:Bzr is dying; Emacs needs to move by swah on Wednesday January 08, 2014 @06:49PM (#7027731)
How do you understand something like Webkit? Its so huge.