unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: 조성빈 <pcr910303@icloud.com>
To: Jean-Christophe Helary <brandelune@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: building the docs
Date: Fri, 17 May 2019 19:01:11 +0900	[thread overview]
Message-ID: <6EA342E6-AB2A-4A18-B2B6-780E4150FC5A@icloud.com> (raw)
In-Reply-To: <D1A69DD6-7C29-4BB2-8BC0-F755536E4245@gmail.com>


2019. 5. 16. 오후 3:59, Jean-Christophe Helary <brandelune@gmail.com> 작성:

>>  If not, perhaps something is wrong with texindex or with texi2pdf?
> 
> I removed texinfo and reinstalled it. And that's what I get. Since I use brew on macos to manage texinfo and have never tried to install it by hand, I guess that's a recent update from the package that's causing the glitch since I don't seem to remember having such issues in the relatively recent past...

IIRC, homebrew’s texinfo is a keg-only formula; If you want the executable in the path you should add /usr/local/opt/texinfo/bin.... and I’m pretty sure I (macOS High Sierra) could get my docs right.



  parent reply	other threads:[~2019-05-17 10:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  6:15 building the docs Jean-Christophe Helary
2019-05-16  6:52 ` Eli Zaretskii
2019-05-16  6:59   ` Jean-Christophe Helary
2019-05-16 13:54     ` Eli Zaretskii
2019-05-17  8:56       ` Jean-Christophe Helary
2019-05-17  9:30         ` Eli Zaretskii
2019-05-17 10:01     ` 조성빈 [this message]
2019-05-17 11:54       ` Jean-Christophe Helary
2019-05-18 12:44         ` Jean-Christophe Helary
2019-05-29  6:11           ` Jean-Christophe Helary
2019-05-29 15:04             ` Eli Zaretskii
2019-05-29 23:37               ` Paul Eggert
2019-05-30  1:46                 ` Jean-Christophe Helary

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=6EA342E6-AB2A-4A18-B2B6-780E4150FC5A@icloud.com \
    --to=pcr910303@icloud.com \
    --cc=brandelune@gmail.com \
    --cc=emacs-devel@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).