summaryrefslogtreecommitdiff
path: root/elisp/geiser-log.el
AgeCommit message (Collapse)Author
2024-07-06Cleanup library headersJonas Bernoulli
- In the summary line, use three dashes to separate the file name from the summary. That is the convention, which some tools depend on, and for some libraries we already did it here too. - Capitalize the first word in the summary. That is the convention, and for some libraries we already did it here too. - For libraries that have a commentary, make sure it is placed in a "Commentary:" section. - Make sure the "Code:" heading, which separates the header from the code part of the library, exists in all files.
2022-12-05Take the byte-compilers advice into accountJonas Bernoulli
2022-10-08geiser-log clean-upsjao
- geiser-log: Obsoleting some -p flags and lexical binding - geiser-eval: Ensuring logs for asynchronous retorts - geiser-debug: don't bail on no output with errors
2022-03-06Harmonizing buffer namesjao
So that now all start with *Geiser (and a space for hidden ones) and use consistent capitalization (see issue #38).
2021-12-27more lenient logging limitsjao
2021-03-07geiser-messages-mode: Don't quote lambda expressionsJonas Bernoulli
2020-12-02Declare keymaps using defvar explicitlyJonas Bernoulli
This makes it possible to re-evaluate the containing buffers without user customizations being clobbered.
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.
2019-10-12Missing require (fixes issue #285)Jose Antonio Ortega Ruiz
Seems we forgot a require while adding a new defcustom in geiser-log.
2019-09-03Add a few minor tweaks.Lockywolf
2019-09-03Fix latest chicken. Add debug level logging. Fixed typo.Lockywolf
2019-09-03Add a custom variable to scroll *geiser messages*.Lockywolf
2012-10-11WhitespaceJose Antonio Ortega Ruiz
2010-12-14Debugging aidsJose Antonio Ortega Ruiz
A couple functions to manage logs, and a fix to the definition of geiser-messages-mode: do not ever kill all local variables in a derived mode definition!
2010-11-11Partial work (connections working)Jose Antonio Ortega Ruiz
2010-10-31Informational logs disabled by defaultJose Antonio Ortega Ruiz
Set geiser-log-verbose-p to t to enable all logs. Calling geiser-show-logs with a prefix argument will do that for you.
2009-09-11BSD relicensing: elisp code.Jose Antonio Ortega Ruiz
2009-08-23Fixes for all byte-compilation warnings.Jose Antonio Ortega Ruiz
2009-02-07Elisp utilities (mostly imported from FUEL).Jose Antonio Ortega Ruiz