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,812 of 68,980    |
|    Herbert Kleebauer to Kenny McCormack    |
|    Re: Question about pushd/popd    |
|    03 Nov 21 10:42:17    |
      From: klee@unibwm.de              On 02.11.2021 21:11, Kenny McCormack wrote:              > 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.              Can you give a real world example, where it is useful to know what's       on the stack? But anyhow, this should work:              popd&call set pop=%%cd%%&pushd %cd%       echo Last enty on stack: %pop%              --- 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