From: pinard@iro.umontreal.ca (François Pinard)
To: emacs-orgmode@gnu.org
Subject: Re: A bit more feedback on org-publish-all
Date: Mon, 06 Feb 2012 09:56:03 -0500 [thread overview]
Message-ID: <87ipjkau4c.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <17364.1328499519@alphaville> (Nick Dokos's message of "Sun, 05 Feb 2012 22:38:39 -0500")
Nick Dokos <nicholas.dokos@hp.com> writes:
> (message "foo") prints to stderr in batch mode, which is an unbuffered
> stream. E.g ``emacs --batch -l foo.el'' with foo.el containing
> (message "foo")
> (sit-for 10)
> prints out ``foo'' and then sits for 10 seconds before exiting.
Hi, Nick.
It seems you are right. I initially guessed that -batch might have
Emacs to allocate an output buffer, or at least do it when output is not
directed to a terminal. But it even works as you say if I do:
emacs 2>&1 --batch -l foo.el | cat
This is more similar to my actual usage, which really is:
[...]
write = sys.stderr.write
for line in os.popen('emacs 2>&1 -batch'
' -l ~/fp/notes/publish.el'
' -f org-publish-all'):
write(repr(line) + '\n')
sys.stderr.flush()
[...]
The write(...) and the flush() are only there for debugging: I wanted to
see if the lines are delivered timely or not (and I'm seemingly getting
the Emacs output in one blow). I just do not understand why the
behavior differs between the "... | cat" line and the Python excerpt.
I'm surely missing something somewhere... Sigh!
> Also, don't you get messages for every file?
Yes, and these messages usually say: "Skipping unmodified file ..."
On the "entertaining side", this is too much noise; I would have
preferred a mere line per project. Not a big deal anyway for me. On
the "debugging side", this is sufficient indeed.
> I would recommend looking at the worg publishing mechanism in
> general. See
> http://orgmode.org/worg/worg-setup.html
> particularly the sections entitled
> - What .emacs.el file is used on the server?
> - I want it for my own server!
Hey, thanks for this pointer, Nick; there seems to be useful hints or
tricks in there. I'm saving it for later study.
I plan to progressively convert more of my previous pages to Org format,
and use it more for new pages too, as Org format and mode are so nice
for maintenance. I plan to retain a few reStructuredText sources as
such, as reST also has it virtues for publishing. I also hope that Org
publishing offers me opportunities for experimenting (OK, OK: toying!)
with new HTML/CSS avenues, I'm not familiar enough to be sure yet.
François
next prev parent reply other threads:[~2012-02-06 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 14:48 A bit more feedback on org-publish-all François Pinard
2012-02-06 1:31 ` François Pinard
2012-02-06 3:38 ` Nick Dokos
2012-02-06 14:56 ` François Pinard [this message]
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=87ipjkau4c.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).