phil/gptel-got
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.org

Browse source
This commit is contained in:
Phil Bajsicki 2025-04-15 01:48:47 +02:00
parent 4b650dfd84
commit ca1fa23ca9
2 changed files with 39 additions and 39 deletions

10
README.org
View file

@ -125,7 +125,7 @@ Stuff, headers, etc.
These tools are primarily concerned with Emacs, Emacs Lisp, and files-or-buffers.
**** exec_lisp
**** eval
Dangerous, but occasionally useful for pure chaos and amusement...
I would like to say. But in actuality, especially with the 'smarter' models, they can surprise with the varied approaches they have to problem-solving.
@ -148,7 +148,7 @@ Highly not recommended, but sometimes an LLM can pull a rabbit out of pure entro
:category "emacs")
#+end_src
**** emacs-list-buffers
**** list-buffers
I wanted the assistant to have an easier time finding my files and buffers, and this has proven to be a great choice. I have yet to manage to get rid of the =:args=, but having them optional/ do nothing works well enough.
The rationale behind using ~ibuffer~ is the same as with dired. They both display a lot of data, densely. So instead of trying to use some workaround with ~buffer-file-name~ or other functions, I'd rather just grab a 'text capture' of the same UI I'm looking at, and call it a day.
@ -170,7 +170,7 @@ Seems to be one of the most reliable tools in the basket... mostly because
:optional t))
:category "emacs")
#+end_src
**** dired-list
**** dired
See above, same reasoning. There's very little reason to use the ~directory-files~ function for this (as in another tool I saw.) The reason is, ~directory-files~ doesn't provide nearly as much information about the items in that directory. Not even a distinction between files and directories.
~directory-files-and-attributes~ might, but I personally found its output horrendous to read, and still somehow more expensive context-wise than just plain ol' dired.
@ -196,7 +196,7 @@ Be sure to customize the function to point to your org directory, if you wish. I
:category "filesystem")
#+end_src
**** emacs-find-buffer-visiting
**** find-buffer-visiting
#+begin_src elisp
(gptel-make-tool
:function (lambda (filename)
@ -208,7 +208,7 @@ Be sure to customize the function to point to your org directory, if you wish. I
:description "The filename to compare to open buffers."))
:category "org-mode")
#+end_src
**** emacs-find-file-noselect
**** find-file-noselect
Continuation from above. Open a file into a buffer for processing. Onec it's found by dired-list.
#+begin_src elisp
(gptel-make-tool