At work I have a personal account, but I'm doing development on a program which is run by a machine account. By "machine account" I just mean that it isn't tied to a person - it doesn't have any special sysadmin role, but it runs our batch jobs. This account has been around for a while and might do a lot of different things.
During development I'm doing most of my work in this account, so I wanted to setup some aliases, for example "alias e=emacs -nw".
But I'm worried if I edit the .profile-user to add these, I could mess something up. What if e is also the name of some other command it uses which I would be overriding?
So, how can I do this safely? I could just try out the aliases I want one-by-one and verify that they show "command not found" so that there wouldn't be a conflict. But I guess that doesn't account for conflicts in cases where the string might become a command under certain circumstances (e.g. the machine account has a program that cd's to a certain directory and then runs a file which happens to be the same name as my alias).
Just curious if anybody has thought about this before and knows a good way around it, or if you think I really shouldn't introduce aliases on this account.