On Mon, May 12, 2025, 6:58 AM Danilo Pecher via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote: > > That's normal. If you start a new shell, the aliases are a clean > sheet. Unlike Unix shells, FreeCOM doesn't have startup files (perhaps > an idea for the future).
AUTOEXEC.BAT is the startup file for command.com (such as FreeCOM) and always has been. It is only read for permanent instances of the shell. Translating this to Unix and Linux, it's similar to the .bash_profile startup file, which is read at login time. I think that's what you are comparing it to -- because .bashrc is a second startup file, which is read for secondary shells, like a terminal window running inside your GUI. I think you are referring to that. On a Linux system, if I create this file as ~/.bash_profile: echo primary shell ..and create this as ~/.bashrc: echo secondary shell ..then when I login at the console (or SSH into the system, or login through an old-style terminal, ..) then the shell will print "primary shell" and nothing else. The ~/.bash_profile is only read as the startup file for a login shell. If I run 'bash' from inside that shell instance, then the shell will print "secondary shell" (but not "primary shell"). That's because ~/.bashrc is only read by secondary shells. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
