Naming the result of a source block












1















The following question has been asked (in slightly different form) in a comment of another answer:



Is it possible to name the results of a source block with #+NAME: foobar (or equivalently but old-style: #+TBLNAME: foobar) rather than #+RESULTS: foobar?



Example:



#+NAME: foo
#+BEGIN_SRC emacs-lisp :var alpha=2 :results value
(let* ((tol 0.1)
(alpha_1 (- 90 alpha)))
`(("angle" "symbol" "value" "max" "min") hline
("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
))
#+END_SRC

#+RESULTS: foo
| angle | symbol | value | max | min |
|-------+----------+-------+------+------|
| toe | alpha | 1 | 1.1 | 0.9 |
| c | alpha_1 | 89 | 89.1 | 88.9 |









share|improve this question



























    1















    The following question has been asked (in slightly different form) in a comment of another answer:



    Is it possible to name the results of a source block with #+NAME: foobar (or equivalently but old-style: #+TBLNAME: foobar) rather than #+RESULTS: foobar?



    Example:



    #+NAME: foo
    #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
    (let* ((tol 0.1)
    (alpha_1 (- 90 alpha)))
    `(("angle" "symbol" "value" "max" "min") hline
    ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
    ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
    ))
    #+END_SRC

    #+RESULTS: foo
    | angle | symbol | value | max | min |
    |-------+----------+-------+------+------|
    | toe | alpha | 1 | 1.1 | 0.9 |
    | c | alpha_1 | 89 | 89.1 | 88.9 |









    share|improve this question

























      1












      1








      1








      The following question has been asked (in slightly different form) in a comment of another answer:



      Is it possible to name the results of a source block with #+NAME: foobar (or equivalently but old-style: #+TBLNAME: foobar) rather than #+RESULTS: foobar?



      Example:



      #+NAME: foo
      #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
      (let* ((tol 0.1)
      (alpha_1 (- 90 alpha)))
      `(("angle" "symbol" "value" "max" "min") hline
      ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
      ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
      ))
      #+END_SRC

      #+RESULTS: foo
      | angle | symbol | value | max | min |
      |-------+----------+-------+------+------|
      | toe | alpha | 1 | 1.1 | 0.9 |
      | c | alpha_1 | 89 | 89.1 | 88.9 |









      share|improve this question














      The following question has been asked (in slightly different form) in a comment of another answer:



      Is it possible to name the results of a source block with #+NAME: foobar (or equivalently but old-style: #+TBLNAME: foobar) rather than #+RESULTS: foobar?



      Example:



      #+NAME: foo
      #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
      (let* ((tol 0.1)
      (alpha_1 (- 90 alpha)))
      `(("angle" "symbol" "value" "max" "min") hline
      ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
      ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
      ))
      #+END_SRC

      #+RESULTS: foo
      | angle | symbol | value | max | min |
      |-------+----------+-------+------+------|
      | toe | alpha | 1 | 1.1 | 0.9 |
      | c | alpha_1 | 89 | 89.1 | 88.9 |






      org-babel org-table






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 4 hours ago









      TobiasTobias

      15.2k11035




      15.2k11035






















          1 Answer
          1






          active

          oldest

          votes


















          2














          One can add the following lines below unnamed source blocks (with bar replaced by the intended table name):



          #+NAME: bar
          #+RESULTS:
          ||


          The line with #+name: bar is preserved after the evaluation of the source block and || is replaced with the resulting table.



          Note, that the name bar really names the table and not the source block.
          That has the following consequences (probably among others I am not aware of at the moment):




          1. If you refer to the table name in the header arguments of another source block, say buh, then the bar source block is not reevaluated when buh is evaluated. The table is not updated but taken as argument for buh as it is.

            That is usually more an disadvantage than an advantage.

            One can call org-babel-execute-buffer to get correctly updated results.


          2. If the source block returns a string containing the formatted org-table rather than table data referring to the source block name in header variables gets you the string and not the table data. That is most often unwanted.

            In that case it is a big advantage that you can alternatively refer to the resulting table by its name.



          If the source block is named, e.g., foo replace #+RESULTS: with #+RESULTS: foo.



          Example:



          #+NAME: foo
          #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
          (let* ((tol 0.1)
          (alpha_1 (- 90 alpha)))
          `(("angle" "symbol" "value" "max" "min") hline
          ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
          ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
          ))
          #+END_SRC

          #+TBLNAME: bar
          #+RESULTS: foo
          | angle | symbol | value | max | min |
          |-------+----------+-------+------+------|
          | toe | alpha | 1 | 1.1 | 0.9 |
          | c | alpha_1 | 89 | 89.1 | 88.9 |

          #+CALL: foo(alpha=bar[2,3])

          #+NAME: buh
          #+RESULTS:
          | angle | symbol | value | max | min |
          |-------+----------+-------+--------------------+-------------------|
          | toe | alpha | 1.1 | 1.2000000000000002 | 1.0 |
          | c | alpha_1 | 88.9 | 89.0 | 88.80000000000001 |


          The example demonstrates the update problem. The header variable alpha had the value 1 at the first evaluation of foo. Afterwards the value was changed to 2 but the source block foo was not evaluated again.

          The evaluation of the #+CALL statement does use the table value 1.1 at cell 2,3 directly without reevaluation of foo.






          share|improve this answer


























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "583"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f48972%2fnaming-the-result-of-a-source-block%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            One can add the following lines below unnamed source blocks (with bar replaced by the intended table name):



            #+NAME: bar
            #+RESULTS:
            ||


            The line with #+name: bar is preserved after the evaluation of the source block and || is replaced with the resulting table.



            Note, that the name bar really names the table and not the source block.
            That has the following consequences (probably among others I am not aware of at the moment):




            1. If you refer to the table name in the header arguments of another source block, say buh, then the bar source block is not reevaluated when buh is evaluated. The table is not updated but taken as argument for buh as it is.

              That is usually more an disadvantage than an advantage.

              One can call org-babel-execute-buffer to get correctly updated results.


            2. If the source block returns a string containing the formatted org-table rather than table data referring to the source block name in header variables gets you the string and not the table data. That is most often unwanted.

              In that case it is a big advantage that you can alternatively refer to the resulting table by its name.



            If the source block is named, e.g., foo replace #+RESULTS: with #+RESULTS: foo.



            Example:



            #+NAME: foo
            #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
            (let* ((tol 0.1)
            (alpha_1 (- 90 alpha)))
            `(("angle" "symbol" "value" "max" "min") hline
            ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
            ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
            ))
            #+END_SRC

            #+TBLNAME: bar
            #+RESULTS: foo
            | angle | symbol | value | max | min |
            |-------+----------+-------+------+------|
            | toe | alpha | 1 | 1.1 | 0.9 |
            | c | alpha_1 | 89 | 89.1 | 88.9 |

            #+CALL: foo(alpha=bar[2,3])

            #+NAME: buh
            #+RESULTS:
            | angle | symbol | value | max | min |
            |-------+----------+-------+--------------------+-------------------|
            | toe | alpha | 1.1 | 1.2000000000000002 | 1.0 |
            | c | alpha_1 | 88.9 | 89.0 | 88.80000000000001 |


            The example demonstrates the update problem. The header variable alpha had the value 1 at the first evaluation of foo. Afterwards the value was changed to 2 but the source block foo was not evaluated again.

            The evaluation of the #+CALL statement does use the table value 1.1 at cell 2,3 directly without reevaluation of foo.






            share|improve this answer






























              2














              One can add the following lines below unnamed source blocks (with bar replaced by the intended table name):



              #+NAME: bar
              #+RESULTS:
              ||


              The line with #+name: bar is preserved after the evaluation of the source block and || is replaced with the resulting table.



              Note, that the name bar really names the table and not the source block.
              That has the following consequences (probably among others I am not aware of at the moment):




              1. If you refer to the table name in the header arguments of another source block, say buh, then the bar source block is not reevaluated when buh is evaluated. The table is not updated but taken as argument for buh as it is.

                That is usually more an disadvantage than an advantage.

                One can call org-babel-execute-buffer to get correctly updated results.


              2. If the source block returns a string containing the formatted org-table rather than table data referring to the source block name in header variables gets you the string and not the table data. That is most often unwanted.

                In that case it is a big advantage that you can alternatively refer to the resulting table by its name.



              If the source block is named, e.g., foo replace #+RESULTS: with #+RESULTS: foo.



              Example:



              #+NAME: foo
              #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
              (let* ((tol 0.1)
              (alpha_1 (- 90 alpha)))
              `(("angle" "symbol" "value" "max" "min") hline
              ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
              ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
              ))
              #+END_SRC

              #+TBLNAME: bar
              #+RESULTS: foo
              | angle | symbol | value | max | min |
              |-------+----------+-------+------+------|
              | toe | alpha | 1 | 1.1 | 0.9 |
              | c | alpha_1 | 89 | 89.1 | 88.9 |

              #+CALL: foo(alpha=bar[2,3])

              #+NAME: buh
              #+RESULTS:
              | angle | symbol | value | max | min |
              |-------+----------+-------+--------------------+-------------------|
              | toe | alpha | 1.1 | 1.2000000000000002 | 1.0 |
              | c | alpha_1 | 88.9 | 89.0 | 88.80000000000001 |


              The example demonstrates the update problem. The header variable alpha had the value 1 at the first evaluation of foo. Afterwards the value was changed to 2 but the source block foo was not evaluated again.

              The evaluation of the #+CALL statement does use the table value 1.1 at cell 2,3 directly without reevaluation of foo.






              share|improve this answer




























                2












                2








                2







                One can add the following lines below unnamed source blocks (with bar replaced by the intended table name):



                #+NAME: bar
                #+RESULTS:
                ||


                The line with #+name: bar is preserved after the evaluation of the source block and || is replaced with the resulting table.



                Note, that the name bar really names the table and not the source block.
                That has the following consequences (probably among others I am not aware of at the moment):




                1. If you refer to the table name in the header arguments of another source block, say buh, then the bar source block is not reevaluated when buh is evaluated. The table is not updated but taken as argument for buh as it is.

                  That is usually more an disadvantage than an advantage.

                  One can call org-babel-execute-buffer to get correctly updated results.


                2. If the source block returns a string containing the formatted org-table rather than table data referring to the source block name in header variables gets you the string and not the table data. That is most often unwanted.

                  In that case it is a big advantage that you can alternatively refer to the resulting table by its name.



                If the source block is named, e.g., foo replace #+RESULTS: with #+RESULTS: foo.



                Example:



                #+NAME: foo
                #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
                (let* ((tol 0.1)
                (alpha_1 (- 90 alpha)))
                `(("angle" "symbol" "value" "max" "min") hline
                ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
                ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
                ))
                #+END_SRC

                #+TBLNAME: bar
                #+RESULTS: foo
                | angle | symbol | value | max | min |
                |-------+----------+-------+------+------|
                | toe | alpha | 1 | 1.1 | 0.9 |
                | c | alpha_1 | 89 | 89.1 | 88.9 |

                #+CALL: foo(alpha=bar[2,3])

                #+NAME: buh
                #+RESULTS:
                | angle | symbol | value | max | min |
                |-------+----------+-------+--------------------+-------------------|
                | toe | alpha | 1.1 | 1.2000000000000002 | 1.0 |
                | c | alpha_1 | 88.9 | 89.0 | 88.80000000000001 |


                The example demonstrates the update problem. The header variable alpha had the value 1 at the first evaluation of foo. Afterwards the value was changed to 2 but the source block foo was not evaluated again.

                The evaluation of the #+CALL statement does use the table value 1.1 at cell 2,3 directly without reevaluation of foo.






                share|improve this answer















                One can add the following lines below unnamed source blocks (with bar replaced by the intended table name):



                #+NAME: bar
                #+RESULTS:
                ||


                The line with #+name: bar is preserved after the evaluation of the source block and || is replaced with the resulting table.



                Note, that the name bar really names the table and not the source block.
                That has the following consequences (probably among others I am not aware of at the moment):




                1. If you refer to the table name in the header arguments of another source block, say buh, then the bar source block is not reevaluated when buh is evaluated. The table is not updated but taken as argument for buh as it is.

                  That is usually more an disadvantage than an advantage.

                  One can call org-babel-execute-buffer to get correctly updated results.


                2. If the source block returns a string containing the formatted org-table rather than table data referring to the source block name in header variables gets you the string and not the table data. That is most often unwanted.

                  In that case it is a big advantage that you can alternatively refer to the resulting table by its name.



                If the source block is named, e.g., foo replace #+RESULTS: with #+RESULTS: foo.



                Example:



                #+NAME: foo
                #+BEGIN_SRC emacs-lisp :var alpha=2 :results value
                (let* ((tol 0.1)
                (alpha_1 (- 90 alpha)))
                `(("angle" "symbol" "value" "max" "min") hline
                ("toe" "\alpha" ,alpha ,(+ alpha tol) ,(- alpha tol))
                ("c" "\alpha_1" ,alpha_1 ,(+ alpha_1 tol) ,(- alpha_1 tol))
                ))
                #+END_SRC

                #+TBLNAME: bar
                #+RESULTS: foo
                | angle | symbol | value | max | min |
                |-------+----------+-------+------+------|
                | toe | alpha | 1 | 1.1 | 0.9 |
                | c | alpha_1 | 89 | 89.1 | 88.9 |

                #+CALL: foo(alpha=bar[2,3])

                #+NAME: buh
                #+RESULTS:
                | angle | symbol | value | max | min |
                |-------+----------+-------+--------------------+-------------------|
                | toe | alpha | 1.1 | 1.2000000000000002 | 1.0 |
                | c | alpha_1 | 88.9 | 89.0 | 88.80000000000001 |


                The example demonstrates the update problem. The header variable alpha had the value 1 at the first evaluation of foo. Afterwards the value was changed to 2 but the source block foo was not evaluated again.

                The evaluation of the #+CALL statement does use the table value 1.1 at cell 2,3 directly without reevaluation of foo.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 3 hours ago

























                answered 4 hours ago









                TobiasTobias

                15.2k11035




                15.2k11035






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Emacs Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f48972%2fnaming-the-result-of-a-source-block%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    What other Star Trek series did the main TNG cast show up in?

                    Berlina muro

                    Berlina aerponto