The well known Vi editor, and it’s evolved counter-part Vim editor are well known among the Linux community. Most of us use these editors when dealing with server configurations, etc., in our day-to-day work. But most of the users (including myself) use only a very small subset of the capabilities of this simple, yet extremely powerful editor. Even the most sophisticated IDEs out there today still do not feature many of the facilities that has been there with Vi and Vim editors for a long time.
However, to get the productivity out of Vim, it’s essential to know what it’s capable of, and use those when possible. You have to memorize the key combinations to get things done, and a one page quick reference sheet would be the ideal solution. So I created the attached quick reference sheet based on an article found at TuxRadar. Initially I made this for my personal use (it’s pasted on a wall of my cubicle), but thought of sharing this. So here it is, the Vim Quick Reference.
Note that this contains only a very small portion of what Vim is capable of. But I have found this quite handy when dealing with most of the needs.
Download Vim Quick Reference Sheet 1.1 [PDF]
The Java API, backed by the JVM provides tons of features and facilities to Java developers, which could be used to get things done easily for certain specific scenarios. However, these features are often overlooked by developers, mainly due to the lack of reading material and resources regarding these APIs. The purpose of this article series is to introduce such features of the JVM and Java API to intermediate Java developers.
Most of the content that will be discussed as part of this series may not be applicable for your day to day work, but knowing this will enable to you to utilize these to get things done simply, and elegantly.
As first part of the series, we will be looking at the Uncaught Exception Handler API of the JVM. Java uses (or in more specific terms, throws) exceptions to notify exceptional situations in programs. Developers write try-catch blocks to handle these exceptions, or simply propagate the exceptions upwards in the call stack. The uncaught exception handler allows developers to provide a code segment to be executed when an exception is propagated up the call stack, without being caught.This is helpful when we need to perform some operations when exceptions occur, such as in safety critical applications.