On 9/15/19 12:50 PM, Roland Illig wrote:
> Hi,
>
> in help.def, the code reads:
>
> if (glob_pattern_p (list->word->word))
> {
> printf ("%s", ngettext ("Shell commands matching keyword `",
> "Shell commands matching keywords `", (list->next ? 2 : 1)));
> print_word_list (list,
On 9/15/19 4:07 PM, Roland Illig wrote:
> The help for "(( ))" says:
>
>> evaluation. Equivalent to "let EXPRESSION".
>
> All other help topics use `these' quotes.
Thanks, it should be let "EXPRESSION", with or without the `' quotes,
as it is in the man page.
--
``The lyf so short, the cr
On 9/15/19 2:01 PM, Roland Illig wrote:
> internal_warning (_("add_process: process %5ld (%s) in the_pipeline"),
> (long)p->pid, p->command);
>
> What does "the_pipeline" mean?
PROCESS *the_pipeline = (PROCESS *)NULL;
>
> And why is an internal warning translated anyway?
It indicates an anomal
On 9/15/19 3:29 PM, Roland Illig wrote:
> The command "help alias | sed s,$,$," prints some lines with trailing
> whitespace. What is the purpose of this trailing whitespace? If there is
> none, it should not be generated at all.
I can't reproduce this.
--
``The lyf so short, the craft so long t
On 9/15/19 2:24 PM, Roland Illig wrote:
> From siglist.c:
>
> sys_siglist[i] =
> (char *)xmalloc (10 + strlen (_("Unknown Signal #")));
>
> sprintf (sys_siglist[i], _("Unknown Signal #%d"), i);
I'll figure something out. This code is used in exceedingly rare
circumstanc
On 9/15/19 3:57 PM, Roland Illig wrote:
> The help text of getopts says:
>
>> Getopts normally parses the positional parameters ($0 - $9), but if
>> more arguments are given, they are parsed instead.
>
> The positional parameter $0 (is it even called that way) is not parsed
> by getopts. Its
That's a a re-post of a bug report I raised a few years ago and
comes back now and then in various Q&A sites I participate in.
The discussions kind of trailed off last time.
https://www.mail-archive.com/bug-bash@gnu.org/msg17783.html
2016-02-24 15:16:41 +, Stephane Chazelas:
> $ time bash -c
