From: Ihor Radchenko <yantar92@posteo.net>
To: Paul Stansell <paulstansell@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] tangle breaks fortran modules [9.7-pre (release_9.6.7-581-gd38ca5)]
Date: Tue, 05 Sep 2023 09:33:31 +0000 [thread overview]
Message-ID: <875y4pvuac.fsf@localhost> (raw)
In-Reply-To: <CAMJKaZw_To8jWyUB3pVH-W4oNgi2437bv0tTCnSQn-Rst0+wAQ@mail.gmail.com>
Paul Stansell <paulstansell@gmail.com> writes:
>>
>> I opened the latest Org git repo, ran make repro, opened the file,
>> clicked on "tangle" link, moved to the linked source code, and executed
>> it. It worked.
>>
>> So, I am unable to reproduce the problem on my system.
>>
>
> Thanks for investigating. Can you please post your tangled file named
> circle.f90.
>
> Mine looks like this
>
> program main
Never mind my previous message. I forgot the provided init.el file,
which makes all the difference.
Confirmed.
By default, ob-fortran (and at least ob-C) wrap the src block body to
become a standalone function unless you put :main no header argument.
The default behaviour is mostly useful during execution, but not when
tangling.
I will need to think about the best way to approach this. A tentative
fix would be handling :main header argument only during block evaluation.
Meanwhile, you can set :main no as default header argument for fortran.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-09-05 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 1:59 [BUG] tangle breaks fortran modules [9.7-pre (release_9.6.7-581-gd38ca5)] Paul Stansell
2023-09-04 7:56 ` Ihor Radchenko
2023-09-04 10:07 ` Paul Stansell
2023-09-05 9:33 ` Ihor Radchenko [this message]
2023-09-05 15:53 ` Paul Stansell
2023-09-05 15:58 ` Ihor Radchenko
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=875y4pvuac.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=paulstansell@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).