My blog syndicates its new contents through an Atom feed so that people can subscribe to updates. And according to the server logs, people use them (that was the initial point of having them; so, thanks!). However, it wasn’t until recently that I actually read the standard and a few other online sources, when I discovered that a few things, such as the entry identifiers, have been done wrong all this time. I’m documenting these issues publicly in order to save for future reference.
It is too easy to star a project on GitHub, maybe because you consider it is a fun experiment or because it actually matters to you. However, keeping track about updates (say about repositories your project depends on), is harder. You can watch a repo, but then you’ll also be subscribed to all the clutter that sometimes issues and PRs cause.
Sibbell is a service that, once connected to your GitHub account, will sync your starred repos, and then, it will automatically check for new releases or tags on those repositories. Whenever one of your starred repositories gets a new release, you’ll receive a notification on your e-mail.
Free tier allows you to receive updates on your starred repositories as they happen; paid tier allows you to digest those updates into a single mail per day or week, and disable starred repositories you are not interested in knowing about.
Here is another quick one that is also easy to forget. One of the many uses of SSH is local and remote port forwarding. Using local port forwarding, you can set up a socket between a port in your local machine and your SSH server. Whenever a communication is established on that local port, it will be forwarded to the server and then, made. This has some interesting use cases, such as connecting to local services (web administration panels, databases…) or acting as a jump server or just a proxy server.
Rustup recently reached v1.0.0. Rustup is a toolchain installer and manager, allowing to install multiple toolchains: stable, beta, nightly, or a particular version. It is very easy and convenient instead of other solutions that rely on manually installing packages. It just became a core project of Rust as well. The download page at Rust website has been updated to reflect this. In fact, Multirust, a similar project for managing multiple Rust installations, is now deprecated.
Llueve, así que si Dani no sale a correr, correr sale a Dani. Cinta de correr + portátil = win. Arriesgado, un poco estúpido, pero funciona 🌧🏃
I've been recently working on recovering posts from old blogs that were stored in my local backup, where they have been rotting for a lot of years. Those blog posts were made in WordPress and Blogger, and therefore had to be migrated into Jekyll. The experience has not been as bad as I thought it would be, althought there have been a few issues that I had to come through.
Previously I told you about Racer, an autocompletion tool for Rust that integrates nicely into many other editors. Today I’d like to talk to you about how to configure Rust autocompletion in Vim using Racer and some plugins. Please note that you need
racerinstalled before proceeding. Check out that blog post if you need some help.
On my previous blog post I wrote about how to install Racer. Today I’ll show you how you can enable autocompletion for Rust code you write on Visual Studio Code, the open source editor made by Microsoft that works on Windows, Linux and MacOS X, that can be extended via plugins.
Racer is an awesome program for enabling autocomplete for your Rust code. Rust is one of the most awesome languages I have seen. Its standard library is very impressive and the crates help extending the platform to do lots of things. However, having autocomplete comes useful for making things easier to write as you can see the functions and classes inside your editor as you are writing.