# htlatex gives me a lot of “random” errors [closed]

I'm using htlatex to convert LaTeX into HTML and I'm getting errors on things that I haven't specified, such as my own environments.

An example is \def\inline{\lstinline[style=inlineStyle]} which lets me write:

\inline{x == 10}

I'm also using it like this:

\inline!new[]{}!

This is just one example, I've got tons of different environments like this. The error I'm getting on this is:

? ! Missing } inserted. } l.223 \inline!new[] {}!

So I want to know if there is an "Silent"-flag that I can use when converting using htlatex? So I don't have to press and hold Enter for 1 minute during the conversion.

-

## closed as too localized by Marco Daniel, Joseph Wright♦Aug 4 '12 at 21:46

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

you can a;ways respond with s to a tex ? error prompt and it will go into scroll mode and not ask again. but if you are using a lot of listings/verbatim macros best would be to define matching configuration in htlatex so that it knows. –  David Carlisle Jul 20 '12 at 18:51
Don't ignore errors, correct them. Also better don't use braces ({..}) to surround the argument of your code. That this works (sometimes) is an experimental feature of \lstinline which can break easily. –  Ulrike Fischer Jul 21 '12 at 10:45
@UlrikeFischer, Break in which way? I've been using that throughout the entire book that I've written. It seems it complains about code that are inside the listings.. Shouldn't it just ignore that?! –  Filip Ekberg Jul 22 '12 at 10:09
I think I narrowed it down to when I use \lstdefinelanguage and then include it with alsolanguage= it gives me these errors. –  Filip Ekberg Jul 22 '12 at 10:19
Seems it doesn't like this particular line: otherkeywords={[, ]} I want highlighting on new[], that's why I have that, but it seems like that is causing the problems. –  Filip Ekberg Jul 22 '12 at 10:25