Curious compile error, easily fixed

[Paul A. Rubin]

On 5/23/22 13:54, Rich Shepard wrote:
> On Fri, 20 May 2022, Paul A. Rubin wrote:
>
>> After the initial compilation attempt, you can open the generated .tex
>> file (lurking in the buffer directory) in a text editor and search 
>> for any
>> mention of verbatim. It could be that some module or funky document
>> element is using it. If there's more than one occurrence, the 
>> location of
>> the error in the document log window might help narrow down which one
>> triggered the error.
>
> Paul,
>
> I wonder if the SARS-COV-2 virus infected this document. Here's the 
> preamble
> as shown in Documents -> Settings -> Preamble:
> \date{}
> \usepackage{mathpazo}
> \usepackage{graphicx,relsize}
> \usepackage{scrlayer-scrpage}
> \usepackage{colortbl}
> \definecolor{lightgray}{gray}{0.8}
> \pagestyle{scrheadings}
> \lehead{Biological Evaluation}
> \rohead{Biological Evaluation}
> \refoot{Applied Ecosystem Services, LLC}
> \lofoot{Applied Ecosystem Services, LLC}
> \automark*{section}
>
> And this is the preamble in /tmp/lyx_tmpdir.oskNDlV31096/lyx_tmpbuf1:
> \batchmode
> \makeatletter
> \def\input at path{{/home/rshepard/projects/.../.../reports/}}
> \makeatother
> \documentclass[twoside,headsepline=on, footsepline=on]{scrreprt}
> \PassOptionsToPackage{natbib=true}{biblatex}
> \usepackage[T1]{fontenc}
> \usepackage[utf8]{inputenc}
> \usepackage[letterpaper]{geometry}
> \geometry{verbose,tmargin=4cm,bmargin=2cm,lmargin=2cm,headsep=1.5cm}
> \pagestyle{plain}
> \setlength{\parskip}{\medskipamount}
> \setlength{\parindent}{0pt}
> \usepackage{verbatim}
> \usepackage{graphicx}
>
> \makeatletter
>
> I do not see any reference to the verbatim package in any settings dialog
> box.
>
> How do I remove an invisible package?
>
> Regards,
>
> Rich
 From some long forgotten sci-fi movie, I think you fill the document 
with a fine powder, shake, and hope it sticks to the invisible package (?).

I created an empty document with the contents of your preamble and 
didn't get any references to verbatim. Does your document contain code 
listings or other funky elements that might automagically trigger a load 
of the verbatim package? You may need to apply bisection to find out the 
culprit.

Paul