Laurence von Bottorff <[email protected]> writes: > I just spent a few hours of my precious mortal life going round and round > with Gemini trying to get ob-sml to work properly. As Gemini pointed out, > the ob-sml.el was essentially abandonware, last updated well over ten years > ago, and very antiquated. We (i.e., Gemini; my Lisp skills are at *The > Little Lisper *level) made improvements that have sml in babel code blocks > working and looking much better on the latest sml 110.99.9. Could I submit > this? If so, how do I do that? Never done before...
Note that ob-sml is not a part of Org mode itself. It is a third-party package. Also, if you are talking about https://github.com/swannodette/ob-sml/blob/master/ob-sml.el, that's also a pretty trivial package. And, since it is licensed under GPL, you can fork it and revive the development. All in your hands. With or without LLM. > At some point I'd like to tackle Prolog, which is also abysmal. And > ob-haskell doesn't play well with latest haskel-mode; I have to use a 10 yo > version. Your thoughts on all the ob-<your obscure language here>? If you know bugs in ob-haskell (which *is* a part of Org mode), feel free to report them. Whether you can send LLM-generated patches, it depends. You definitely cannot send complex patches. LLM-produced code is likely public domain, and adding non-trivial amount of public domain code may have implications on GPL licensing. Until GNU clarifies on these implications with lawyers, we are putting large LLM contributions on hold. The best I can suggest here is turning patches into third-party packages - those are definitely not restricted in terms of what you can use or not (all the legal burden will be on you, the author). You likely (but I still need to confirm), can send LLM-generated patches that are no more than 15 lines of code, or more than 15 lines of code, but make trivial changes. Do note that even if you do send LLM patches, please, please review them first. Otherwise, you will put a burden to review LLM code on me (the maintainer), potentially wasting my limited time that could be spent on something more productive. Even better, especially if you are not familiar with Org code or Elisp, try to write yourself first - this will be a great opportunity to learn Emacs, Elisp, and Org mode. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
