Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15373 > unrolled thread

Re: typo in internal warning: the_pipeline

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: typo in internal warning: the_pipeline Chet Ramey <chet.ramey@case.edu> - 2019-09-16 10:26 -0400

#15373 — Re: typo in internal warning: the_pipeline

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 anomalous but non-fatal condition that indicates a possible
bug, so it's a message like any other. You'd like the user to know what it
is and, I hope, report it.

In this case, that doesn't really matter because the message is #ifdef
DEBUG and won't appear in production releases, so it probably doesn't need
to be translated.

The real bug is that there are some untranslated calls in jobs.c that
aren't protected by #ifdef DEBUG.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web