| Did you know ... | Search Documentation: |
| Title for pldoc(default) |
[Dec 2 2025]
__auto_type[Nov 30 2025]
objcopy, add the state as an
ELF section. This makes the system a valid ELF executable on which
all ELF tools work normally.zip(true) to create a clean .zip file.[Nov 24 2025]
max_text to exclude ellipsis.
As we already exclude the quotes and escape sequences, excluding the
ellipsis is more consistent. After remarks by Joachim Schimpf.[Nov 23 2025]
swipl-win[Nov 21 2025]
max_depth(+Depth) to use Unicode …
If the encoding of the output supports Unicode. Otherwise the ASCII
sequence ... is emitted.max_text(+Length) for quoted output.[Nov 20 2025]
max_text(+Length) Actually
called text_max in the proposal. Considering all other options
and flags are named `max_*`, I think this should change.
This commit only implements this option for unquoted atoms and strings.
truncated(-Bool). Bool
is unified to true if the term has been truncated due to the
max_depth option.portable(Bool)On Windows, stream timeout only works for sockets. [Nov 19 2025]
[Nov 24 2025]
[Nov 23 2025]
# as anonymous tag.[Dec 2 2025]
header(true), EOF resulted in a warning that the thread died
on failure.[Nov 30 2025]
[Nov 26 2025]
[Nov 25 2025]
header(true) option[Nov 23 2025]
# This
used to be a variable. Following discussion about dicts in the PIP
meetings, this is part of getting rid of unbound tags and use #
as anonymous (dynamic) dict.[Dec 2 2025]
syntax_table->keywords to register known keywords for
a syntax[Dec 1 2025]
text_buffer->for_all_comments Replaced by
text_buffer->for_all_syntax, which qualifies additional syntax
types. Currently only quoted material.syntax_table->prolog: bool replaced by
syntax_table->languagelsp_offset(line,character) --> offset Translate
position in LSP notation to an offset.text_buffer<-lsp_column Produces the character field
of an LSP range start/end. This is the position inside the line in
UTF-16 code points.[Nov 29 2025]
editor->align_line to avoid modifications if alignment
is already satisfied.[Nov 28 2025]
[Nov 24 2025]
text_buffer to allow forwarding changes incrementally
This implements methods to generate LSP (Language Server Protocol)
compatible incremental change events. The basic method is
text_buffer<-lsp_changes, which returns a chain of text_change
objects that provide the changed range and replacement text.