summaryrefslogtreecommitdiff
path: root/elisp/geiser-capf.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-10-13expect completion-in-region functions to preserve current bufferjao
see discussion in issue #56
2022-10-13autodoc: correctly display docsigs for in-region completions (#56)jao
we were doing it really wrong: first, by not setting the evaluation environment when things are computed outside the original buffer (the completion in region case for consult and the likes, where the current buffer is the minibuffer) and, to add insult to injury, by not waiting for a response from the scheme side! actually waiting can make things a tad laggy when the scheme is not as fast as, say, chez and there are lots of completions (if one uses completion-in-region; for pop ups like company it's fine), so i've also added a flag, geiser-autodoc-use-docsig, to turn the functionality off.
2022-10-10fix for completion-for-modulejao
We were calling an undefined function... not too many people using the functionality (or geiser at all :)).
2022-08-20fix: don't override user's capfs (see issue #50)jao
2022-04-23geiser-capf: new module to break cyclic dependenciesjao