Alexander Pann

I've changed the wording a bit, but yes, this is the actual use case. I am not sure if my proposed change is really a good idea, and I also...

I'll close the ticket myself. If there is a need for this use case, it can be implemented as an intention in the project that needs this.

I am closing this issue because there are too many open issues for anybody to find this issue.

The issue is that the gap between "something" and "as any" is considered by the layouter but not by the size calculation of the box.

> Why is it necessary to hardcode these references here? This is explained in the comment: There would be a cyclic dependency between `org.iets3.core.expr.typetags.units.si` and `org.iets3.core.expr.typetags.units.si` which is disallowed in...

On a side note: I really question the way we handle special characters in `IValidNamedConcept`. The current handling is awful. We already have an extension point. Why not have a...

Yes, they would become obsolete but we can still use the information. You could read the return type of the existing two methods and add the corresponding character mappings to...

Let's close this ticket. I don't understand it and it is probably obsolete.

> @alexanderpann and @sergej-koscejev Thanks very much for the fix. I tried it and it works great. Should we create an issue for the broken optional cell in the grammar...

The optional cell uses [side transformations](https://www.jetbrains.com/help/mps/transformation-menu-language.html#sidetransformations). Normally they work, but this editor uses `punctuation-left:true` and `punctuation-right:true` in some cells which disallows the cursor at those positions. As a result, the...