emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ob-ditaa.el: custom var name, ditaa executable, SVG output, and chararacter encoding
Date: Fri, 08 Nov 2024 19:10:09 +0000	[thread overview]
Message-ID: <878qttwnhq.fsf@localhost> (raw)
In-Reply-To: <87a5eanfys.fsf@iki.fi>

Jarmo Hurri <jarmo.hurri@iki.fi> writes:

>>> +	 (png (cdr (assq :png params)))
>>> +	 (svg (cdr (assq :svg params)))
>>>  	 (eps (cdr (assq :eps params)))
>>
>> I am wondering if we could instead deprecate the :png/:eps parameters
>> and instead use the :file extension to decide.
>
> This could be done, but I do not see much harm in providing an
> override. Note that the file extension is used by default.
>
> So, your choice: is it
> a) file extension only
> b) file extension with possibility to override with parameters?

AFAIU, the current situation is not ideal: if we have something like
#+begin_src ditaa :pdf :file foo.eps, the results will be very strange.

Moreover, we have API function `org-babel-graphical-output-file' (not
used by ob-ditaa) that makes use of :file-ext standard header argument
that is serving similar purpose with :eps/:pdf in ob-ditaa (see 16.5
Evaluating Code Blocks section of the manual).

So, I view these :ext options that are still used by several babel
backends as candidates for deprecation. Certainly, I do not want to make
them proliferate in the new features.

>>> +      (message cmd)
>>> +      (shell-command cmd)
>>> +      (when pdf
>>> +	(let ((pdf-cmd (concat "epstopdf" " " ditaa-out-file " "
>>> +		              "-o=" (org-babel-process-file-name out-file))))
>>> +          (message pdf-cmd)
>>
>> Why message?
>
> I was originally directed to ob-plantuml, which message's its
> command. During the testing of this patch I found messaging useful to
> observe what was happening.
>
> So, your choice:
> a) no messaging
> b) message always
> c) defcustom a toggle for messaging?

I'd prefer no messaging as it serves no clear purpose to the user.
For debugging purposes, one can always do M-x trace-function shell-command

> And, finally, should I add myself as the maintainer?

That would be great. Thanks!
I assume that you already have access to savannah as you are
listed as the maintainer of ob-processing.

-- 
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>


      reply	other threads:[~2024-11-08 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03 14:05 [PATCH] ob-ditaa.el: custom var name, ditaa executable, SVG output, and chararacter encoding Jarmo Hurri
2024-11-03 17:45 ` Ihor Radchenko
2024-11-08 11:05   ` Jarmo Hurri
2024-11-08 19:10     ` Ihor Radchenko [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=878qttwnhq.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=jarmo.hurri@iki.fi \
    /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).