Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: Subject: Manual directory stack ambiguity Date: Fri, 14 Aug 2015 16:29:37 -0400 Lines: 15 Approved: bug-bash@gnu.org Message-ID: References: NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1439584215 19190 208.118.235.17 (14 Aug 2015 20:30:15 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org To: Tim Nielens Envelope-to: bug-bash@gnu.org Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 139.137.100.1 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:11352 On Fri, Aug 14, 2015 at 12:08:07PM +0200, Tim Nielens wrote: > Within the whole manual node, it's never clear whether the directory stack > includes the current directory or not. imadev:~$ bash imadev:~$ popd bash: popd: directory stack empty imadev:~$ dirs ~ *shrug* I don't use these commands, so I don't know either. One of them says it's empty, and the other says it has ~ in it. More legacy csh rubbish.