From: Ihor Radchenko <yantar92@gmail.com>
To: Joseph Turner <joseph@breatheoutbreathe.in>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] lisp/ob-plantuml.el: Insert results in buffer
Date: Mon, 25 Jul 2022 21:15:40 +0800 [thread overview]
Message-ID: <87bktduydf.fsf@localhost> (raw)
In-Reply-To: <20220719231520.100206-1-joseph@breatheoutbreathe.in>
Joseph Turner <joseph@breatheoutbreathe.in> writes:
> Allow src block execution without ":file" header arg. When ":file" is
> omitted, insert txt output in buffer below src block.
>
> TINYCHANGE
Thanks for your contribution!
This addition makes a lot of sense.
Some comments:
Most importantly, the patch does not change the default value of
org-babel-default-header-args:plantuml. :results header arg is set to
"file" by default. This yields something like the following:
#+begin_src plantuml
Bob->Alice : Hello1!
#+end_src
#+RESULTS:
[[file: ,---. ,-----.
|Bob| |Alice|
`-+-' `--+--'
| Hello1! |
|-------------->|
,-+-. ,--+--.
|Bob| |Alice|
`---' `-----'
]]
Note that the output is treated as a path to file:
[[file: ... output string ...]]
which is indeed wrong.
The solution will be simply removing the default :results setting.
Other comments are for code and documentation style.
> Allow src block execution without ":file" header arg. When ":file" is
> omitted, insert txt output in buffer below src block.
Please use double space between sentences. See
https://orgmode.org/worg/org-contribute.html
> +
> +*** =org-babel-execute:plantuml= can output ASCII graphs in the buffer
> +
> +Previously, executing PlantUML src blocks required a ":file" header argument. Now, if that header argument is omitted, an ASCII graph will be inserted below the src block.
> +
Likewise. Also, please fill the paragraph making sure that each line
spans less than 80 columns. Same for the code and comments inside the
code.
> - nil)) ;; signal that output has already been written to file
> + (unless do-export (with-temp-buffer
> + (insert-file-contents out-file)
> + (buffer-substring-no-properties (point-min) (point-max))
> + ))))
We follow Elisp conventions regarding indentation and parenthesis
placement as in D.1 Emacs Lisp Coding Conventions - do not leave
parenthesis on the line of their own.
Also, the way you typed unless leads to excessive indentation. You could
instead do
(unless do-export
(with-temp-buffer
...))
Best,
Ihor
next prev parent reply other threads:[~2022-07-25 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 23:15 [PATCH] lisp/ob-plantuml.el: Insert results in buffer Joseph Turner
2022-07-25 13:15 ` Ihor Radchenko [this message]
2022-07-25 19:52 ` Joseph Turner
2022-07-26 5:50 ` Ihor Radchenko
2022-07-27 20:51 ` Joseph Turner
2022-07-28 14:36 ` Ihor Radchenko
2022-07-31 22:05 ` Joseph Turner
2022-08-02 12:42 ` 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=87bktduydf.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=joseph@breatheoutbreathe.in \
/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).