From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add emacs-ess.
Date: Wed, 6 Jul 2016 12:52:42 +0200 [thread overview]
Message-ID: <877fczhwcl.fsf@mdc-berlin.de> (raw)
In-Reply-To: <8760sjkprg.fsf@gnu.org>
Roel Janssen <roel@gnu.org> writes:
> Ricardo Wurmus writes:
>
>> Roel Janssen <roel@gnu.org> writes:
>>
>>> Ricardo Wurmus writes:
>>>
>>>> Hi Roel,
>>>>
>>>>>> As Ben wrote “texlive-minimal” might be sufficient. Please also move
>>>>>> these two to “native-inputs” if that’s possible.
>>>>>
>>>>> Unfortunately, when building with texlive-minimal, we are missing a
>>>>> font:
>>>>> !pdfTeX error: /gnu/store/gnh4kn47mn3m2rlgm9i9xl3wmq2kahia-texlive-minimal-2016
>>>>> /bin/pdftex (file cmr9): Font cmr9 at 600 not found
>>>>> ==> Fatal error occurred, no output PDF file produced!
>>>>
>>>> Too bad! We should take some time to figure out how to split up
>>>> texlive and make it find modules via some search path. I’m afraid this
>>>> might take a long time.
>>>
>>> Does that mean we should put emacs-ess on hold until we have fixed this?
>>
>> No, not at all. Use “texlive” in this case. I was just trying to
>> express that this is a recurring itch that needs scratching :)
>
> Right. I agree. So I can push emacs-ess?
I have no objections. Since nobody else has raised any objections I’d
say: please push!
~~ Ricardo
next prev parent reply other threads:[~2016-07-06 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 12:56 [PATCH] gnu: Add emacs-ess Roel Janssen
2016-07-05 13:14 ` Ben Woodcroft
2016-07-05 13:44 ` Roel Janssen
2016-07-05 13:59 ` Ben Woodcroft
2016-07-05 13:39 ` Ricardo Wurmus
2016-07-06 8:28 ` Roel Janssen
2016-07-06 8:44 ` Ricardo Wurmus
2016-07-06 10:02 ` Roel Janssen
2016-07-06 10:12 ` Ricardo Wurmus
2016-07-06 10:46 ` Roel Janssen
2016-07-06 10:52 ` Ricardo Wurmus [this message]
2016-07-09 19:31 ` Andreas Enge
2016-07-10 10:39 ` Roel Janssen
2016-07-10 13:26 ` Andreas Enge
2016-07-10 15:17 ` Roel Janssen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fczhwcl.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=roel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.