emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: Volunteering to maintain ob-asymptote.el within Org
Date: Tue, 26 Jul 2022 00:15:20 +0300	[thread overview]
Message-ID: <86a68wrj13.fsf@bonfacemunyoki.com> (raw)
In-Reply-To: <87tu791u93.fsf@iki.fi> (Jarmo Hurri's message of "Fri, 22 Jul 2022 10:28:24 +0300")

[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]


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

> Greetings Munyoki.
>

Hi!

[...]

>> That said, shouldn't this be in org-contrib?  Too many features in a
>> tool - featurism - may be distracting, in the sense that you focus
>> more on your tool than work at hand.  
>
> I do not understand this. Why would supporting a professional-level
> graphics programming language be distracting someone from their work
> when using Org?
>

I'm not _against_ supporting a proffesional-level
graphics PL.  What I'm trying to say is that
having it installed should be a choice made by the
end-user.  Personally, I try to keep my systems as
minimal as I can make them; and as such I advocate
for users having that choice.  Very much by
opinions.  Nevertheless...

>> And that said, to work around this, I reckon that's why (?)  we have
>> org-contrib.  You - the end user - install what you want/need. 
>
> Yes, but whenever we split up support, we raise the threshold for the
> use of a combination of tools, in this case Org and Asymptote.
>

I agree with this.

> Org is a very powerful publication tool. Does it not make complete sense
> to include support for a tool for creating professional-quality
> publication graphics?
>

Makes sense.  Just not complete sense to me.  I
reckon I'll give this is a shot this coming
weekend and see how this goes.  Is this:
<https://www.orgmode.org/worg/org-contrib/babel/languages/ob-doc-asymptote.html>
sufficient to get me started?

-- 
(Life is like a pencil that will surely run out,
    but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
    (hkp://keys.openpgp.org))

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]

  parent reply	other threads:[~2022-07-25 21:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21  5:16 Volunteering to maintain ob-asymptote.el within Org Jarmo Hurri
2022-07-21 10:22 ` Munyoki Kilyungi
2022-07-22  7:28   ` Jarmo Hurri
2022-07-25 21:15     ` Munyoki Kilyungi
2022-07-25 21:15     ` Munyoki Kilyungi [this message]
2022-07-26  3:40       ` Greg Minshall
2022-07-26  9:52       ` Jarmo Hurri
2022-07-26  2:05     ` Ihor Radchenko
2022-07-26 10:09       ` Jarmo Hurri
2022-07-27  3:12         ` Ihor Radchenko
2022-07-27  3:13         ` Ihor Radchenko
2022-07-27  0:03       ` Tim Cross
2022-07-27  3:06         ` Ihor Radchenko
2022-07-27  4:09           ` Tim Cross
2022-08-18 16:04             ` Max Nikulin
2022-07-27  4:07       ` Jarmo Hurri
2022-09-01  7:52 ` Bastien
2022-09-03 13:25   ` Jarmo Hurri
2022-09-27 22:06     ` Bastien
2022-10-08  9:58       ` Jarmo Hurri
2022-11-09  6:21         ` Ihor Radchenko
2022-11-10 12:23           ` Jarmo Hurri
2022-11-13  4:27             ` Ihor Radchenko
2022-11-19 11:15               ` Bastien
2022-11-21  6:59                 ` Jarmo Hurri

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=86a68wrj13.fsf@bonfacemunyoki.com \
    --to=me@bonfacemunyoki.com \
    --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).