all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: p.stephani2@gmail.com, 31497@debbugs.gnu.org
Subject: bug#31497: 27.0.50; vc-hg doesn't separate standard error from standard output
Date: Fri, 11 Oct 2019 09:27:43 +0200	[thread overview]
Message-ID: <87y2xroi6o.fsf@gnus.org> (raw)
In-Reply-To: <837e5dt5v1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Oct 2019 10:30:26 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> I can confirm that this bug is still present in Emacs 27.  The command
>> is started from vc-doc-command, which uses start-file-process, which
>> uses start-process, which doesn't even allow separating stderr from
>> stdin.
>> 
>> (In general, Emacs stderr/stdin handling is very frustrating.)
>
>>From the doc string of start-process:
>
>   If you want to separate standard output from standard error, use
>   ‘make-process’ or invoke the command through a shell and redirect
>   one of them using the shell syntax.

Yes, I think start-file-process and start-process should also provide
the same stderr capabilities as make-process.  Those two functions are
handy, but lead to sloppy handling of stderr.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-11  7:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 17:42 bug#31497: 27.0.50; vc-hg doesn't separate standard error from standard output Philipp Stephani
2019-10-09 21:57 ` Lars Ingebrigtsen
2019-10-10  7:30   ` Eli Zaretskii
2019-10-11  7:27     ` Lars Ingebrigtsen [this message]
2019-10-10 11:11 ` Andrii Kolomoiets
2019-10-14 23:54 ` bug#31497: [Andrii Kolomoiets] " Lars Ingebrigtsen
2019-10-15  0:33   ` Lars Ingebrigtsen
2019-10-16  7:32     ` Andrii Kolomoiets
2019-10-17  2:26       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2xroi6o.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=31497@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=p.stephani2@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.