From: Eli Zaretskii <eliz@gnu.org>
To: Karthik Chikmagalur <karthikchikmagalur@gmail.com>
Cc: yantar92@posteo.net, jschmidt4gnu@vodafonemail.de, emacs-devel@gnu.org
Subject: Re: Understanding filter function calls
Date: Sat, 29 Jul 2023 09:04:51 +0300 [thread overview]
Message-ID: <83r0ori77g.fsf@gnu.org> (raw)
In-Reply-To: <87a5vf1z97.fsf@gmail.com> (message from Karthik Chikmagalur on Fri, 28 Jul 2023 14:51:00 -0700)
> From: Karthik Chikmagalur <karthikchikmagalur@gmail.com>
> Cc: Jens Schmidt <jschmidt4gnu@vodafonemail.de>, emacs-devel@gnu.org
> Date: Fri, 28 Jul 2023 14:51:00 -0700
>
> > Do you mean that
> >
> > -v, --verbosity=level
> > Controls the type of messages printed during a dvisvgm run:
> > 0 no message output at all
> > 1 error messages only
> > 2 warning messages only
> > 4 informational messages only
> >
> > Note By adding these values you can combine the
> > categories. The default level is 7, i.e. all messages
> > are printed.
> >
> > is not sufficient?
>
> Yes. The text in the example stdout(s) I included are all generated by
> 4, "informational messages only".
Then I guess another level, which will only output the file name, is
in order.
next prev parent reply other threads:[~2023-07-29 6:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 5:46 Understanding filter function calls Karthik Chikmagalur
2023-07-24 20:57 ` Jens Schmidt
2023-07-27 21:08 ` Karthik Chikmagalur
2023-07-27 21:44 ` Karthik Chikmagalur
2023-07-28 5:47 ` Eli Zaretskii
2023-07-28 5:44 ` Eli Zaretskii
2023-07-28 21:42 ` Karthik Chikmagalur
2023-07-29 6:02 ` Eli Zaretskii
2023-07-29 22:16 ` Karthik Chikmagalur
2023-07-30 5:14 ` Eli Zaretskii
2023-07-28 7:54 ` Ihor Radchenko
2023-07-28 21:51 ` Karthik Chikmagalur
2023-07-29 6:04 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-18 3:52 Karthik Chikmagalur
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=83r0ori77g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=karthikchikmagalur@gmail.com \
--cc=yantar92@posteo.net \
/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.