** Tags added: hardy
--
/etc/skel/.bashrc - lesspipe problem
https://bugs.launchpad.net/bugs/58103
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
As per the duplicate bug report bug 120459, this isn't a problem in
Hardy upwards, but users upgrading to one of these will still have this
problem.
--
/etc/skel/.bashrc - lesspipe problem
https://bugs.launchpad.net/bugs/58103
You received this bug notification because you are a member of Ubuntu
Marking Triaged, there should be enough information here for a developer
to begin working on this problem.
** Changed in: less (Ubuntu)
Status: Confirmed = Triaged
--
/etc/skel/.bashrc - lesspipe problem
https://bugs.launchpad.net/bugs/58103
You received this bug notification because you
** Changed in: less (Ubuntu)
Importance: Undecided = Low
--
/etc/skel/.bashrc - lesspipe problem
https://bugs.launchpad.net/bugs/58103
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: less (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
/etc/skel/.bashrc - lesspipe problem
https://launchpad.net/bugs/58103
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Relying on any sort of environment variable seems problematic, and my
suggestion especially will not work, because the division isn't between
bash and all other shells, but csh and derivitaves vs all other
shells.
Hadmut's solution or a similar one seems like the right direction to
take on this,
Micah Cowan wrote:
Bash does set SHELL, but (1) only if it's not already set, and (2)
always to the user's login shell, as specified in /etc/passwd
(therefore, it's not always bash: if the user's login shell is
/bin/tcsh, bash will actually set SHELL to /bin/tcsh).
The solution feels like a
Bash does set SHELL, but (1) only if it's not already set, and (2)
always to the user's login shell, as specified in /etc/passwd
(therefore, it's not always bash: if the user's login shell is
/bin/tcsh, bash will actually set SHELL to /bin/tcsh).
The solution feels like a hack, but I'm not sure
