emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rodrigo Morales <moralesrodrigo1100@gmail.com>
To: emacs-orgmode@gnu.org
Subject: How do you name your code blocks?
Date: Mon, 15 Feb 2021 14:18:17 -0500	[thread overview]
Message-ID: <87wnv9b0na.fsf@gmail.com> (raw)

I think this question is aimed to people which have Org Mode files
with a lot of source code blocks and those code blocks are usually
assigned a name.

I am asking this question because I just noticed that it is not
possible to have multiple source code blocks with the same name. If
that occurs, then

1. The first code block found with the given name is only taken into
2. =M-x org-lint= warns about that.

So, taking into consideration that that is not allowed, I have the
following questions for you

1. Do you use long names? That is, instead of using =generate-table=,
   which is ambiguous, you would use
   =generate-table-grocery-shopping-2020-may=. Another example:
   instead of using =create-venv= you would use

2. If not, how do you name your code blocks to avoid name conflicts?

Rodrigo Morales.

IRC: rdrg109 (freenode)

             reply	other threads:[~2021-02-15 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 19:18 Rodrigo Morales [this message]
2021-02-16  4:53 ` How do you name your code blocks? 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
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:

  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=87wnv9b0na.fsf@gmail.com \
    --to=moralesrodrigo1100@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).