From: pinard@iro.umontreal.ca (François Pinard)
To: emacs-orgmode@gnu.org
Subject: A bit more feedback on org-publish-all
Date: Sun, 05 Feb 2012 09:48:37 -0500 [thread overview]
Message-ID: <87ty351gl6.fsf@iro.umontreal.ca> (raw)
Hi, Orger friends.
When I execute org-publish-all, I would like to have some indication of
the progress, so I can follow what is going on.
The *Messages* buffer indeed gets crowded with many noisy lines, and I
can find hints about the project being processed though "Skipping
unmodified file SUCH-AND-SUCH" or "Loading .../PROJECT.cache" messages.
These lines may undoubtedly be useful when something goes wrong, but
otherwise, they just prevent the mini-buffer, say, to display some
clear "Publishing PROJECT..." message at the start of each project.
Such "Publishing PROJECT..." message would also be useful to me in
another way. I'm using a script which launches "emacs -batch ... -f
org-publish-all" under the scene and filters its output to get rid of
all the noisy lines. My hope is that errors, if any, will stand out. I
could let such "Publishing" messages go through the filter, however.
Currently, I find that the script execution is a bit longish (I have a
few dozen projects), while being too silent.
I could probably manage with hooks of various kind and more
configuration to the org-publish-project-alist structure, but it would
look as overkill to me for getting such a benign feedback.
François
next reply other threads:[~2012-02-05 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 14:48 François Pinard [this message]
2012-02-06 1:31 ` A bit more feedback on org-publish-all François Pinard
2012-02-06 3:38 ` Nick Dokos
2012-02-06 14:56 ` François Pinard
2012-02-06 15:21 ` Nick Dokos
2012-02-06 15:27 ` Nick Dokos
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ty351gl6.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--cc=emacs-orgmode@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).