The code of
El-Get has been pretty stable for a long time now. About the
whole set of patches against the
4.x series has been about bug fixing corner
cases (sometimes cases that had nothing
cornery about them too) and
providing more and more recipes. That's what you expect from a
software, and that what allows us to move to a
rolling releases model.
Yes it did happen, for real, in London: the Emacs Conference. It was easter week-end. Yet the conference managed to have more than 60 people meet together and spend a full day talking about Emacs. If you weren't there, a live stream was available and soon enough (wait for about two weeks) the video material will be published, as sacha is working on it.
I've discovered recently another Emacs facility that I since then use
several times a day, and I wonder how I did without it before:
the command mark-sexp.
I've been asked about how to integrate the ack tool (you know, the one that is better than grep) into Emacs today. Again. And I just realized that I didn't blog about my solution. That might explain why I keep getting asked about it after all...
Please welcome the new stable version of
El-Get, the much awaited
4.1 has now been branched for your pleasure. It's packed with lots of
features to make your life easy, comes with a
Info documentation book and
even has a
logo. That's no joke, I found one, at least:
A friend of mine just asked me for advice to tweak some Emacs features, and I think that's really typical of using Emacs: rather than getting used to the way things are shipped to you, when using Emacs, you start wanting to adapt the tools to the way you want things to be working instead. And you can call that the awesome!
J'ai eu la chance hier soir de participer à la Battle Language à la Marmite, où j'avais proposé de parler de Emacs Lisp, proposition qui s'est transformée en porte-étendard de la grande famille Lisp. J'ai utilisé avec plaisir certains contenu de Lisperati dans ma présentation et je vous recommande le détour sur ce site !
el-get project releases its new stable version,
3.1. This new release
fixes bugs, add a host of new recipes (we have 420 of them and counting) and
some nice new features too. You really want to upgrade.
From the first days of el-get is was quite clear for me that we would reach a point where users would want a nice listing including descriptions of the packages, and a major mode allowing you to select packages to install, remove and update. It was also quite clear that I was not much interested into doing it myself, even if I would appreciate having it done.
Emacs we get to manage a larger and larger setup file (either
~/.emacs.d/init.el), sometime with lots of dependencies, and some
sub-files thanks to the
load function or the
Emacs comes with a pretty good implementation of a terminal emulator,
term. Well not that good actually, but given what I use it for, it's just
what I need. Particulary if you add to that my
cssh tool, so that
ssh to a remote host is just a
=C-= runs the command
cssh-term-remote-open away, and completes on the host name thanks to
I stumbled upon the following
cheat sheet for
Emacs yesterday, and it's
worth sharing. I already learnt or discovered again some nice default
chords, like for example
C-x C-o runs the command delete-blank-lines and
C-M-o runs the command split-line. I guess I will use the later one a lot.
blog article, you're shown a quite long function that loop through
your buffers to find out if any of them is associated with a file whose full
"projects". Well, you should not be afraid of using
Current el-get status is stable, ready for daily use and packed with extra features that make life easier. There are some more things we could do, as always, but they will be about smoothing things further.
It so happens that a colleague of mine wanted to start using Emacs but couldn't get to it. He insists on having proper color themes in all applications and some sensible defaults full of nifty add-ons everywhere, and didn't want to have to learn that much about Emacs and Emacs Lisp to get started. I'm not even sure that he will Take the Emacs tour.
Yes, you read it well,
recipes, and is now
1.1 release. The reason for this release is mainly that I have
two big chunks of code to review and the current code has been very stable
for awhile. It seems better to do a release with the stable code that exists
now before to shake it this much. If you're wondering when to jump in the
water and switch to using
el-get, now is a pretty good time.
It's been a week since the last commits in the
el-get repository, and those
were all about fixing and adding recipes, and about notifications. Nothing
core plumbing you see. Also,
0.9 was released on
2010-08-24 and felt
pretty complete already, then received lots of improvements. It's high time
to cross the line and call it
I wanted to play with the idea of using the whole keyboard for my
switch-window utility, but wondered how to get those keys in the right order
and all. Finally found
quail-keyboard-layout which seems to exists for such
uses, as you can see:
Yes, that's another
el-get related entry. It seems to take a lot of my
attention these days. After having setup the
git repository so that you can
el-get from within itself (so that it's
self-contained), the next
logical step is providing
After discovering the excellent
Gwene service, which allows you to subscribe
newsgroups to read
RSS content (
commits, etc), I came to
read this nice article about
Happy Numbers. That's a little problem that
fits well an interview style question, so I first solved it yesterday
Emacs Lisp as that's the language I use the most those days.
A very good remark from some users: installing and managing
el-get should be
simpler. They wanted both an easy install of the thing, and a way to be able
to manage it afterwards (like, update the local copy against the
authoritative source). So I decided it was high time for getting the code
out of my
~/.emacs.d git repository and up to a public place:
I've been receiving some requests for
el-get, some of them even included a
patch. So now there's support for
http-tar, augmenting the
existing support for
Thanks to you readers of Planet Emacsen taking the time to try those pieces of emacs lisp found in my blog, and also the time to comment on them, some bugs have been fixed, and new releases appeared.
I've been using emacs for a long time, and a long time it took me to consider learning Emacs Lisp. Before that, I didn't trust my level of understanding enough to be comfortable in managing my setup efficiently.
Thanks to amazing readers of
planet emacsen, two annoyances of
switch-window.el have already been fixed! The first is that handling of
isn't exactly an option after all, and the other is that you want to avoid
the buffer creation in the simple cases (1 or 2 windows only), because it's
the usual case.
So it's Sunday and I'm thinking I'll get into
el-get sometime later. Now is
the time to present
dim-switch-window.el which implements a
C-x o. I
know of only one way to present a
visual effect, and that's with a screenshot:
Now you know what piece of software is used to publish this blog. I really
like it, the major mode makes it a great experience to be using this tool,
and the fact that you produce the
rsync it all from within Emacs
C-c C-p then
C-c C-r with some easy
elisp code) is a big advantage as far
as I'm concerned. No need to resort to
At pgday there was this form you could fill to give speakers some feedback about their talks. And that's a really nice way as a speaker to know what to improve. And as Magnus was searching a nice looking chart facility in python and I spoke about matplotlib, it felt like having to publish something.
As you might have noticed, this little blog of mine is not compromising much
and entirely maintained from Emacs. Until today, I had to resort to
upload my publications, though, as I've been too lazy to hack up the tools
integration for simply doing a single
rsync command line. That was one time
So you have a
rolodex like database in your Emacs, or you have this phone
number in a mail and you want to call it. It happens you have
VoIP setup and
Twinkle to make your calls. Maybe you'll then find this
The function didn't allow for using more than one
mailrc file, which isn't a
good idea, so I've just added that. Oh and for
gnus integration what I need
(add-hook 'message-mode-hook 'mail-abbrevs-setup) it seems... so that if
I type the alias it'll get automatically expanded. And to be real lazy and
avoid having to type in the entire alias,
mail-abbrev-complete-alias to the
rescue, assigned to some easy to reach keys.
So I've been adviced to use
~/.mailrc for keeping a basic address book in
Emacs, for use within
gnus for example. I had to resort to the manual to
find out how to use the file aliases when I need them, that is when
composing a mail. For the record, here's what I had to do:
First, here's a way to insert at current position the last message printed
into the minibuffer... well not exactly, in
*Messages* buffer in fact. I was
tired of doing it myself after invoking, e.g.,
So finaly a blogging software for geeks exists?