GOTO Masanori wrote: > At Sun, 5 Jan 2003 18:06:08 +0000, > Colin Watson wrote: > > For what it's worth, I remember Owen talking about this problem back in > > 1999. He was trying to develop a "guru" locale which simply printed the > > error or signal name - that is, "EPIPE" or "SIGPIPE" - rather than an > > explanatory message. This can't be done correctly when the error > > messages for EPIPE and SIGPIPE are the same, because the gettext msgid > > is keyed on the description, not the error or signal name. > > "guru" message seems good idea, but is it _really_ needed? > Is it a real requirement?
It would sometimes save confusion if EPIPE printed out something different, rather than lots of running around trying to find out why the SIGPIPE hasn't been dropped/handled. In general it's good practice to have different messages for different things. (In my opinion, at least). > > > So I think it's not bug, it's not wishlist item. I close this bug. > > > > I think it's a valid wishlist item and should be reopened as such, even > > if it may be difficult to fix. > > I think this patch fixes this wishlist, but I have not tested yet. It's not a very long patch, so I wouldn't've thought it would be too much of a problem to apply it. J. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
