I think at the time I frequently found myself working in environments where
typing "vi" would end up in compatible mode (which I never wanted).
(Probably a lot of "sudo vi file" on a new OS install...).
It felt silly to have to keep installing workarounds like multiple aliases
or something
when i could even more easily type the command I really wanted and never
have that problem again.
I had never used the real "vi" anyway... "vim" is all I've ever known.
On Mon, May 30, 2011 at 4:52 PM, Chas. Owens <chas.ow...@gmail.com> wrote:
> On Mon, May 30, 2011 at 10:06, Randy Stauner
> <ra...@magnificent-tears.com> wrote:
> snip
> > As another example, when I tried to teach myself to stop using "vi" and
> type
> > out "vim" i simply aliased "vi" to echo me a reminder to use "vim" and
> then
> > do nothing. I quickly learned to stop doing that and have since removed
> my
> > alias.
> snip
>
> Why type out vim instead of vi? I always just alias vi to be vim.
>
>
>
> --
> Chas. Owens
> wonkden.net
> The most important skill a programmer can have is the ability to read.
>
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
