The way I was doing the test is incorrect, as [ is the test(1) program
and the shell builtin command is not something it understands. Instead,
I now just let the shell execute `command` and then set the variable if
`brew` is available.
This requires the local key (fernandos@N17FERNANDOS3) to be added to
~/.ssh/authorized_keys but uses a more standard and straightforward way
to connect via SSH.
Also, we now connect via a host-only network. This makes us independent
from any port forwarding later.
`bash` will not save history if this directory doesn't exist - it will
create the file but not the directories in the path.
Just to be safe, we do the same for `less`.
As I am creating new keys with the ed25519 type, the constraint was
inconvenient. I now let SSH use the default, which will use either RSA
od ED25519, whatever is available.
Previously the global namespace of all interactive python session were
polluted with all the stuff we did in this initialization script. For
example, globals()['__doc__'] would show the docstring from this file.
While none of this was ciritical, it could be confusing sometimes. So
this commit fixes that.
This bug caused entries to not be removed if they were already present
in the beginning of the list before being prepended. This could lead to
duplication of entires, usually this ended up being /usr/local/bin.
Since the old ports I was using are now no longer accessible from work,
I had to change to the following:
- 143/imap for SSH logins and tunneling
- 587/smtp for access to git repos over SSH
Hopefully these ports will stay open because they are common services.
The default value is:
let g:ctrlp_working_path_mode = 'ra'
which means:
a - like "c", but only applies when the current working directory outside of
CtrlP isn't a direct ancestor of the directory of the current file.
r - the nearest ancestor that contains one of these directories or files:
.git .hg .svn .bzr _darcs
So this makes it more convenient to work within repositories, which is
what I mostly do anyway.
As I am in the process of migrating my key to the more secure ED25519,
this setting was annoying for hosts that don't have RSA keys. Besides,
I am using the defaults anyway, so we can just get rid of this
configuration altogether.
