From: gerard.vermeulen@posteo.net
To: Emacs orgmode <emacs-orgmode@gnu.org>,
Ihor Radchenko <yantar92@posteo.net>
Subject: [PATCH] ob-fortran.el: Fix name of caller in documentation
Date: Fri, 15 Sep 2023 08:14:50 +0000 [thread overview]
Message-ID: <a02e749d5ec4638041fcce9e8fbcd5ad@posteo.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
Hi,
This patch fixes an oversight in
765a84ea252fd7f281340c40fdc97f696f8cac33
It fixes the caller name in documentation and conforms to "rules" in
sibling ob-XXX.el files.
Regards -- Gerard
[-- Attachment #2: 0001-ob-fortran.el-Fix-name-of-caller-in-documentation.patch --]
[-- Type: application/octet-stream, Size: 1106 bytes --]
From e5fae8056dbae674603de9fe0ff79c028d974ab0 Mon Sep 17 00:00:00 2001
From: Gerard Vermeulen <gerard.vermeulen@posteo.net>
Date: Fri, 15 Sep 2023 09:48:33 +0200
Subject: [PATCH] ob-fortran.el: Fix name of caller in documentation
* lisp/ob-fortran.el (org-babel-execute:fortran): Fix name of caller
in documentation and conform to "rules" in sibling ob-XXX.el files.
---
lisp/ob-fortran.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/ob-fortran.el b/lisp/ob-fortran.el
index 7075d8a9f..fabc6a47a 100644
--- a/lisp/ob-fortran.el
+++ b/lisp/ob-fortran.el
@@ -51,8 +51,8 @@
:type 'string)
(defun org-babel-execute:fortran (body params)
- "Execute fortran BODY according to PARAMS.
-This function should only be called by `org-babel-execute:fortran'."
+ "Execute Fortran BODY according to PARAMS.
+This function is called by `org-babel-execute-src-block'."
(let* ((tmp-src-file (org-babel-temp-file "fortran-src-" ".F90"))
(tmp-bin-file (org-babel-temp-file "fortran-bin-" org-babel-exeext))
(cmdline (cdr (assq :cmdline params)))
--
2.42.0
next reply other threads:[~2023-09-15 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 8:14 gerard.vermeulen [this message]
2023-09-15 9:23 ` [PATCH] ob-fortran.el: Fix name of caller in documentation 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=a02e749d5ec4638041fcce9e8fbcd5ad@posteo.net \
--to=gerard.vermeulen@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).