This allows me to specify the destination folder if the link name
doesn't need to be changed, i.e., if I want to install
vim/ftplugin/ruby.vim, I no longer need to specify the following line:
lnfile vim/ftplugin/ruby.vim ~/.vim/ftplugin/ruby
Instead, I can simply give the destination folder, just terminate it
with a slash character as follows:
lnfile vim/ftplugin/ruby.vim ~/.vim/ftplugin/
There is a possibility that for every 0.1 stardates (8640 seconds),
the final 0.05 stardate would get rounded up (432 seconds). This kind
of inaccuracy is unacceptable by Starfleet standards, so I've reduced
the inaccuracy to 5e-10 stardates or 43.2 microseconds.
This moves from a one-size-fits-all approach for tab expansion to
dictating a default expansion scheme and a per filetype scheme. The
current plugin has custom schemes for Ruby and Makefiles.
Instead of using <ESC>i to get out of insert mode and reenter it at
the closing bracket, Vim accepts the use of <Left> to move the cursor
left without leaving insert mode. This allows undo and repeats to work.
With Ruby version 1.8.5, the smartwd script would abort with an error that
the shift method would take no arguments. Therefore, I have restricted the
use of the script to ruby version 1.8.7 and above.
On older versions, it will simply behave the same as \w in PS1 of bash.
Console uses Solarized (Dark) colorscheme, so having a light
background doesn't work well in the console. On the other hand,
the dark background is hard to read in MacVim (for me).
This script evaluates the commands specified on the command line and
sends a beep to the terminal after the command completes execution. In
tmux, this results in the window status bar displaying the beep signal.
check_empty for restore was trying to run a git checkout in the current
working directory, instead of in the ~/.notes directory. Fix this issue
note_show uses less to display the contents of the note file.
Add a function add_to_path so that it can prepend any specified path
to the PATH environment variable, but only if it is not already there.
Don't worry about (re)setting the LS_COLORS environment if it's already
been set by the system bashrc.
Fix the following issues in note
1. Always use a combo of lowercase letters, hyphen, underscore and
numbers for the file name. This is taken from the title and uses sed
to translate the uppercase letters to lowercase. Unfortunately,
sed's translation mode doesn't support ranges, so we must use the
full alphabet.
2. Add support for displaying version information.
3. Reformat the help display so it all fits in a single line.
4. Add checking to ensure that at least one argument is passed to note
so that the parse_args routine doesn't barf an error with shift.
5. Remove argument checking in notes_init. It's called only by the init
function, so there's no need to add a flag to control warnings.
This file is sourced by .bashrc and exports LSCOLORS (for OS X systems).
If the .dircolors file exists in the user's home directory, then it is
passed to the dircolors utility (if it exists) and the output is
evaluated to configure GNU ls coloring.
nirenjan