From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 35424@debbugs.gnu.org
Subject: bug#35424: Gnome terminal doesn't keep current working directory in new tab/window
Date: Tue, 23 Jul 2019 09:35:14 +0300 [thread overview]
Message-ID: <20190723063514.GC780@macbook41> (raw)
In-Reply-To: <87lfwpdgyu.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Mon, Jul 22, 2019 at 09:09:13PM +0200, Ricardo Wurmus wrote:
>
> Hi Ben,
>
> >> Just minor thing, but on other systems I use, when you open subsequent
> >> Gnome Terminal tabs, the current working directory is maintained in the
> >> new tab. On my Guix System, new tabs start up back at /home/ben.
> >
> > I've found that sourcing vte.sh fixes the issue, and the working
> > directory is retained:
> >
> > `source /gnu/store/...-vte-0.52.2/etc/profile.d/vte.sh`
>
> Interesting. Is this file installed to /etc/profile.d/vte.sh on other
> systems? Or is it otherwise sourced?
>
I can only speak for my own system. I don't have gnome-terminal
installed, but I do have tilda which uses vte. My
~/.guix-profile/etc/profile.d/ only has bash_completion.sh.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-23 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 5:28 bug#35424: Gnome terminal doesn't keep current working directory in new tab Ben Sturmfels
2019-07-22 8:50 ` bug#35424: Gnome terminal doesn't keep current working directory in new tab/window Ben Sturmfels
2019-07-22 19:09 ` Ricardo Wurmus
2019-07-23 6:35 ` Efraim Flashner [this message]
2019-07-23 6:40 ` Ben Sturmfels
2019-07-23 6:54 ` Ben Sturmfels
2019-07-23 8:26 ` Ben Sturmfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190723063514.GC780@macbook41 \
--to=efraim@flashner.co.il \
--cc=35424@debbugs.gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).