From: Jacopo De Simoi <wilderjds@protonmail.com>
To: Vladimir Lomov <lomov.vl@yandex.ru>
Cc: Greg Minshall <minshall@umich.edu>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Allow tangling to a list of files
Date: Fri, 09 Jul 2021 13:39:06 +0000 [thread overview]
Message-ID: <eroLflxYbPilYDgaDSwivFTrKVc4Kk98T0-FdL5RJuVnz6Nwc07lT4WqvEA9kFYGmG5B6EgNF0P95dP7sf66aEh0TQMNP7FP57atmM79Sl4=@protonmail.com> (raw)
In-Reply-To: <YOhAdZzb8ek64aNQ@smoon.bkoty.ru>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, July 9th, 2021 at 8:26 AM, Vladimir Lomov <lomov.vl@yandex.ru> wrote:
> Hello,
>
> ** Greg Minshall minshall@umich.edu [2021-07-07 09:56:06 +0300]:
>
> > Vladimir,
>
> > > I couldn't find in Org manual how tangling should work if there are
> > >
> > > several source code blocks with the same file name for ':tangle'. The
> > >
> > > Org manual section "15.8 Extracting Source Code" is a bit
> > >
> > > obscure. There are these two sentences
>
> > i think what Tim answered is correct. but, i believe the "desired"
> >
> > approach is to put all those blocks to be tangled to the same file under
> >
> > a headline with a property drawer containing something like:
> > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> > :header-args+: :tangle "submsim.jl"
> >
>
> Hmm, the more I read the manual and your answers the less I understand. As I
>
> said I didn't find in the manual any mention of feature you and Tim referring
>
> to. Besides I didn't find definition of [source] code block. If Org document
>
> has several #+BEGIN/END_SRC constructions is this the one "code block" or not?
>
> May be they are different if they use different "language" identifier? Again,
>
> I didn't find any definition or explanation in the manual. This is either lack
>
> of documentation or feature of how Org deals with source blocks. In my
>
> opinion, this is undocumented feature.
+1 for clarifying the docs. My point is that there is even a unit test designed to check in which order different source blocks are tangled to the same file. Hence it is a desired feature.
If the documentation lacks the description of this feature, then the documentation needs to be updated.
>
> > i believe this is for performance of tangling, but possibly the
> >
> > "multiple source blocks to same :tangle'd file" feature may disappear?
>
> > cheers, Greg
>
> WBR, Vladimir Lomov
>
> --------------------
>
> How do I get HOME?
next prev parent reply other threads:[~2021-07-09 13:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 18:54 [PATCH] Allow tangling to a list of files Jacopo De Simoi
2021-07-06 2:57 ` Vladimir Lomov
2021-07-06 4:43 ` Greg Minshall
2021-07-06 5:09 ` Jacopo De Simoi via General discussions about Org-mode.
2021-07-06 6:11 ` Vladimir Lomov
2021-07-06 15:24 ` Jacopo De Simoi via General discussions about Org-mode.
2021-07-07 3:27 ` Vladimir Lomov
2021-07-07 4:09 ` Tim Cross
2021-07-07 5:01 ` Jacopo De Simoi
2021-07-07 6:56 ` Greg Minshall
2021-07-07 11:05 ` Jacopo De Simoi
2021-07-09 12:26 ` Vladimir Lomov
2021-07-09 13:39 ` Jacopo De Simoi [this message]
2021-07-09 22:47 ` Tim Cross
2021-07-06 7:30 ` Tim Cross
2021-07-07 23:06 ` Jacopo De Simoi via General discussions about Org-mode.
2021-07-07 23:28 ` Tim Cross
2021-07-08 0:01 ` Jacopo De Simoi
2021-07-08 0:41 ` Tom Gillespie
2021-07-08 16:41 ` Trust me I am a Doctor
2021-07-08 17:42 ` Jacopo De Simoi
[not found] <-0ZoEP_lzUvrnWSq9TwiYHNJ0Spa94xjiTOF0TU8np0pYgHEPx-62_dr5xBMd3VUu7frSRXxiAFje99v2jeaJg==@protonmail.internalid>
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='eroLflxYbPilYDgaDSwivFTrKVc4Kk98T0-FdL5RJuVnz6Nwc07lT4WqvEA9kFYGmG5B6EgNF0P95dP7sf66aEh0TQMNP7FP57atmM79Sl4=@protonmail.com' \
--to=wilderjds@protonmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lomov.vl@yandex.ru \
--cc=minshall@umich.edu \
/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).