Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail From: Linda Walsh Newsgroups: gnu.bash.bug Subject: bash expanding relative paths in auto-complete Date: Thu, 13 Aug 2015 15:34:09 -0700 Lines: 15 Approved: bug-bash@gnu.org Message-ID: NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1439505264 7083 208.118.235.17 (13 Aug 2015 22:34:24 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash Envelope-to: bug-bash@gnu.org User-Agent: Thunderbird X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 173.164.175.65 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:11349 in bash 4.3.39, if I type a command, (like "."(source)) and a relative path like : ../conf, it expands the relative pathname to absolute pathnames. This is bad .. since I reuse relative commands in different absolute places. It didn't used to do this, and it's a potential security problem, since if you reuse a command to configure something from before, and don't catch that it's not using the relative path, it could run the wrong command...