6ba78769a5
* lisp/tla+-mode.el (tla+-tlc-depth): tune depth parameter, default to 1000 now. (tla+-tlc-workers): tune worker threads (at least 2 threads should be used by default) (tla+-dot-convert, tla+-dot-binary): dot(1) customization variables. (tla+-run-dot): elisp function to run dot(1) and convert the state graph to a PNG file (tla+-run-model): automatically generate the PNG output file, change the window handling. It seems better to only show the tlc buffer output once (when it is a newly created buffer). The user may kill it, or arrange it in such a way that the output can be read by another tlc model check run. Also: set the bufffer to readonly. (tlc-widget-example): remove the cfgname; seems that the lambda expressions do not see the cfgname anyway so I have to reconstruct it. * ChangeLog: add a changelog file
23 lines
859 B
Plaintext
23 lines
859 B
Plaintext
2020-08-02 Christian Barthel <bch@online.de>
|
|
|
|
* lisp/tla+-mode.el (tla+-tlc-depth): tune depth
|
|
parameter, default to 1000 now.
|
|
(tla+-tlc-workers): tune worker threads (at least
|
|
2 threads should be used by default)
|
|
(tla+-dot-convert, tla+-dot-binary): dot(1)
|
|
customization variables.
|
|
(tla+-run-dot): elisp function to run dot(1) and
|
|
convert the state graph to a PNG file
|
|
(tla+-run-model): automatically generate the PNG
|
|
output file, change the window handling. It
|
|
seems better to only show the tlc buffer output
|
|
once (when it is a newly created buffer). The
|
|
user may kill it, or arrange it in such a way
|
|
that the output can be read by another tlc model
|
|
check run. Also: set the bufffer to readonly.
|
|
(tlc-widget-example): remove the cfgname; seems
|
|
that the lambda expressions do not see the cfgname
|
|
anyway so I have to reconstruct it.
|
|
|
|
|