Daniel Bausch <[email protected]> writes: >>> (org-babel-call "foo" :var "a" (org-babel-ref-resolve "tbl[1,1]")) >> >> What if someone wants to pass two variables? > > Obviously :var can be repeated (as in the header args). > > (org-babel-call "foo" pos1 pos2 :var "a" "bar" :var "b" 12345)
This can work, yes. >>> Regarding your comments on the complementary function >>> `org-babel-result`: >>> ... >> Could you elaborate on what you expect to happen when there is no cached >> result in buffer? > > Then it returns nil. It's meant to be really very intuitive. > > Contract: Just take the currently materialized result of a named source > block as it is from the buffer/file. Having something like :cache 'only would make sense for me then. >> Before we go too far with LLM-generated patches, please note that GNU >> projects, including Emacs, cannot accept LLM-generated patches as of >> now. This is a temporary policy that will be in place while GNU is >> consulting with lawyers on the implications of LLM code on GPLv3 >> license. I hope that GNU can produce the final policy in the coming >> months. > > I got this and I'm in the process of re-writing everything from scratch > by hand. I feel, not having a good option for non-trivial orchestration > is a serious gap in Babel, which is why I'm committed to substantially > invest time in that project. > > As I worked solely spec-driven and test-driven up to v4, I really never > looked closely on the generated code. The most intense "conversation" I > had with the model about the code was on the comments and docstrings. > > So, my plan is to deliver a clean-room implementation of the functions' > contract soon. As long as you confirm that it is your own code, there should be no problem. > I will run the AI generated tests against it, to reassure that I did at > least as well as the AI, if that's ok. I will deliver clean-room > hand-written tests in the patch though. You can use AI to search for bug, or check things in any other way. That's not disallowed as it has no relation to copyright. How you analyze your code is your business - we do not dictate which OS you use or which editor. > Would that meet Emacs' policies? I think yes. > I already asked for FSF assigments but did not get a reply yet. If there is no reply withing one month, let me know - I will bump FSF staff. -- 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>
