Since the last official release, there’s been a lot of work on the Identica-mode for Emacs. Its been a while since the last release and probably most users have been using the development version directly from the Git repository. Even though I try to make the development branch as stable as possible, official releases give some users more confidence and ditributions (like Arch, so far I know of) can name their packages with some versioning reference.
Added icons to indicate if automatic timeline updates are on or off
Can now delete notices
Added option to show timeline in reverse order (newest at the bottom)
Added support to recognize ur1.ca urls without the “http://” part (some clients like Choqok use this syntax)
Added support to recognize unicode urls
Added option to limit number of dents in timeline
Removed dependency on cURL to shorten URLs with ur1.ca
and many bug fixes
I hope you enjoy using identica-mode as much as I do. I’d also like to share my joy of developing and improving it as well, so if you have any ideas or code contributions, please use the project’s Savannah page.
Any donations to support the development of this project are very much appreciated. Thank you for using, contributing or supporting Emacs Identica-mode.
The backend that makes the HTTP connections has been completely rewritten to use url.el mode instead of the previous networking calls. This has made a big improvement on speed and reliability. Emacs no longer hangs for a while on crappy or slow connections.
Now you can follow group and tag timelines, pressing C-c C-g for group timeline and C-c C-t for tag timeline. Also, pressing while the cursor is on a tag, username or group it will switch to that element’s timeline.
– Added support for unicode named tags and groups
Basically you’ll notice a speed and stability improvement overall.
You can also help out if you’ve liked Emacs identica-mode and have some spare change. It would be great to support this project by making any kind of donation on the “tip jar” in appreciation of the hours invested on its development and improvement.
The emacs personalization file (dotemacs) is a very important resource for every Emacs user. Typically found at ~/.emacs, this file contains elisp code all the personalization of Emacs to accommodate each user. Its so important that it basically represents your Emacs “personality”.
To loose your .emacs file can mean loosing a lot of hours of tweaking and personalizing GNU Emacs through a bunch of collected-through-time snippets. So, being a very valuable asset, having a good method to back it up is a must have.
Here are 3 common methods people use to keep their Emacs file safe:
The most simple thing to do is to manually make copies of the file on a different directory, another partition on the same hard drive, an external hard drive, or a USB key. Also works well when having multiple computers and copying the same .emacs file on each of them. Using rsync to back it up periodically is a good idea, and it can be used to backup all your other elisp code for common modes (typically at ~/.emacs.d/) you use too.
A good option would be to back it up to an online storage service like Drop.io or even Amazon S3.
The standard and most common way to store your emacs customizations is by saving them on a file named .emacs placed on your home folder. But this is difficult to setup on a version control system since version control systems check things under directories. So this would mean you would be version controlling your whole home folder, which wouldn’t be a bad idea on some cases but on others would be a mess to maintain.
Fortunately there’s another way: at startup, Emacs also looks for a file called init.el on a hidden folder named .emacs.d/ in your home folder when the typical ~/.emacs file is not found. This way, you can easily set your preferred version control system to track changes on that folder. This has the advantage that any other Emacs modes or code you have can be stored and tracked too. This way, whenever you have a clean install, your Emacs setup and modes are just a checkout away from getting done.
On some setups, tracking changes on the whole ~/.emacs.d/ directory may not be a good option. So, to track changes on only your .emacs file can be achieved by moving your init.el file to a folder inside the home elisp directory and will look like this: ~/.emacs.d/dotemacs/init.el and make a symbolic link to it in ~/.emacs.d/ This way I can version control the “dotemacs” directory very easily.
Distributed version control
Many people use SVN as their preferred version control system, which backs up your data into a central location. But using a distributed version control system like Git, Mercurial or Bazaar is a better option. DVCSs let you setup multiple locations where to backup your code repository, so you don’t have a single point of failure. So you can version control your dotemacs file and back up the changes history on many places like Github, Gitorious, Launchpad or any other code hosting service, plus several other remote locations like multiple machines, a NAS or external drives with complete history of your changes.
Do you know other methods? How do you keep from loosing your dotemacs file?
Emacs identica-mode, a way to read and post to Identi.ca microblogging site and any Laconi.ca installation from Emacs, now has support for several (friends, replies, public and user) timelines. Also added support to send direct messages.
Some of the changes are:
All API calls are now through HTTPS
Changed keybinding, pressing “g” on identica-mode buffer now refreshes the buffer.
New keybinding “C-c C-r” switches to retrieve replies timeline.
New keybinding “C-c C-f” switches to retrieve friends timeline (default).
New keybinding “C-c C-d” sends direct message to a given user.
New keybinding “C-c C-g” switches to retrieve public timeline.
New keybinding “C-c C-u” switches to retrieve user (self) timeline.
Emacs modeline shows which timeline is currently being retrieved on identica-mode buffer.
Its been a while since my last release of identica-mode. This time, rather than publishing frequent but small updates, I waited to release a bunch of new features.
I’ve been looking for ways to blog from Emacs and so far my best solution has been to use weblogger.el. This mode supports many blogging platforms through the xmlrpc apis for blogger, metaweblog, livejournal and movable type. For more details about this mode, visit the emacswiki page.
Since this blog is based on WordPress and it supports the metaweblog api, this has worked very well. My only complaint was that since WordPress version 2.6, tag support was added and blogging from Emacs left my posts without tags. So I decided to add the tags support using the mt_keywords method on the metaweblog api, which on WordPress maps to the post tags. All you have to do is add the Summary label on the post header and write down the tags separated by commas.