Philipp Imhof

> * Make the necessary changes so that the input boxes are easier to place, for example with a display:inline-block. This method becomes the default. Very good. I will go...

> > it's not really the line in many cases > > What the error message refers to is, in reality, the "statement" number Yes, exactly. And in many cases...

> So in order to find the line range where the error happened, one has to go back and match the problematic expression with the entire input. Oh, and I...

I suggest we do the following: * have statement numbers instead of line numbers in a "gutter" next to the editor; basically like you did in your first idea where...

Hello Dominique No worries at all, I haven't startet this project yet; I am still working on the edit form refactoring. I look forward to seeing a collection of examples....

I haven't decided yet. It is among several possibilities I am currently evaluating. I will keep you posted, as soon as I start the development.

Similar to what I wrote in #45, I will change the syntax in order to allow placing parts with `inline-block` by using `{#1|inline}` via their placeholders. That means absolutely no...

Yes, that is all pretty straightforward with divs; that's more or less what I had, as well. It's the big pro of this approach. The con, on the other hand,...

How could I miss that... Probably seen too many fiddles in the last few days. That would be a solution without line numbers then. Certainly easier to do and to...

With the progress made on replacing the entire parsing and evaluation engine of the Formulas Question, we will soon have better and more precise error reporting. Almost all error messages...