On 7 Jul 2014 19:47, "Eric Blake" wrote:
>
> On 07/07/2014 12:34 PM, Chris Down wrote:
> > Hi Jon,
> >
> > As is standard with other buitins, umask is documented at `help umask`:
>
> That said, POSIX allows, and ksh already supports, the use of --help as
> an option to ALL builtins. It might be ni
On 7/30/14, 2:44 PM, Notes Jonny wrote:
> On 7 Jul 2014 19:47, "Eric Blake" wrote:
>>
>> On 07/07/2014 12:34 PM, Chris Down wrote:
>>> Hi Jon,
>>>
>>> As is standard with other buitins, umask is documented at `help umask`:
>>
>> That said, POSIX allows, and ksh already supports, the use of --help
I just noticed in the 4.2.45 I'm still running that when I
reset my local to standard (LC_ALL=C), it turned off
"vi mode" in my shell ops and turned on emacs mode.
Has this been fixed?
Thanks..
If I assigned the read-only bit to an exported var and run a new
shell, that var is still read-only.
However, doing the same with an exported function seems to drop
the read-only status. If read-only status is supposed to be
immutable, wouldn't is this desirable?
(bash 4.2)
I got various suggestions for getting my script to work at boot time,
and any of them might have been applicable before I'd gotten to the current
problem...
In particular the <<<"$VAR" construct where VAR was holding
output from a program.. was something on my "iffy" list,
but it seemed to work
Was comparing /contrasting output of "which" with output of "type -[pPa]"
(trying all 3) with the intent of being able to turn which into an
alias, since
it returned incorrect info for "builtins, aliases and functions" -- because
it is a separate program.
While "which" returns "not found in pat
