git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] sending errors to stdout under $PAGER

From
ETEdgar Toernig <froese@gmx.de>
Date
Feb 17, 2008, 13:48 UTC
Message-ID
<20080217144854.56fcb98d.froese@gmx.de>
In-Reply-To
<7vbq6g90gy.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
Show 8 quoted lines
>
> +	FILE *outto = (pager_in_use() ? stdout : stderr);
> +
>  	vsnprintf(msg, sizeof(msg), err, params);
> -	fprintf(stderr, "%s%s\n", prefix, msg);
> +	fprintf(outto, "%s%s\n", prefix, msg);
>
> What do people think?  Have I overlooked any downsides?

Wouldn't it be better/safer to redirect stderr to the pager in the first place?

So, instead of the current
	foo | less
use
	foo 2>&1 | less
or, in pager.c:
         /* return in the child */
        if (!pid) {
                dup2(fd[1], 1);
+               dup2(fd[1], 2);
                close(fd[0]);
                close(fd[1]);
                return;
        }
Ciao, ET.
Previous: Jeff KingNext: Johannes Schindelin
Message 4 of 9 in “[RFC] sending errors to stdout under $PAGER”
  1. Junio C HamanoFeb 16, 2008
  2. Shawn O. PearceFeb 17, 2008
  3. Jeff KingFeb 17, 2008
  4. Edgar ToernigFeb 17, 2008
  5. Johannes SchindelinFeb 17, 2008
  6. Junio C HamanoFeb 17, 2008
  7. Jeff KingFeb 17, 2008
  8. Junio C HamanoFeb 17, 2008
  9. Johannes SchindelinFeb 17, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.