> "GW" == Greg Wooledge writes:
GW> I find tab completion to be a primary safeguard
Yes but in this case I am merely obediently copying the whole line with
my mouse and stuffing it into the shell. Thanks anyway though.
On Monday 10 June 2013 18:20:44 Chris F.A. Johnson wrote:
> On Mon, 10 Jun 2013, Linda Walsh wrote:
> >> Point taken, but the only way such a string would be passed as a
> >> variable name is if it was given as user input -- which would,
> >> presumably, be sanitized before being used. Progra
Linda Walsh wrote:
Chris F.A. Johnson wrote:
What's wrong with:
rm -rf *
1) it may or may not ignore hidden files depending on shell settings.
2) it crosses into mounted files systems
Forgot an important one:
3) Follows symlinks in the directory you are deleting in. (so if
They
Chris F.A. Johnson wrote:
What's wrong with:
rm -rf *
1) it may or may not ignore hidden files depending on shell settings.
2) it crosses into mounted files systems
On Mon, 10 Jun 2013, Linda Walsh wrote:
Point taken, but the only way such a string would be passed as a
variable name is if it was given as user input -- which would,
presumably, be sanitized before being used. Programming it literally
makes as much sense as 'rm -rf /'.
---
T
Point taken, but the only way such a string would be passed as a
variable name is if it was given as user input -- which would,
presumably, be sanitized before being used. Programming it literally
makes as much sense as 'rm -rf /'.
---
That still didn't POSIX-Gnu rm from disabli
Mike Frysinger wrote:
pretty sure the linux kernel (and others?) would return ETXTBSY and not even
allow the write
I think that's a relatively new innovation -- i.e. since
the ability to setup read-only code segments was implemented,
though FWIW, you are right.
I think it
On Sunday 09 June 2013 16:59:15 Linda Walsh wrote:
> jida...@jidanni.org wrote:
> > All I know is there I am in emacs seeing things in the output of a
> > running bash script that I want to tweak and get busy tweaking and saving
> > changes before the script finishes, thinking that all this stuff w
On Mon, 10 Jun 2013, Greg Wooledge wrote:
On Mon, Jun 10, 2013 at 10:23:10AM -0400, Chris F.A. Johnson wrote:
On Mon, 10 Jun 2013, Chris Down wrote:
Enjoy your arbitrary command execution.
Can you give me an example, using the code I posted, where that would
happen?
On 10 Jun 2013
On Mon, Jun 10, 2013 at 1:37 PM, Pierre Gaston wrote:
> On Mon, Jun 10, 2013 at 12:43 PM, Linda Walsh wrote:
>>
>>
>> Pierre Gaston wrote:
>>
>>> bash4 has associative arrays:
>>>
>>> declare -A array
>>> array[foobar]=baz
>>> echo "${array[foobar]}"
>>
>> ---
>>
>> Right, and bash's namespace is
On Mon, 10 Jun 2013, Greg Wooledge wrote:
On 10 Jun 2013 14:15, "Chris F.A. Johnson" wrote:
It is not the least bit difficult with eval:
eval "array=( \"\${$1[@]}\" )"
On Mon, Jun 10, 2013 at 09:17:23PM +0800, Chris Down wrote:
Enjoy your arbitrary command execution.
To be fair, Chris
On Mon, Jun 10, 2013 at 10:23:10AM -0400, Chris F.A. Johnson wrote:
> On Mon, 10 Jun 2013, Chris Down wrote:
>
> >Enjoy your arbitrary command execution.
>
>Can you give me an example, using the code I posted, where that would
>happen?
> >On 10 Jun 2013 14:15, "Chris F.A. Johnson" wrot
On Mon, 10 Jun 2013, Chris Down wrote:
Enjoy your arbitrary command execution.
Can you give me an example, using the code I posted, where that would happen?
On 10 Jun 2013 14:15, "Chris F.A. Johnson" wrote:
On Mon, 10 Jun 2013, Greg Wooledge wrote:
On Sun, Jun 09, 2013 at 02:02:02PM
> On 10 Jun 2013 14:15, "Chris F.A. Johnson" wrote:
> >It is not the least bit difficult with eval:
> >
> > eval "array=( \"\${$1[@]}\" )"
On Mon, Jun 10, 2013 at 09:17:23PM +0800, Chris Down wrote:
> Enjoy your arbitrary command execution.
To be fair, Chris Johnson was probably assuming a p
On 6/10/13 5:43 AM, Linda Walsh wrote:
> What I found myself wanting was having several 'sets' of
> the same parameters of info. so I could have
> multiple hashes or associative arrays,
>
> eth0=([ip]=1.2.3.4/24 [mtu]=1500 [startmode]=auto)
> eth1=([ip]=192.168.0.1/24 [mtu]=9000 [startmode]=o
Enjoy your arbitrary command execution.
On 10 Jun 2013 14:15, "Chris F.A. Johnson" wrote:
> On Mon, 10 Jun 2013, Greg Wooledge wrote:
>
> On Sun, Jun 09, 2013 at 02:02:02PM -0700, Linda Walsh wrote:
>>
>>> I was wondering if I was missing some syntax somewhere...
>>> but I wanted to be able to p
On Mon, 10 Jun 2013, Greg Wooledge wrote:
On Sun, Jun 09, 2013 at 02:02:02PM -0700, Linda Walsh wrote:
I was wondering if I was missing some syntax somewhere...
but I wanted to be able to pass the name of a hash in
and store stuff in it and later retrieve it... but it
looks like it's only possi
On Sun, Jun 09, 2013 at 02:02:02PM -0700, Linda Walsh wrote:
> I was wondering if I was missing some syntax somewhere...
> but I wanted to be able to pass the name of a hash in
> and store stuff in it and later retrieve it... but it
> looks like it's only possible with an eval or such?
Passing arr
On Sun, Jun 09, 2013 at 08:39:10AM +0800, jida...@jidanni.org wrote:
> # gdk-pixbuf-query-loaders >|
> /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
> bash: gdk-pixbuf-query-loaders: command not found
I know it doesn't directly address your issue, but in cases like these,
I find tab
On Mon, Jun 10, 2013 at 12:43 PM, Linda Walsh wrote:
>
>
> Pierre Gaston wrote:
>
>> bash4 has associative arrays:
>>
>> declare -A array
>> array[foobar]=baz
>> echo "${array[foobar]}"
>
> ---
>
> Right, and bash's namespace is also an associative array -- names & values.
>
> In the main namespac
Pierre Gaston wrote:
bash4 has associative arrays:
declare -A array
array[foobar]=baz
echo "${array[foobar]}"
---
Right, and bash's namespace is also an associative array -- names & values.
In the main namespace you can use '!' to introduce indirection,
but not in a generalized way.
i.e.
21 matches
Mail list logo
