There's still something I don't quite get. There's a global alias list, used by concurrent sessions and with SHRALIAS possibly future sessions as well. Then I say "ALIAS /L". Now the session at hand uses a new alias list (right?) and that new list is populated with what's in the global list (right? ... this may not be what's wanted). Then I make/change some aliases (supposedly in the local list) and later "ALIAS /G". Why is the local list propagated to the global list? Does anyone want that to happen? It seems counter-productive to me. For me, the global list is something that endures (for years, really) and while I might want to use special aliases for a while I don't want tha global list messed with. Yes, I know there's SETLOCAL but the need to use both SETLOCAL and ALIAS /L (/G) together to prevent aliases changing in concurrent and future sessions is cumbersome and confusing. I'd be happy with two completely independent lists, a local one and a global one. Global-to-local propagation is OK but I wouldn't need it. Local-to-global propagation (IMHO) should be a no-no. I'd like to be able to (in a batch file) alias /l Now i can do batch specific stuff, even load an alias file; later alias /g Go back to using the global aliases (as they were). In a nutshell: Is the local-to-global propagation of aliases necessary or desirable?