Exporting form emacs texinfo-mode to dvi, pdf, and html

[lisa-asket@perso.be]

Seems to work using



M-x compile
texi2pdf myfile.texi



But I cannot find the generated pdf file.


From: Bruno Barbier <brubar.cs@gmail.com>
To: lisa-asket@perso.be;
   moasenwood@zoho.eu;
   help-gnu-emacs@gnu.org
Subject: Re: Exporting form emacs texinfo-mode to dvi, pdf, and html
Date: 26/06/2021 21:37:30 Europe/Paris

lisa-asket@perso.be writes:

> If you want mo to perform as well as others, you are looking for a disappointment.
>
> Don't know anything about make.
>
>
>
> If I do M-x compile and enter "make -j 4 -s -k" emacs complains with  
>
>
>
> make -j 4 -s -k 
> make: *** No targets specified and no makefile found.  Stop.
>

You don't need 'make'. The 'compile' function accepts any shell command.


Just type:

M-x compile

then, when prompted, enter:

texi2pdf myfile.texi

If that works for you, you could follow Eli advice, and put the
following line, at the top of you file, to define the variable
'compile-command':

-*- compile-command: texi2pdf myfile.texi -*-

at the top of your file, so that you don't have to enter it manually
each time.

If you want to do this for every texinfo file, then, you may teach Emacs
to configure it for you, using a texinfo mode hook.


Bruno


>
>
>
>
>
> From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Exporting form emacs texinfo-mode to dvi, pdf, and html
> Date: 26/06/2021 20:03:00 Europe/Paris
>
> lisa-asket wrote:
>
>> Ok, let's do it. It also says one can use mode hooks to
>> specify it in certain modes, like this:
>>
>> (add-hook 'c-mode-hook
>> (lambda ()
>> (unless (or (file-exists-p "makefile")
>> (file-exists-p "Makefile"))
>> (setq-local compile-command
>> (concat "make -k "
>> (if buffer-file-name
>> (shell-quote-argument
>> (file-name-sans-extension buffer-file-name))))))))
>
> You don't need any of that because the `compile-command', e.g.
> "make -j 4 -s -k " that can be the same for every mode or
> programming language or formatting you do.
>
> Also there's no need to look for a Makefile because it looks
> in the same directory as the buffer for one and if there is
> one, that's where it happens.
>
> Time to step up your game :(
>
> -- 
> underground experts united
> https://dataswamp.org/~incal