Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.msdos.batch.nt    |    Fun with Windows NT batch files    |    68,980 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 67,809 of 68,980    |
|    Kenny McCormack to All    |
|    Question about pushd/popd    |
|    02 Nov 21 20:11:50    |
      From: gazelle@shell.xmission.com              CMD.EXE has a version of the pushd/popd commands, obviously based on the       pre-existing commands in the Unix shells (starting with csh, about 4       decades ago).              However, as far as I can tell, the DOS/Windows implementations of these       commands is missing one key functionality - that is, the ability to see       what is on the stack. That is, to see what you will get if you do "popd".       And, in fact, IMHO, it's not really worth much to have the stack and to be       able to "pop" if you have no idea where you're going to pop to.              Note, BTW, that you might argue that you should know where pop is going to       take you, because you should remember where you were before you did the       last "push". This may or may not be true, but what if you've push'd       multiple times? You can't be expected to remember everything, can you?              So, I hope I'm missing something. Is there any way to tell what       directories are currently in "the stack" ?              --       Most Southerners interest in, knowledge of, and participation in politics       begins with       and ends with: Screw the blacks. If a guy is onboard with that, he's our guy!              Get them back in chains where they belong!              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca