summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-04-21Use new implementation extension declarator0.16jao
2021-04-21whitespacejao
2021-04-05fix: auto-activate implementation0.14jao
2021-03-28emacs dependency0.13jao
2021-03-28compilation warnings (unused variable)jao
2021-03-28Typojao
2021-03-28preparing MELPA submissionjao
2020-08-20add built-in keywords and extra keywords customizationJay Xu
2020-07-22make autodoc support the procedure defined by case-lambda.Jay Xu
2020-07-20typojao
2020-07-20license and readmejao
2020-07-20scheme load path adjustmentsjao
2020-07-20files moved from original import locationsjao
2020-07-12chez: pretty printing macroexpand results.0.12Jay Xu
2020-07-11make chez display output and error messages.Jay Xu
2020-04-19add extra parameter support to chezjulian herrera
2020-04-19add extra parameter support to chez implementationjulian herrera
2020-03-27Use cl-lib instead of clJonas Bernoulli
Starting with Emacs 27 cl is fully deprecated, including at compile-time.
2020-03-27Delete trailing whitespaceJonas Bernoulli
2020-03-27Fix indentationJonas Bernoulli
2020-03-27Mark the beginning of code part of elisp libraries with Code: headingJonas 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-27Begin the summary lines of all elisp libraries with three semicolonsJonas Bernoulli
It's the convention and by following it we make a big step towards supporting outline navigation.
2020-01-03Add rudimentary Chez support for macro expansion0.11.20.11.10.11Aaron Marks
2019-12-05Capture stdout in ChezScheme's eval:geiserjitwit
2019-02-09fix for geiser-chez-parametersJose Antonio Ortega Ruiz
2019-02-07Add geiser-chez-init-fileLuis 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-29fix compile and load for chezMaris Orbidans
2017-09-13simple geiser-chez--display-error0.10Chaos Eternal
2017-08-27more reduction on geiser:eval, add testChaos Eternal
2017-08-24rewritten 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-20Alway pretty-print for resultsChaos Eternal
2017-08-18Handle exceptions of ChezScheme and multi-value as wellChaos Eternal
- Capture exceptions of ChezScheme - handles multi-value return
2016-09-30Use (car (process-lines ...)) instead of (shell-command ...)0.9Jordan 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-28fix call the chez scheme executable.izuo
2016-05-02Chez: add rudimentary autodoc supportPeter
2016-04-30Clean-up elisp codePeter
2016-04-30Add preliminary support for Chez SchemePeter
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-27 13:05:07 +0000