summaryrefslogtreecommitdiff
path: root/elisp/geiser-compile.el
AgeCommit message (Collapse)Author
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.
2018-03-19A prefix for geiser-compile-current-buffer to restart it allJose Antonio Ortega Ruiz
Okay, i must confess it's sometimes handy to restart the REPL before compiling a file (the proverbial clean slate and all). And we already have geiser-restart-repl, so combining the two things when C-u happens was not really difficult.
2016-12-03Bug fix: expanding file name at the right timeJose Antonio Ortega Ruiz
We were expanding the path of files to be loaded at the wrong place in the wrong way. This should be better and address bug #196.
2016-06-11Cleanups to the show/jump debug buffer messJose Antonio Ortega Ruiz
Let's see if i finally got this right...
2013-02-07Accepting ~ in geiser-add-to-load-pathJose Antonio Ortega Ruiz
2012-10-11WhitespaceJose Antonio Ortega Ruiz
2011-02-03New geiser-add-to-load-path, just for Guile right nowJose Antonio Ortega Ruiz
As per Andy's request. Adding it to Racket (and to the user manual), shouldn't be difficult).
2010-12-28Leaner autodoc cacheJose Antonio Ortega Ruiz
We cannot consistently maintain a local cache, because of re-evaluations of external symbols will go unnoticed. The new strategy (remembering only the latest signatures) mostly works, although it introduces a bit of extra flickering every now and then. A global cache is perhaps worth considering.
2010-12-28Finer grained maintenance of autodoc's cacheJose Antonio Ortega Ruiz
2010-10-30Elisp: more flexible parsing of :eval and :ge formsJose Antonio Ortega Ruiz
This allows the implementation decide the concrete structure of the code sent to the REPL. For instance, it doesn't need to be a single s-expression, and argument order can be re-arranged.
2010-09-06Autodoc: clean cache upon evaluationJose Antonio Ortega Ruiz
2009-09-11BSD relicensing: elisp code.Jose Antonio Ortega Ruiz
2009-04-28Fixes for eval/compilation error display.Jose Antonio Ortega Ruiz
2009-02-24Partial support for stack trace display.Jose Antonio Ortega Ruiz
2009-02-21Correct stack in load/compile file retorts.Jose Antonio Ortega Ruiz
2009-02-21Capture backtrace. Fix load/compile from Emacs.Jose Antonio Ortega Ruiz
2009-02-17Separate commands for evaluation and compilation.Jose Antonio Ortega Ruiz
2009-02-13Small improvements.Jose Antonio Ortega Ruiz
2009-02-12Edit symbol at point for programs.Jose Antonio Ortega Ruiz
2009-02-11README stuff.Jose Antonio Ortega Ruiz
2009-02-11Load file commands.Jose Antonio Ortega Ruiz
2009-02-11Compile file.Jose Antonio Ortega Ruiz