when xfce4-terminal creates its window in an existing terminal process, the environment variables set in the new terminal are the ones set on the first terminal's process, and not inherited from the xfce4-terminal execution that triggered (via dbus) the window creation. as the optimizations of having just one process are quite transparent to the user, they should not affect the observable behavior. (compare rxvt-unicode: even though client-server terminals are explicit there, the environment variables are passed on from the urxvtc (client) call to the created window). this is an issue in combination with all programs that expect environment variables to be passed down to their child process, for example tmux (where it got me) or virtualenv. obseved with xfce-terminal 0.6.3 as packaged for debian as 0.6.3-1+b1.
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/apps/xfce4-terminal/-/issues/11. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev