Calum wrote:i was under the impression that apps like vim and elvis will run differently re: things like colour coding depending on how they are invoked, ie: if invoked through a symlink called "vi" they would behave differently than if called directly. Is this a misunderstanding on my part?
I did some quick research into this. They do have command-line options, which are mostly for file management. Command-line arguments are clearly passed to the editor, otherwise I couldn't tell it what file to open - "vi myfile.txt" works whether you use a symlink or an alias. It looks like both vim and elvis use an rc script such as .vimrc to control their environment, although there are also commands within both programs to change environment settings on the fly.
Calum wrote:also, why not put the alias into a global rc file? something like /etc/profile or maybe there's an /etc/bashrc to put it into. This is probably what i'd do after reading this thread, simply because i like to treat any system as though it's a multiuser system, because i think that's good practice and aolso you never know what the future holds.
You're probably right, pretending it is a multiuser system is better for learning, which is my primary goal. But I don't think there is any real difference between using a symlink or a global alias. In fact, you could probably use both. A symlink is what was there, so that's what I worked with. (the fact that the symlink was to elvis, not vim, was probably Pat's personal choice) I believe that any user could still make a local alias to choose another editor. I'll actually try using both a global symlink and a local alias to see which editor I get, just so I know how it works.