From: Noboru Ota <me@nobiot.com>
To: Ihor Radchenko <yantar92@gmail.com>, Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: transclusion, tangling, flycheck/flymake, etc.
Date: Sat, 06 Nov 2021 11:55:33 +0100 [thread overview]
Message-ID: <87mtmhk0yi.fsf@nobiot.com> (raw)
In-Reply-To: <875yt9e9ce.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> Greg Minshall <minshall@umich.edu> writes:
>
>> my thought about flycheck, flymake, whatever, is that (optionally) a
>> silent, background, =tangle= and/or =<<noweb>> expansion= would take
>> place to produce a "full source file buffer"[*], then the narrowed
>> version of that (corresponding to the part where =C-c '= was issued)
>> buffer is presented for the user's editing convenience.
>
> You are right. That's what I had in mind. Though noweb <<name()>>-style
> references may need to be transcluded without expanding - they may be
> computationally expensive.
>
>> your thought here, iiuc, is that source files would live in the file
>> system, and be transcluded into the .org file. i can see the utility of
>> that. but, i would miss =<<noweb>>= and also the ability to break the
>> source code into small chunks for purposes of documentation.
>
> No. I did not imply that source files will be transcluded into the .org
> file. Currently, .org file is the source of the code (unless you use
> org-babel-detangle). I was thinking that C-c ' will trigger generating a
> temporary prog-mode buffer (according to .org file!). It is not a good
> idea to associate the temporary buffer with actual file because tangling
> may involve expanding noweb references. Noweb sometimes require long
> computations or even access to remote servers. I think that it's better
> to trigger tangle process manually by default.
This part of the discussion is beyond me; apologies for not being able
to engage in a useful way. I don't consider myself a programmer so the
use of Org-transclusion to achieve some elements of IDE (integrated
development environment, I assume) experience is something I cannot
fully address.
As an attempt to clarify my original intent, this use from Greg is what
I had in mind: "source files would live in the file system, and be
transcluded into the .org file". This lets the technical writer (for
example) "break the source code into small chunks for purposes of
documentation." I have had a comment from a user that that's exactly
this person is doing.
So the direction is *from* the source file *to* an org file. What Ihor
seems to be suggesting is the other direction: *from* an org file *to* a
(temporary) source file. I do not think the latter is possible with the
current state of Org-transclusion.
Noboru
prev parent reply other threads:[~2021-11-06 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 8:15 transclusion, tangling, flycheck/flymake, etc Greg Minshall
2021-11-03 12:01 ` Ihor Radchenko
2021-11-03 12:55 ` Greg Minshall
2021-11-06 10:55 ` Noboru Ota [this message]
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=87mtmhk0yi.fsf@nobiot.com \
--to=me@nobiot.com \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
--cc=yantar92@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).