Naming the result of a source block Planned maintenance scheduled April 17/18, 2019 at...

What is Wonderstone and are there any references to it pre-1982?

What is the role of the transistor and diode in a soft start circuit?

Using audio cues to encourage good posture

What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?

Book where humans were engineered with genes from animal species to survive hostile planets

Output the ŋarâþ crîþ alphabet song without using (m)any letters

Why did the rest of the Eastern Bloc not invade Yugoslavia?

Why do people hide their license plates in the EU?

Dating a Former Employee

Why do we bend a book to keep it straight?

Can an alien society believe that their star system is the universe?

When a candle burns, why does the top of wick glow if bottom of flame is hottest?

Seeking colloquialism for “just because”

Can a USB port passively 'listen only'?

What does this icon in iOS Stardew Valley mean?

Sci-Fi book where patients in a coma ward all live in a subconscious world linked together

Echoing a tail command produces unexpected output?

How to align text above triangle figure

What's the purpose of writing one's academic biography in the third person?

What is a non-alternating simple group with big order, but relatively few conjugacy classes?

Why is "Consequences inflicted." not a sentence?

When do you get frequent flier miles - when you buy, or when you fly?

How to bypass password on Windows XP account?

Using et al. for a last / senior author rather than for a first author



Naming the result of a source block



Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Can I use elisp code make a table and insert a variable into cell?Indentation of source block resultFontify result of source block in org-modeHow to have org-babel treat the first line of a table result as a header?Org-mode: pipe source block output as stdin to next source blockHow to append header arguments to result code src block?How to insert a result of an org-mode source block as part of the document's syntax?Org-mode: Get src block result inside block definition for clocktableget contents of source blockCatching warnings from sh source blockHow to generate the result file for dot source block and include it with another path in org-mode?












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

                    ORA-01691 (unable to extend lob segment) even though my tablespace has AUTOEXTEND onORA-01692: unable to...

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    Circunscripción electoral de Guipúzcoa Referencias Menú de navegaciónLas claves del sistema electoral en...