texstudio-org/texstudio

Exclamation mark in logfile detected as Error instead of Bad Box

Open

#2,518 opened on Aug 9, 2022

View on GitHub
 (6 comments) (1 reaction) (0 assignees)C++ (397 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (3,516 stars)
PR merge metrics
 (Avg merge 5h 26m) (19 merged PRs in 30d)

Description

Environment

  • TeXstudio: 4.2.3
  • Qt: 6.3.0
  • OS: Windows 10
  • TeX distribution: miktex

Expected behavior

My LaTeX file compiles without error ("process terminated normally") and produced a Bad Box with the following log entry:

[34]
Loose \hbox (badness 53) in paragraph at lines 149--150
[]\T1/lmr/m/sc/10.95 (+20) Remark \T1/lmr/m/n/10.95 (+20) 1.4.2\T1/lmr/m/sc/10.
95 (+20) . []\T1/lmr/m/n/10.95 (+20) A more abstract definition of $\U/bbm/m/n/
10.95 1[] \U/msa/m/n/10.95 ^^B \OML/lmm/m/it/10.95 X$ \T1/lmr/m/n/10.95 (+20) f
or $\OML/lmm/m/it/10.95 X [] \OT1/lmr/m/n/10.95 (+20) ([]) \OMS/lmsy/m/n/10.95 
! \OT1/lmr/m/n/10.95 (+20) ([])$ \T1/lmr/m/n/10.95 (+20) and
 []

Package cleveref Info: loaded `english' language definitions on input line 155.

I would expect the row starting with Loose \hbox [...] to show up as a Bad Box under "Errors and Warnings".

Actual behavior

The 7th row, starting with ! \OT1/lmr/m/n/10.95 [...], is detected as an Error and highlighted in red after compiling despite pdflatex terminating normally. I suspect it has to do with the row starting with an exclamation mark.

How to reproduce

I can provide a TeX file if needed.

Contributor guide

Research direction
Investigate the log parser code in TeXstudio that classifies log lines. The issue is that an exclamation mark in a line (e.g., part of a math expression) is incorrectly detected as an error line. Examine the regular expressions or logic used to identify error lines and bad box lines, and find where a line starting with '!' triggers an error detection even when it's actually part of a bad box message.
Tech stack
None
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++QtLaTeX log parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50