3 ms·
So 'run commands' is the historically correct interpretation. For me, I've heard it explained as 'run configuration' many years ago and that is the explanation
by weinzierl 7y ago
So 'run commands' is the historically correct interpretation.
For me, I've heard it explained as 'run configuration' many years ago and that is the explanation that stuck because rc is in essence used for config files no matter if they run commands or not. Others have found different expansions, which are probably equally obvious for them. The ones I stumbled upon by a quick search [1,2,3,4]:
run commands
run control
run configuration
runtime configuration
resource control
Maybe there are more.
[1] https://unix.stackexchange.com/questions/3467/what-does-rc-in-bashrc-stand-for/3469#3469 https://unix.stackexchange.com/questions/3467/what-does-rc-i...
[2] https://superuser.com/questions/144339/vimrc-screenrc-bashrc-kshrc-etc-what-does-the-rc-mean https://superuser.com/questions/144339/vimrc-screenrc-bashrc...
[3] https://askubuntu.com/questions/23482/what-does-rc-in-bashrc-nanorc-stand-for https://askubuntu.com/questions/23482/what-does-rc-in-bashrc...
[4] http://www.catb.org/~esr/writings/taoup/html/ch10s03.html http://www.catb.org/~esr/writings/taoup/html/ch10s03.html
- Sharlin 7y agoCertainly the other expansions are backronyms, invented by people wondering what the "rc" stands for.
- jasoneckert 7y agoDitto here - I've heard it referred to as runtime configuration for decades (even when I worked at SUN writing drivers and interfaces for SunOS 4 and 5).