Additional information in status bar -- biggest overfull/underfull & no. of pages

[ceplm@…]

Would it be possible to put some additional information to the statusbar after
completion of LaTeX working on the document(á la AUCTeX)? I mean especially
no. of pages of processed dvi/pdf and the biggest overfull/underfull?

I hope, that accquiring this information should not be difficult (you parse
.log file anyhow, don't you?) and I hope it may hugely minimize (at least
for me) time spent in View/LaTeX logfile.

Thanks

[levon]

move to 1.2.0 - 1.1.6 series is not accepting feature requests...

[lasgouttes]

Could you give for reference more information on what auctex provides? We could
also insert the overfull markers in the text as inseterrors (or insetwarnings
which would mostly be the same).

Number of pages may be useful too, and probably a way to go from an error
inset to the relevant log file line.

[levon]

Oh yes please, I've wanted inseterrors for overfulls for /ages/ !
(And some sensible way of using sloppypar where appropriate)

[ceplm@…]

AUCTeX print in the status the following information:

a) information about the errors (and information how to access log), or
b) information, that document need to be reprocessed (via LaTeX or BibTeX), or
c) information, that document is completed and how many pages are in DVI/PDF.

Obviously a) and b) do not apply for LyX, but the last one does. And my addition
was to report also the maximum overfull/underfull.

Of course, if the overfull markers would be included ALSO (I would like still to
keep the information in status bar) even better. Actually, AUCTeX has it
optional
(it either registers overfull/underfull or just leave it), which may be good
idea.

Thanks for taking my idea into account.

[levon]

Mass move to 1.2.0 - grep out the bugspam with "Dharma ex one+one"

[levon]

I can't think of a good way to represent this info (overfull) in
the minibuffer. It would be nice to have the nr. pages etc. from
the build there, though.

[levon]

What about this:

LaTeX done -- 4 pages, 2 overfull boxes, 1 underfull box.

You previously requested "biggest overfull/underfull". Your suggestion
here (basically, a quick summary of the success that would then
indicate to the user that they should have a look at the inseterrors
we inserted) seems OK though.

[lasgouttes]

I think it should be inseterror for overfull/underfull (probably very
easy) and some stats in minibuffer like number of pages.

[levon]

Lars doesn't want any bugs.

[matej@…]

Hi,

just wanted to ask about state of this bug and elaborate on the proposed
report to the status page. It could be even better:

LaTeX done -- 4 pages, 2 overfull boxes (0.05pt max), 1 underfull box.

Matej

[lasgouttes]

I think the state of the bug is that it would be very nice to have,
but nobody is currently doing it :(

This is related to the complete rewrite of .log file parser that we
need to do eventually (I searched for a bug but could not find one).

[sven@…]

Hi, ok this one is pretty old and I've found a similar wishlist bug in the
Debian BTS. I hope it's ok to add it here instead of opening another bug for it.
​http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=208032

Original report:
"""
Lyx should recognized and mark lines where the line wrap failed
("overfull/underfull hbox") and give the user and easy way of enabling
sloppypar for a paragraph that cannot be changed to generate a pretty
linewarp.
Right now you need to search the location yourself (which is a PITA for large
documents, a "goto bad line break" would be very convenient) and then
add Inline-Tex to enable sloppypar and disable it at the end
(so it's two things you need and copy&paste will be annoying, too.
"""

[Uwe Stöhr]

In LyX 2.0 there is a new windows showing you all Latex messages -> fixedintrunk

[ps]

2.0.0 is ready