Hi all,Sorry if intervening inappropriately but aren't the names stdin, stdout 
and stderr only C language names?Wouldn't it be preferable to replace them by 
the long name version like 'standard input', 'standard output' and 'standard 
error'?I don't know if POSIX or Standard UNIX or LSB have any recommendations 
though.Best to all.- Bernard Burette
-------- Message d'origine --------De : Bernhard Voelker 
<m...@bernhard-voelker.de> Date : 05/08/2025  21:58  (GMT+01:00) À : Pádraig 
Brady <p...@draigbrady.com>, coreutils@gnu.org Objet : Re: [PATCH] doc: use 
consistent references to standard files On 7/28/25 12:30, Pádraig Brady wrote:> 
* cfg.mk (sc_standard_outputs): A new syntax check to> enforce standard 
references.> * doc/coreutils.texi: s/stderr/standard error/ etc.Nice.Do we 
need/want more patterns, e.g. for translated strings?   $ GIT_PAGER= git grep 
-E '_\("[^"]*std(in|out|err)' -- '*/*.c'   src/du.c:          error (0, 0, 
_("when reading file names from stdin, "   src/nohup.c:                 ? 
N_("ignoring input and redirecting stderr to stdout")   src/nohup.c:            
     : N_("redirecting stderr to stdout")));   src/sort.c:                error 
(SORT_FAILURE, 0, _("when reading file names from stdin, "   src/split.c:      
error (0, 0, _("--filter does not process a chunk extracted to stdout"));   
src/stdbuf.c:              error (0, 0, _("line buffering stdin is 
meaningless"));   src/wc.c:          error (0, 0, _("when reading file names 
from stdin, "Have a nice day,Berny

Reply via email to