Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm more than a bit disappointed with the limits of the internal variable $OLDPWD in BASH. My analogy for it is as follows:
A fellow who lives in a two-story house gets up in the morning. He goes out to his porch after getting dressed. He comes back in, goes into his kitchen downstairs and cooks breakfast. He eats his breakfast in his dining room. Then he goes upstairs to his home office/study. In the middle of looking for a book, a call of nature brings him to the upstairs bathroom. While he's there, he crosses the hallway outside and gets a new can of shaving cream out of a closet. Then he returns to the bathroom and shaves. On finishing this task, he returns to the home office room, sits down at the computer and starts his email application. An email from a friend asks him what he's been up to that morning. The only thing he can remember is being in the upstairs bathroom, shaving.
I'm not implying it should remember all the cd (change directory) commands in a session; just one more cached for the $OLDPWD variable would be an improvement on things, however.
If BASH can't be "ramped up" in the way I'm describing, is there already a shell with a better "memory," a better handle on where one has been in terms of directory navigation, and has variables or built-in commands to prove it?