From: Kannan Varadhan <kvaradhan3@gmail.com>
To: jdh <dhenman@gmail.com>
Cc: Zsh Users' List <zsh-users@zsh.org>
Subject: Re: texinfo
Date: Mon, 6 Apr 2020 13:06:30 -0700 [thread overview]
Message-ID: <AA1C4AFB-1ADC-48ED-8F83-0CF3F37BD85A@gmail.com> (raw)
In-Reply-To: <CAFNqd5VJy1NTDUGyn0b844iu8wTHcGqhLyOxNWShmkAtpfuayQ@mail.gmail.com>
Depending on your motivation, you can simply run TexLive off a DVD or USB without system integration.
This may be useful if you are only doing one offs, and don’t want to store all this on your local system
All the time.
Check out: https://tug.org/texlive/doc/texlive-en/texlive-en.html#tlportable
Kannan
> On Apr 6, 2020, at 7:20 AM, Christopher Browne <cbbrowne@gmail.com> wrote:
>
> On Sun, Apr 5, 2020 at 7:08 PM jdh <dhenman@gmail.com> wrote:
>
>>
>> texi2pdf and texi2dvi which are in the texinfo debian package require a
>> 'tex' binary program to run.
>>
>> I'd prefer to not have to install all of texlive just to get it.
>>
>> Is there any tex binary in the standalone lmtx system?
>>
>> If not are there any recommendations to install it?
>>
>
> Regrettably, you need a bunch of the things that will be in texlive in
> order to use it.
>
> Tex, but no macro collections? Oops, no good.
>
> Tex, but no font definitions? Oops, no good.
>
> I expect the list of "Tex, but no <foo>? Oops, no good" items continues
> from there. Macro collections and fonts leap to mind immediately, but I'm
> sure that's not all :-(
>
> There may be something smaller than texlive; it looks like MiKTeX might be
> a possibility.
> --
> When confronted by a difficult problem, solve it by reducing it to the
> question, "How would the Lone Ranger handle this?"
prev parent reply other threads:[~2020-04-06 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 23:08 texinfo jdh
2020-04-06 14:20 ` texinfo Christopher Browne
2020-04-06 20:06 ` Kannan Varadhan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AA1C4AFB-1ADC-48ED-8F83-0CF3F37BD85A@gmail.com \
--to=kvaradhan3@gmail.com \
--cc=dhenman@gmail.com \
--cc=zsh-users@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).