Per discussion in: https://bugzilla.gnome.org/show_bug.cgi?id=697475 VTE upstream thinks we should source /etc/profiles.d/*.sh content always (login and non-login shells) as Fedora does to easily recover "open tab in previous directory" feature -> https://bugzilla.gnome.org/show_bug.cgi?id=697475#c24 Not sure if would be possible to do that :/ Reproducible: Always
that's not going to happen. profile.d is for login shells only, end of story. i've debated adding bashrc.d in the past, but never had a compelling use case. i also vaguely recall there being other aspects, but it's been so long that i can't really remember.
Well, bashrc.d could also help I think, but will explain this to upstream as other people from other distributions different than Fedora are also complaining. Will keep you informed Thanks
They don't like the idea because other shells (like zsh) would need to run scripts from bashrc.d dir :/ https://bugzilla.gnome.org/show_bug.cgi?id=697475#c34
Created attachment 388934 [details, diff] bashrc.d patch Here's my patch to add bashrc.d support. If nobody has a better idea, I'll commit it today. Otherwise, please provide this better idea since people want completions to work *this* year.
I can't tell for sure if you are already considering this to be needed in /etc/bash/bashrc # https://bugs.gentoo.org/show_bug.cgi?id=338335 # Login shell, avoid duplicate profile.d run http://unix.stackexchange.com/a/26782/2847 shopt -q login_shell && return for sh in /etc/profile.d/*.sh ; do [ -r "$sh" ] && . "$sh" done unset sh Otherwise we're gonna be running profile.d stuff twice on login shell.
+*bash-4.3_p30-r1 (09 Nov 2014) + + 09 Nov 2014; Michał Górny <mgorny@gentoo.org> +bash-4.3_p30-r1.ebuild, + +files/bashrc-r1: + Introduce support for bashrc.d directory that is sourced in bashrc by default, + bug #468094.
So now app-shells/bash-completion-2.1-r92 blocks against all previous versions of bash, including bash-3.2* and bash-4.2* which are the official versions used in ebuilds. Changes of that scope should be discussed in -dev. Reopening and CCing QA.
(In reply to Ulrich Müller from comment #7) > So now app-shells/bash-completion-2.1-r92 blocks against all previous > versions of bash, including bash-3.2* and bash-4.2* which are the official > versions used in ebuilds. Changes of that scope should be discussed in -dev. > > Reopening and CCing QA. This predates me by several years and I have no idea what the context was/is. Is there a reason to keep this open? I don't see one.
(In reply to Sam James from comment #8) > (In reply to Ulrich Müller from comment #7) > > So now app-shells/bash-completion-2.1-r92 blocks against all previous > > versions of bash, including bash-3.2* and bash-4.2* which are the official > > versions used in ebuilds. Changes of that scope should be discussed in -dev. > > > > Reopening and CCing QA. The blocker was removed soon after: https://gitweb.gentoo.org/archive/repo/gentoo-2.git/commit/?id=6c67e7330a48691d3775aed494ae3874e19fd02f commit 6c67e7330a48691d3775aed494ae3874e19fd02f Author: Michał Górny <mgorny@gentoo.org> Date: Mon Nov 10 17:59:34 2014 +0000 Remove the bash blocker, and just depend on bash. There is no point having | | ( bash zsh ) when bash is obligatory for ebuilds. (Portage version: 2.2.14/cvs/Linux x86_64, signed Manifest commit with key E FB4464E!) > This predates me by several years and I have no idea what the context > was/is. Is there a reason to keep this open? I don't see one. Yes, this bug can be closed.
