Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable)

On Thu 31 Jul 2014 23:40:18 Linda Walsh wrote: > Chet Ramey wrote: > > type -P echo > > > > ls -l $(type -P echo) > > > > > > If you already have `echo' in the command hash table, type -P will return > > it, since that's what the shell will attempt to execute. > > --- > It's not in the ha

Re: Tilde expansion during command search

On Wed 23 Jul 2014 08:51:19 Dan Douglas wrote: > On Wednesday, July 23, 2014 09:28:02 AM you wrote: > > On 7/23/14, 8:22 AM, Dan Douglas wrote: > > > Hi, from this discussion: > > > > > > https://github.com/koalaman/shellcheck/issues/195#issuecomment-49678200 > > > > > > I can't find any referenc

Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable)

On Thu, Jul 31, 2014 at 11:40:18PM -0700, Linda Walsh wrote: > Ishtar:/> ll {,/usr}/bin/echo > -rw-r--r-- 2 136753 Nov 19 2013 /bin/echo > --w--- 2 136753 Nov 19 2013 /usr/bin/echo > >sudo chmod +x /bin/echo > Ishtar:/> type -P echo > /bin/echo #c

Re: read-only flag is lost for functions in sub shells

On Thu, Jul 31, 2014 at 04:45:20PM -0700, Linda Walsh wrote: > Also noticing broken-ness upon using "sudo" -- functions defined > at login are undefined: > > >typeset -f|grep titlebar > titlebar () > declare -fx titlebar Some implementations of sudo clear the environment before elevating privi

Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable)

On 8/1/14, 2:40 AM, Linda Walsh wrote: > > > Chet Ramey wrote: >> type -P echo >> >> ls -l $(type -P echo) >> >> >> If you already have `echo' in the command hash table, type -P will return >> it, since that's what the shell will attempt to execute. > --- > It's not in the hash table, but typ

Re: Tilde expansion during command search

On Friday, August 01, 2014 06:20:28 AM Mike Frysinger wrote: > On Wed 23 Jul 2014 08:51:19 Dan Douglas wrote: > > On Wednesday, July 23, 2014 09:28:02 AM you wrote: > > > On 7/23/14, 8:22 AM, Dan Douglas wrote: > > > > Hi, from this discussion: > > > > > > > > https://github.com/koalaman/shellchec

Re: Tilde expansion during command search

On 08/01/2014 07:53 AM, Dan Douglas wrote: >> how so ? execvp doesn't do tilde expansion. only the shell does. > > That's the problem. A program using execvp should be able to expect the same > result as that of the shell for a given PATH value. Because of this, it > can't, unless exec has th

Re: Tilde expansion during command search

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/1/14, 11:26 AM, Eric Blake wrote: > On 08/01/2014 07:53 AM, Dan Douglas wrote: > >>> how so ? execvp doesn't do tilde expansion. only the shell does. >> >> That's the problem. A program using execvp should be able to expect the same >> result

Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable)

Mike Frysinger wrote: type -P reflects what the shell will attempt, not what is useful. the fact that it's not usable is irrelevant. The fact that it is not usable is relevant. The type command says it will return the name of the file that will be executed if name was us

Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable)

On Fri, Aug 01, 2014 at 12:30:58PM -0700, Linda Walsh wrote: > Maybe I'm in the minority, but I think the type command is > *fundamentally*, used to look up commands -- things that are > executable. Returning something that isn't because it fits > some Faustian rules seems a bit perverse, no? Wel

Bash-4.3 Official Patch 19

BASH PATCH REPORT = Bash-Release: 4.3 Patch-ID: bash43-019 Bug-Reported-by:John Lenton Bug-Reference-ID: Bug-Reference-URL: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1317476 Bug-Description:

Bash-4.3 Official Patch 20

BASH PATCH REPORT = Bash-Release: 4.3 Patch-ID: bash43-020 Bug-Reported-by:Jared Yanovich Bug-Reference-ID: <20140417073654.gb26...@nightderanger.psc.edu> Bug-Reference-URL: http://lists.gnu.org

Bash-4.3 Official Patch 21

BASH PATCH REPORT = Bash-Release: 4.3 Patch-ID: bash43-021 Bug-Reported-by:Jared Yanovich Bug-Reference-ID: <20140625225019.gj17...@nightderanger.psc.edu> Bug-Reference-URL: http://lists.gnu.org

Bash-4.3 Official Patch 22

BASH PATCH REPORT = Bash-Release: 4.3 Patch-ID: bash43-022 Bug-Reported-by:scorp.dev.n...@gmail.com Bug-Reference-ID: Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2014-06/msg000

Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable)

Greg Wooledge wrote: On Thu, Jul 31, 2014 at 11:40:18PM -0700, Linda Walsh wrote: Ishtar:/> ll {,/usr}/bin/echo -rw-r--r-- 2 136753 Nov 19 2013 /bin/echo --w--- 2 136753 Nov 19 2013 /usr/bin/echo sudo chmod +x /bin/echo Ishtar:/> type -P echo /bin/echo

Re: read-only flag is lost for functions in sub shells

Greg Wooledge wrote: On Thu, Jul 31, 2014 at 04:45:20PM -0700, Linda Walsh wrote: Also noticing broken-ness upon using "sudo": functions are undefined... Some implementations of sudo clear the environment before elevating privileges. Clearing the environment would also remove exported func

How to read fields into an array?

I tried setting a var as an array: declare -a var and then doing a read read var Is there a way to get arrays to work with read directly and not doing something like a split on space into multiple lines and use readarray w/that? It seems like it would make sense if the "declare -a var"

Re: How to read fields into an array?

Linda Walsh wrote: I tried setting a var as an array: declare -a var and then doing a read read var never sorta mind ... read -a var is fine. (Though it would have been snazzy..)

Re: How to read fields into an array?

Remember to use help-bash for these questions.