karthink

> In a nutshell, allow content to be included in a chat by reference, via links in the conversation, to "anything that makes sense, so long as it's text", and...

Question 1: Because users can have lots of links in regular Org buffers, which are almost always intended for purposes other than sending data to the LLM. Question 3: To...

> For example, I often use an Org document as a reference for prose and content material, and would not want to have links translated into media Yes, this is...

Done. Links to plain-text files in chat buffers are now followed, and their contents included in the request. For example, suppose you have this text file named `remap.yaml`: ``` yaml...

I have two questions about this feature. 1. Should `gptel-track-media` be renamed to something more appropriate, like `gptel-track-links`? 2. How should links to directories be handled? Currently they are ignored.

> - Are all links supported? If use a TRAMP link or FTP, is that handled? Only `file:` links are handled, but all `file:` links are handled. So TRAMP links...

> More generally, is there any reasonable default way (without custom link types) to link to a buffer? I'm not aware of any, but if there were, that could be...

> Another way of doing this might be to define a org link alias for "file:" which > perhaps could be called "gptel:". > > It would do exactly the...

> Can't font-lock highlight rules be added without this marker? Yes, you can add a font-lock rule that adds a little check mark at the end of links that are...

> That makes sense, just `@` is not very specific, even if not used for anything > right now in org/markdown. It could easily be something else, `@@file`, or >...