I am getting the same problem
--
lesspipe relies on $SHELL to tell which shell it's running from
https://bugs.launchpad.net/bugs/120459
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Rephrasing my entry from November last year:
The problem seems to be fixed for new users (at least on my 8.04 system)
as the contents of /etc/skel/.bashrc has been updated to say:
[ -x /usr/bin/lesspipe ] eval $(SHELL=/bin/sh lesspipe)
The problem though is that this doesn't fix the problem
*** This bug is a duplicate of bug 58103 ***
https://bugs.launchpad.net/bugs/58103
If you feel these are the same problem, I shall mark this as a duplicate
of bug 58103. Any more information you can give, please do so in the
other bug report, which will be the main one now. The status of that
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
** Changed
I have the same problem going from tcsh to bash. The reason this at all
shows up is that lesspipe is called in .bashrc: The workaround below
works nicely for me. Actually, looking at /etc/skel/.bashrc, a fix
similar to this has already been implemented, i.e., the problem seems to
be fixed for new
I'm another tcsh user that encountered the same bash: setenv: command
not found errors and traced it back to the same source. Definitely a
logic error in /usr/bin/lesspipe.
--
lesspipe relies on $SHELL to tell which shell it's running from
https://bugs.launchpad.net/bugs/120459
You received this
