unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Dependencies of Org
Date: Sun, 18 Nov 2018 09:40:04 +0100	[thread overview]
Message-ID: <87va4ueq3f.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <E1gNSOS-0007Ej-GO@fencepost.gnu.org> (Richard Stallman's message of "Thu, 15 Nov 2018 19:53:56 -0500")

Hello,

Richard Stallman <rms@gnu.org> writes:

> I don't think we reached a clear resolution about the cases where
> where Org suggests loading something else.  That practice is not
> necessarily a problem -- loading some unrelated free program is fine.
> It is a problem when the code depended on is nonfree, or if it ought
> to be part of Emacs (which could mean ELPA) but it isn't.
>
> Are there still cases like this?

I think the manual is fine, now. The conversion from "htmlize" to
"htmfontify" has stalled, however. I asked for some guidance about it
a few weeks ago. I now wait for an answer.

One potential issue I can think of is Babel libraries, i.e., libraries
used to execute source code in an Org buffer. Typically, such a library
relies on an external Elisp library, e.g., "ob-scheme" relies on
"geiser", "ob-shen" relies on "inf-shen", "ob-R" on "ess", and so on.
These external libraries are free, but I don't know if they qualify as
"ought to be part of Emacs". I assume not, since Emacs cannot provide
a mode for every language out there.

Regards,

-- 
Nicolas Goaziou



  reply	other threads:[~2018-11-18  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16  0:53 Dependencies of Org Richard Stallman
2018-11-18  8:40 ` Nicolas Goaziou [this message]
2018-11-18 23:14   ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2018-10-26  2:57 Richard Stallman

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87va4ueq3f.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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.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).