Markus Triska

> Do you have an example of how it would look? Yes indeed, the SICStus info pages are a good example, and also the Emacs and Elisp info pages. For...

Please see the discussion in #3155. As mentioned there, I think an **`info`** page would be ideal, it is a huge plus of (for example) the SICStus documentation that it can...

In case anyone is interested in such a feature, I would much prefer first having a discussion about this topic. For instance, what is the relation to **meta-structures** mentioned in...

> ... using a directive ... One small point regarding this part of the comment: We can set the flag also at runtime with the *predicate* `set_prolog_flag/2` (instead of with...

It seems OK at first sight? One attribute is already attached, a variable becomes the same as another variable, and a new attribute must be taken into account?

Where does the number 1200 come from? 6.3.6 states: 6.3.6 Compound terms - curly bracketed term A term with principal functor '{}'/1 can also be expressed by enclosing its argument...

This is an issue resulting from the current naive traversal of **all Unicode code points** with `between/3`: https://github.com/mthom/scryer-prolog/blob/dc05526c71169a88f90ba91bbbb72cad450782b0/src/lib/charsio.pl#L155 Until this is resolved in the library, it is conceptually straight-forward to...

To quickly trace down the problem, apply declarative reasoning: **Generalize** the example to find shorter fragments that still exhibit the issue. You can generalize the code and query by using...

If such use cases arise, please post more about them, there may be better ways to solve them than simply adding the first predicate that seems useful in such a...

`Lis` is a dedicated type with its own tag on the heap, and `functor!` does not create a structure of that type even though it could when the argument is...