karthink
karthink
> Would be nice to have `id` links be evaluated, too. > > I start writing my documentation for an issue/feature from a new org node, and this node often...
Just a note, buffer-local context specification (add files or buffers to context) is now possible, see https://github.com/karthink/gptel/issues/475#issuecomment-3341392365
gptel will now annotate links, and let you know via a tooltip why a link path cannot be included with the prompt. Assuming you have link tracking turned on (with...
This is a strange one, I don't know what's causing that highlighting. It doesn't appear to be any of the properties I'm adding to the overlay in `gptel-rewrite`. It should...
Thanks. I think I fixed the gptel-rewrite warnings. For the rest I would like to figure out why the byte-compiler thinks the docstrings of the `gptel-make-*` functions are too wide...
> > For the rest I would like to figure out why the byte-compiler thinks the docstrings of the `gptel-make-*` functions are too wide instead of ignoring them. Any idea?...
I agree with setting `byte-compile-docstring-max-column` -- let's set it once in `.dir-locals` instead of in every elisp file, to a value just above that generated by the cl-defstruct macros.
> I don't think setting variables in `.dir-locals.el` works with byte-compilation. I tested it out. Whether it works depends on how byte-compilation is invoked. `elisp-byte-compile-buffer` copies the buffer to a...
Let's just add it to all the files defining cl-structures, i.e. to all the backend libraries.
Thanks for the PR @pabl0!