Re: [Daniel Burrows <[email protected]>] Bug#292886: Phantom spaces appearing in TeX documents; related to fill?

* Frank Küster (2005-01-31) writes:

> Ralf Angeli <[email protected]> schrieb:
>
>> * Frank Küster (2005-01-31) writes:
>>
>>> There is Debian infrastructure for this. The only thing we need is a
>>> command (a shell command, not an emacs one) that would echo the body
>>> part of "TeX-submit-bug-report" to stdout, i.e. without creating the
>>> headers for the mail. Can you help us with this?
>>
>> The following should do.  I don't know how to get rid of the first two
>> lines of output, though.  Maybe by providing a function in AUCTeX
>> which provides the respective output.
>>
>> emacs -batch -eval "(progn (require 'tex-site) (require 'latex) (require 'reporter) (let ((reporter-status-count 0) (reporter-eval-buffer (current-buffer))) (reporter-dump-state \"AUCTeX\" '(window-system LaTeX-version TeX-style-path TeX-auto-save TeX-parse-self TeX-master) nil nil)) (message (buffer-string)))"
>
> Actually it comes out on stderr, but that doesn't hurt.

According to the Elisp manual this is how it is supposed to be:

,----[ (info "(elisp)Batch Mode") ]
|    Any Lisp program output that would normally go to the echo area,
| either using `message', or using `prin1', etc., with `t' as the stream,
| goes instead to Emacs's standard error descriptor when in batch mode.
`----

The problem with the code is that it uses internals of reporter.el.
It is therefore likely to break once reporter.el gets updated.
Unfortunately reporter.el doesn't provide a clean interface for doing
such stuff.  Its functionality is more or less limited to the creation
of a mail buffer with the whole bug report as its content.

-- 
Ralf