Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: Feature request: output/send \033]7; file:///the/current/dir\033\\ on directory change Date: Mon, 25 Nov 2019 08:53:53 -0500 Lines: 29 Approved: bug-bash@gnu.org Message-ID: References: <20191125135353.GK851@eeg.ccf.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1574690065 2377 209.51.188.17 (25 Nov 2019 13:54:25 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org Mail-Followup-To: bug-bash@gnu.org Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 139.137.100.1 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20191125135353.GK851@eeg.ccf.org> X-Mailman-Original-References: Xref: csiph.com gnu.bash.bug:15632 On Mon, Nov 25, 2019 at 02:08:04PM +0200, IFo Hancroft wrote: > I have the following feature request: > > Output/send \033]7;file:///the/current/dir\033\\ on directory change. cd() { builtin cd "$@" && printf '\e]7;file://%s\a' "$PWD" } pushd() { builtin pushd "$@" && printf '\e]7;file://%s\a' "$PWD" } popd() { builtin popd "$@" && printf '\e]7;file://%s\a' "$PWD" } > TL;DR: > It makes sense for the shell to output it on directory change. > Everyone can take advantage of that. > It will be clean solution. You can do it yourself, by putting the functions I just gave you into your ~/.bashrc file. This kind of change doesn't belong in the shell itself, because it will *not* be a "clean solution" for everybody.