emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Minshall <minshall@umich.edu>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>
Cc: emacs-orgmode@gnu.org, Eric S Fraga <e.fraga@ucl.ac.uk>
Subject: Re: How do you name your code blocks?
Date: Wed, 17 Feb 2021 09:56:45 +0300	[thread overview]
Message-ID: <1494323.1613545005@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Tue, 16 Feb 2021 20:27:54 -0500." <87sg5vlbz9.fsf@gmail.com>

hi, Rodrigo,

thanks.  i understand.  we all like "int i;" to be independent in
separate functions (as it were).  right now, names of source blocks are
global to the .org file, and i don't suspect that will (or should)
change.

i apologize for bringing it up, but the one thing that jumps out at the
programmer part of me is that the python blocks in your code don't
"know" what main.txt actually contains when they are executed, as there
is no dependency on the correct "create-file" source block.  possibly,
though, if you created some dummy :var (on the python "begin_src" lines)
to express this dependency, it would help?  or, maybe it doesn't really
matter?

cheers, Greg


  reply	other threads:[~2021-02-17  6:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 19:18 How do you name your code blocks? Rodrigo Morales
2021-02-16  4:53 ` Greg Minshall
2021-02-17  1:21   ` Rodrigo Morales
2021-02-16 12:03 ` Eric S Fraga
2021-02-17  1:27   ` Rodrigo Morales
2021-02-17  6:56     ` Greg Minshall [this message]
2021-02-17 20:31       ` Rodrigo Morales
2021-02-17  1:58 ` Kevin M. Stout
2021-02-17  9:57   ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1494323.1613545005@apollo2.minshall.org \
    --to=minshall@umich.edu \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=moralesrodrigo1100@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).