At a first glance, this task seems to be easy:

1. Go to the top of the source code block
2. Insert "#+NAME: <<name>>" or replace the current name.
3. Done.

However, there are multiple scenarios. The attached file =main.org=
contains the possible scenarios that the function must cover in order to
be considered usable.

Anyway, I could write the function but before spending time doing that I
was wondering if there exist some solutions out there.

The motivation for this question is to make names of code blocks include
the ID of the current heading so that name clashes doesn'tf occur in Orgf
mode files. Recall that =M-x org-lint= complains when there are two code
blocks with the same name in the same file. This means that if you have
a code block with name =generate-data=, you can't use that same name in
that specific file.

* foo

Some code blocks have neither headers nor names.

#+begin_src dash
ls
#+end_src

#+begin_src dash :noweb yes :results output
ls
#+end_src

Some code blocks only have headers.

#+HEADER: :noweb yes
#+begin_src dash
ls
#+end_src

Some code blocks have multiple headers

#+HEADER: :results output
#+HEADER: :noweb yes
#+begin_src dash
ls
#+end_src

Some code blocks have empty names

#+NAME:
#+begin_src dash
echo a
#+end_src

Some code blocks have names.

#+NAME: ls
#+begin_src dash
ls
#+end_src

Some code blocks have names and headers.

#+NAME: ls
#+HEADER: :results output
#+HEADER: :noweb yes
#+begin_src dash
ls
#+end_src

#+HEADER: :results output
#+NAME: ls
#+HEADER: :noweb yes
#+begin_src dash
ls
#+end_src

#+HEADER: :results output
#+HEADER: :noweb yes
#+NAME: ls
#+begin_src dash
ls
#+end_src
-- 
Greetings,
Rodrigo Morales.

IRC: rdrg109 (freenode)

Reply via email to