From: Ben Sturmfels <ben@stumbles.id.au>
To: Efraim Flashner <efraim@flashner.co.il>,
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 16:54:48 +1000 [thread overview]
Message-ID: <3ca7f646-7b83-2fb4-9891-03d31410c962@stumbles.id.au> (raw)
In-Reply-To: <2c8f90ad-09a8-e2f3-db53-b80fa1c0fc1b@stumbles.id.au>
On 23/07/19 16:40, Ben Sturmfels wrote:
>>> 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.
>
> I wonder if it's just a matter of moving vte to the propagated-inputs of
> gnome-terminal (and other packages like tilda)? I'll try now and report
> back.
Ok, moving vte to propagated-inputs for gnome-terminal makes
~/.guix-profile/etc/profile.d/vte.sh show up if installed with `guix
package` and /etc/profile.d/vte.sh show up if installed with `guix system`.
Neither ~/.guix-profile/etc/profile or /etc/profile source their
respective profile.d files though like Trisquel does. Can someone give
me a lead on how these profiles are generated?
Regards,
Ben
next prev parent reply other threads:[~2019-07-23 6:55 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
2019-07-23 6:40 ` Ben Sturmfels
2019-07-23 6:54 ` Ben Sturmfels [this message]
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=3ca7f646-7b83-2fb4-9891-03d31410c962@stumbles.id.au \
--to=ben@stumbles.id.au \
--cc=35424@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--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).