Vim

Just discovered "vidir" , a way to manipulate filenames inside your favorite text editor (better known as Vim).

Previously, I would use complex and cumbersome BASH constructs using "for;do;done", "sed", "awk" etc., coupled with the operation itself:

I love Vim! It is so easy enough to edit a remote file with my local Vim through the Secure Copy protocol:

Description

Buffersaurus is a Vim plugin for searching and indexing the contents of buffers for regular expression patterns or collections of regular expression patterns. Results are displayed in separate buffer, and can be (optionally) viewed with user-specifiable lines of context (i.e., a number of lines before and/or after the line matching the search pattern) or filtered for specific patterns.

Global commands provided include (among others):

I am afraid that in practice I have always ended up going the simple "litter the code with print statements" route when debugging my Python. Without the compilation step, the cost of inserting and then removing these lines from the source code is relatively cheap, and has served me well enough so far. Thus, as sanctioned under the "if it is not broken, don't fix it" clause, I have not felt the need to look any further, or look into learning how to use pdb.

The Python 2 and 3 standard library documentation can be installed as Vim help files through installation of the following:

• Python 2.x: http://www.vim.org/scripts/script.php?script_id=3277
• Python 3.x: http://www.vim.org/scripts/script.php?script_id=3278

Installation:

Git offers two ways of viewing differences between commits, or between commits and your working tree: diff and difftool. The first of these, by default, dumps the results to the standard output. This mode of presentation is great for quick summaries of small sets of changes, but is a little cumbersome if there are a large number of changes between the two commits being compared and/or you want to closely exa

The Great Controversy

A standard dictum amongst experienced Vim users is not to use the arrow keys to move around your document. This dictum is often repeated again and again, in tones that range from the taken-for-granted to hysterical-zeal. The most common reason given for this is that using the arrow keys takes your hands away from the home row of your keyboard, and thus is wasteful both in terms of time and energy, whereas the standard Vim movement keys --- `h`, `j`, `k`, and `l` --- keep your hands on the home row, and therefore is far more efficient. Here is what I have discovered: this anti-arrow key argument is wrong!

Let:

$\mathbf{P} = \{i \mid i \in \text{people}\}$.

Let:

$\mathbf{V} = \{i \mid i : \text{use Vim to write LaTeX documents}, i \in \mathbf{P}\}$.

Let:

$\mathbf{L} = \{i \mid i : \text{memorized all LaTeX commands}, i \in \mathbf{P} \}$.

If you are $\in \mathbf{V} \cap \mathbf{L}$, then this post is not for you. But you are probably not, as $\mathbf{L} = \emptyset$, and hence $\mathbf{V} \cap \mathbf{L} = \emptyset$. But if you are $\in \mathbf{V} \cap \mathbf{L}^c$, as I am, then you might be interested in the following ...