Gregory's Server@abcdw
1. Yes, I usually have the info manual on the side but it is still annoying to having to go and find a module for a function.
2. Yes, I rely on the autocompletion to find useful functions, but sometimes if a module is not part of "base guile" It does not work unless I load the module first.
3. Yes I understand that a debugger is a long way to go. I meant some commands that could help with debugging, like displaying the locals or backtrace by default or something similar.
|
Top-level
3 comments
2. For example call geiser-doc-symbol-at-point and try to find the string-match function. It requires (ice-9 regex) to already be loaded. I was not familiar with the sourcehut platform, I would be happy to collaborate (I need to learn this email workflow) I have thought about using geiser-eval--send to eval some modules in a separate buffer, and also to somehow extract the list of symbols out of the modules, a hacky solution for points 1 and 2. I will explore this.  @mirkoh the currently implemented completion is module-aware and shows only symbols available in module environment (and it seems to be a proper OOTB behavior). Theoretically, we can traverse all the modules in load-path and collect all the symbols available and provide a list of them via arei-find-symbol or something similiar. It can make sense for some use cases (to find a function without importing module upfront for example). |
@mirkoh
1. No such thing yet, completion is bare-bone at the moment, but it's open to extension.
2. Show the guile snippet or pseude code please, it can help me understand better what you mean.
3. At the momnet there are no debugging capabilities except printing a backtrace and exception.
If you have any ideas on how to implement particular functionality (the code or just the overall idea) drop a message on rde-discuss or rde-devel:
https://lists.sr.ht/~abcdw/