zsh-workers
 help / color / mirror / code / Atom feed
From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: Test release: 5.6.2-test-3
Date: Mon, 7 Jan 2019 12:25:01 +0900	[thread overview]
Message-ID: <B5137206-984B-4EF0-92F0-DC97D6B43CD0@kba.biglobe.ne.jp> (raw)
In-Reply-To: <20457BFF-83B5-4DF5-AB6D-A90E80DDBED9@dana.is>


> 2019/01/07 1:37, dana <dana@dana.is> wrote:
> 
> For the PDF, i needed TeX, which the normal Homebrew repo also doesn't have i
> guess because it's similarly complicated to build on macOS. Homebrew Cask has
> the MacTeX distribution, but the full thing is over 3 GiB, which is silly. I
> found the 'basic' distribution, though, and then i needed to manually install
> the texinfo thing for it, and after all that i thought i'd be OK, but
> apparently TeX needs X11 to generate the PDF for some reason (font stuff, i
> assume).

I'm using the binary distribution from http://www.tug.org/mactex/
(MacTeX.pkg, 3.2GB) and it works fine. It also includes gs (ghostscript)
and ps2pdf. Of course X11 is NOT required.

# I haven't tried the BasicTeX.pkg and don't know whether it works or not.

Can you create PDF from a simple LaTeX source by pdflatex command?


> 2019/01/07 6:34, Daniel Tameling <tamelingdaniel@gmail.com> wrote:
> 
> I have both, TeX and X11, installed but stilled failed to build the
> entire documentation because roff2ps is missing. So this might not be
> the end for you if you want to try it again.

I'm using /usr/bin/groff in place of roff2ps and it seems to work.
Create a script like

#!/bin/sh
groff -T ps "$@"

name it roff2ps, and put it somewhere in your PATH.

  parent reply	other threads:[~2019-01-07  4:08 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05  7:08 dana
2019-01-05 17:49 ` Peter Stephenson
2019-01-05 18:42   ` dana
2019-01-05 20:58   ` Martijn Dekker
2019-01-05 21:55     ` Daniel Shahaf
2019-01-06  2:37 ` Axel Beckert
2019-01-06 15:12 ` Jun T.
2019-01-06 16:37   ` dana
2019-01-06 16:43     ` Daniel Shahaf
2019-01-06 16:56       ` dana
2019-01-06 21:34     ` Daniel Tameling
2019-01-07  3:25     ` Jun T [this message]
2019-01-07  7:02       ` dana
2019-01-21 12:54 ` ETA for zsh 5.7? (was: Test release: 5.6.2-test-3) Axel Beckert
2019-01-21 14:26   ` Peter Stephenson
2019-01-21 19:14     ` Mikael Magnusson
2019-01-21 19:32       ` Mikael Magnusson
2019-01-21 19:32       ` Mikael Magnusson
2019-01-21 21:56         ` Sebastian Gniazdowski
2019-01-22  9:29           ` Peter Stephenson
2019-01-21 23:00 ` Bug with traps and exit Martijn Dekker
2019-11-24  5:54   ` Martijn Dekker
2019-11-25 16:42     ` Sebastian Gniazdowski
2019-12-10 19:23     ` Martijn Dekker
2019-12-11  2:40       ` Daniel Shahaf
2019-12-12 10:14       ` Peter Stephenson
2019-12-13 14:26         ` Martijn Dekker
2019-12-13 14:49           ` Peter Stephenson
2019-12-14 11:28             ` Daniel Shahaf
2019-12-15 18:59               ` Peter Stephenson
2019-12-16  5:24                 ` Daniel Shahaf
2019-12-16  6:37                   ` Bart Schaefer
2019-12-17  7:31                     ` Daniel Shahaf
2019-12-17 20:29                       ` Peter Stephenson
2019-12-18  0:31                         ` Daniel Shahaf
2019-12-31  2:03                           ` Daniel Shahaf
2019-12-31 13:46                             ` Daniel Shahaf
2019-12-16 10:09                   ` Peter Stephenson
2019-12-16  5:27     ` The bug from workers/44922 (was: " Daniel Shahaf
2020-01-30 13:49       ` The bug from workers/44922 Martijn Dekker
2020-01-30 14:01     ` Bug with traps and exit Martijn Dekker
2020-01-31  4:29       ` Daniel Shahaf
2022-11-26  3:00       ` Bart Schaefer

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=B5137206-984B-4EF0-92F0-DC97D6B43CD0@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).