Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-03-28 | preparing MELPA submission | jao | |
2020-08-20 | add built-in keywords and extra keywords customization | Jay Xu | |
2020-07-22 | make autodoc support the procedure defined by case-lambda. | Jay Xu | |
2020-07-20 | typo | jao | |
2020-07-20 | license and readme | jao | |
2020-07-20 | scheme load path adjustments | jao | |
2020-07-20 | files moved from original import locations | jao | |
2020-07-12 | chez: pretty printing macroexpand results.0.12 | Jay Xu | |
2020-07-11 | make chez display output and error messages. | Jay Xu | |
2020-04-19 | add extra parameter support to chez | julian herrera | |
2020-04-19 | add extra parameter support to chez implementation | julian herrera | |
2020-03-27 | Use cl-lib instead of cl | Jonas Bernoulli | |
Starting with Emacs 27 cl is fully deprecated, including at compile-time. | |||
2020-03-27 | Delete trailing whitespace | Jonas Bernoulli | |
2020-03-27 | Fix indentation | Jonas Bernoulli | |
2020-03-27 | Mark the beginning of code part of elisp libraries with Code: heading | Jonas Bernoulli | |
It's the convention and by following it we make a big step towards supporting outline navigation. The convention doesn't say much about what parts of the code are supposed to be part of that sections and what parts belong in a subsequent section. Here we put the `require' forms in this section and maybe some setup code, that's a popular approach. In most cases there was "" where we now insert "Code:". They both serve a similar purpose and we keep the former because some users depend on that for navigation. We even add this "" in libraries where it previously was missing. In some cases the permission statement was followed by a commentary, which obviously does not belong in the "Code:" section. In such cases add the conventional "Commentary:" section. | |||
2020-03-27 | Begin the summary lines of all elisp libraries with three semicolons | Jonas Bernoulli | |
It's the convention and by following it we make a big step towards supporting outline navigation. | |||
2020-01-03 | Add rudimentary Chez support for macro expansion0.11.20.11.10.11 | Aaron Marks | |
2019-12-05 | Capture stdout in ChezScheme's eval:geiser | jitwit | |
2019-02-09 | fix for geiser-chez-parameters | Jose Antonio Ortega Ruiz | |
2019-02-07 | Add geiser-chez-init-file | Luis Osa | |
Add a new customization variable for an init file to be read on startup of a Chez REPL, where user code can be defined. The usage is copied from the equivalent Racket init file, to avoid an error if the file has not been created. | |||
2018-03-29 | fix compile and load for chez | Maris Orbidans | |
2017-09-13 | simple geiser-chez--display-error0.10 | Chaos Eternal | |
2017-08-27 | more reduction on geiser:eval, add test | Chaos Eternal | |
2017-08-24 | rewritten geiser:eval to fix the following bug: | Chaos Eternal | |
when eval (make-violation) it shall return: \#<condition &violation> but previous impletement will treat it as an ERROR. | |||
2017-08-20 | Alway pretty-print for results | Chaos Eternal | |
2017-08-18 | Handle exceptions of ChezScheme and multi-value as well | Chaos Eternal | |
- Capture exceptions of ChezScheme - handles multi-value return | |||
2016-09-30 | Use (car (process-lines ...)) instead of (shell-command ...)0.9 | Jordan Brown | |
`shell-command` assumes Bourne-shell-compatible quoting, which doesn't work when the user isn't using a Bourne-compatible shell. Instead of futzing about with quoting, we can just use `process-lines` to execute a process and pass it arguments directly. | |||
2016-05-28 | fix call the chez scheme executable. | izuo | |
2016-05-02 | Chez: add rudimentary autodoc support | Peter | |
2016-04-30 | Clean-up elisp code | Peter | |
2016-04-30 | Add preliminary support for Chez Scheme | Peter | |