all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrii Kolomoiets <andreyk.mad@gmail.com>
To: larsi@gnus.org
Cc: 31497@debbugs.gnu.org
Subject: bug#31497: 27.0.50; vc-hg doesn't separate standard error from standard output
Date: Thu, 10 Oct 2019 14:11:45 +0300	[thread overview]
Message-ID: <E0A630EE-9296-4D87-A047-2DADF2F6AF85@gmail.com> (raw)
In-Reply-To: <wvr4in7ksvwo.fsf@a.muc.corp.google.com>

Lars Ingebrigtsen writes:

>> $ hg log -l 1 -r . -T '{rev}'
>>
>> but that outputs
>>
>> not trusting file /tmp/hg/.hg/hgrc from untrusted user root, group root 
>> not trusting file /tmp/hg/.hg/hgrc from untrusted user root, group root
>
> filter out the "not trusting" lines, or is this just one of a
> gazillion error messages that can be output here?

Other errors also printed to stderr, so filtering out stderr completely
can hide meaningful errors.

This particular warning is also present in log and annotate buffers and
completely messing up vc-dir buffer.

There are option 'ui.report_untrusted' in hg since this commit:
https://www.mercurial-scm.org/repo/hg/rev/97369f6a6bb6

It present in mercurial 2.6.2, the earliest version I found in pip.

To filter out just "not trusting" warning I can propose to run hg like
this:
hg log --config ui.report_untrusted=0 -l 1 -r . -T '{rev}'

or specify '--config ui.report_untrusted=0' as default value for
vc-hg-global-switches

I think 'pull' and 'push' are the only commands that must print this
warning.





  parent reply	other threads:[~2019-10-10 11:11 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
2019-10-10 11:11 ` Andrii Kolomoiets [this message]
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=E0A630EE-9296-4D87-A047-2DADF2F6AF85@gmail.com \
    --to=andreyk.mad@gmail.com \
    --cc=31497@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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.