François Pinard wrote:
> ...
> 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-pub
François Pinard wrote:
> > 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 "deb
Nick Dokos 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
François Pinard wrote:
> pin...@iro.umontreal.ca (François Pinard) writes:
>
> > When I execute org-publish-all, I would like to have some indication
> > of the progress, so I can follow what is going on. [...] Such
> > "Publishing PROJECT..." message would also be useful to me in another
> >
pin...@iro.umontreal.ca (François Pinard) writes:
> When I execute org-publish-all, I would like to have some indication
> of the progress, so I can follow what is going on. [...] Such
> "Publishing PROJECT..." message would also be useful to me in another
> way. [...] the script execution is a
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-
