nic-ferrier

9 ms·

61.
by nic-ferrier 14y ago
this is really neat. what would be cool is to keep the package list up to date automatically (possibly by advising package installation - https://github.com/nicferrier/emacs-package-store/blob/maste... ). Then everytime you installed a pac
62.
by nic-ferrier 14y ago
But we're not talking about that, as I said elsewhere, MELPA can have quite strict requirements (only the people allowed to commit to the github project of a repo can make a change, seems fair enough) and marmalade is aiming towards digital
63.
by nic-ferrier 14y ago
Of course this is true. But it's also true of everything. APT, YUM, GEM, PYPI, anything where there is contributed code and you can't take legal action against someone. Emacs is no different.
64.
by nic-ferrier 14y ago
As I've said elsewhere, we will sort this out in the end. Right now MELPA tends to be the latest and greatest and marmalade is more stable (read 'less exciting') releases. It would be good to have this recognized per-package though so hopef
65.
by nic-ferrier 14y ago
You're right. I have renamed the article "Packages for Emacs Programmers"
66.
by nic-ferrier 14y ago
Again, that's why we want to add signatures to packages. This is probably always going to be a two tier system though (some people are likely to not add a signature). There are other possible security systems as well, like MELPA could use g
67.
by nic-ferrier 14y ago
The guys who run MELPA and me (I run marmalade) are talking and we hope that there can be just one repo in the end. It may take us a while to combine the best parts of the 2 systems in the right way.
68.
by nic-ferrier 14y ago
el-get is pretty cool but I think package has the following advantages over el-get: 1) it's standard emacs 2) although it doesn't have yet it will be able to support digital signatures for packages (as well as other security mechanisms) As
69.
by nic-ferrier 14y ago
My init file is now much much simpler. It's easier to use customization once you're using packages. Package quality is also better than the old "install this file in your load-path somewhere" because there are established ways of doing stuf
70.
Emacs packages for programmers(nic.ferrier.me.uk)
80 points by nic-ferrier 14y ago|28 comments
71.
Learn shell by example - a tutorial through a very simple shell script hack (nic.ferrier.me.uk)
1 points by nic-ferrier 15y ago|0 comments
72.
by nic-ferrier 15y ago
I read this yesterday, it's a really great tutorial. It should be added to the emacs wiki as a learning resource.
73.
by nic-ferrier 15y ago
that's just one plan. a lot of emacs people think that's a good plan, a lot of emacs people think that's a bad plan. I'm in the latter camp and prefer CommonLisp. But, hey, whatever works.
74.
by nic-ferrier 15y ago
I think that should be the aim for any tool conference, to help new users get a leg up and to help existing users move it forwards. Same for Emacs. The great thing about Emacs is that it's so big and versatile everyone can learn something n
75.
by nic-ferrier 15y ago
I'd love to hear tromey talk about his plans to rebase emacs in CL: http://tromey.com/blog/?p=709
76.
by nic-ferrier 15y ago
the organizer says he is collecting interest right now. Once he's gauged the level it will be decided when and where.
77.
An Emacs conference(emacsconf.herokuapp.com)
234 points by nic-ferrier 15y ago|44 comments
78.
Emacs lisp continuous delivery(nic.ferrier.me.uk)
10 points by nic-ferrier 15y ago|0 comments