Hello,
I can not help too much on the "bug" side, but I would like to give a
tip regarding the situation you describe.
Often I've the same caveats about how my code will be used in a future
without my control...
If you know for sure, what makes the code unreliable, in this example
the /proc subs
On 4 March 2013 14:51, Chet Ramey wrote:
>
> This isn't accurate. Run the following script:
>
> foo()
> {
> echo foo
> }
> bar=quux
>
> readonly foo
> readonly bar
>
> readonly
>
> In addition to the built-in bash readonly variables, both bar and foo will
> be listed.
Maybe I'm wrong, bu
Hello,
Sorry if this has been reported earlier, but I can't find nothing
related in the archives.
$ help readonly | grep -- '-p'
readonly: readonly [-aAf] [name[=value] ...] or readonly -p
-pdisplay a list of all readonly variables and functions
$ echo $B
