François Pinard <pin...@iro.umontreal.ca> 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 > > way. [...] the script execution is a bit longish [...] while being > > too silent. > > Hmph! > > `emacs --batch' buffers its output. So, "Publishing PROJECT" messages > would not be written timely, and the delaying would remove the > entertaining virtues. > > Yet, such "Publishing PROJECT" messages would be helpful in case of any > error, as a kind of title prefixing it, and would ease debugging. >
[I haven't looked at earlier messages in this thread, so I hope I am not misinterpreting.] (message "foo") prints to stderr in batch mode, which is an unbuffered stream. E.g ``emacs --batch -l foo.el'' with foo.el containing --8<---------------cut here---------------start------------->8--- (message "foo") (sit-for 10) --8<---------------cut here---------------end--------------->8--- prints out ``foo'' and then sits for 10 seconds before exiting. Also, don't you get messages for every file? The only publishing I've done recently is worg publishing (I publish locally to test any changes I make before pushing). That gives me a fairly detailed list of what it is doing. AFAICT, that's the default behavior, but there may be settings I've overlooked. 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! Nick
