From: Pierre Langlois <pierre.langlois@gmx.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Pierre Langlois <pierre.langlois@gmx.com>, 43777-done@debbugs.gnu.org
Subject: bug#43777: [PATCH] gnu: Add emacs-ob-sclang.
Date: Tue, 06 Oct 2020 20:45:37 +0100 [thread overview]
Message-ID: <875z7nuoim.fsf@gmx.com> (raw)
In-Reply-To: <87blhjxsku.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hello,
Nicolas Goaziou writes:
> Hello,
>
> Pierre Langlois <pierre.langlois@gmx.com> writes:
>
>> Recently I realised I had to build/download qtwebengine because of
>> pulling in supercollider from the emacs-org-contrib package. I thought
>> it'd be a good idea to package the supercollider Org-babel support into
>> its own package to reduce emacs-org-contrib's set of dependencies.
>>
>> What do you think?
>
> It is a good idea. I wish all these libraries were separated upstream;
> org-contrib does not make much sense as a meta package.
Yeah I agree, it's tempting to do that ourselves downstream but it's
probably more trouble than it's worth.
>
> Some nit-picking follows.
>
>> + (synopsis "Org-babel support for SuperCollider")
>
> -> Org Babel support for SuperCollider
>
>> + (description "This package adds support for evaluating @code{sclang}
>> +Org-mode source blocks. It is extracted from the
>> @code{emacs-org-contrib} package.")))
>
> -> Org mode source blocks
Thanks for the review! I tweaked the descriptions as suggested and
pushed with 38094a4f8d56ea8f3ce200a88a2a11885c929348 .
Thanks,
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
prev parent reply other threads:[~2020-10-06 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 11:17 [bug#43777] [PATCH] gnu: Add emacs-ob-sclang Pierre Langlois
2020-10-03 15:00 ` Nicolas Goaziou
2020-10-06 19:45 ` Pierre Langlois [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875z7nuoim.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=43777-done@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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/guix.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).