Problem with Latex / compile dvi postscript

Problem with Latex / compile dvi postscript

[Christian Banik]

Dear Emacs users,

i always used ktexmaker2 to create Latex texts. There you have a 
"compile" Button, a "create DVI " and a "DVI to PS " Button. Now i'm 
working with GNU Emacs, and up to now i did'nt find out how to do this 
under Emacs!
If you've just written (for example) test1.tex, how can you tell Emacs 
to compile that file? How can you tell Emacs to create the file 
test1.dvi and test1.ps ?


Thanx a lot Christian

Re: Problem with Latex / compile dvi postscript

[Tim Heaney]

Christian Banik <c.banik@tu-harburg.de> writes:
> 
> If you've just written (for example) test1.tex, how can you tell Emacs
> to compile that file? How can you tell Emacs to create the file
> test1.dvi and test1.ps ?

If you are editing test1.tex in TeX mode--- it should say (TeX) or
(TeX Fill) in the modeline--- then

  C-c C-b     should tex it (to a temp file)
  C-c C-v     should view it (from that temp file)
  C-c C-p     should print it (from that temp file)

so you can tex, preview, and print the file you are working on without
creating permanent copies of the intermediate files. If you want to
keep the intermediate files, then

  C-c C-f

should tex it (creating test1.dvi) and you can run the command line
program dvips from within Emacs with

  M-! dvips test1

creating test1.ps. Recent versions of Emacs should have a menubar
across the top and in TeX mode, you should have a menu called "TeX"
with the above commands and more in it. 

If you do not have TeX mode (if editing a .tex file or typing

  M-x tex-mode

does not put you in TeX mode), then try

  http://mirrors.sunsite.dk/auctex/www/auctex/

I don't have a printer myself, so I wanted to make C-c C-p take the
temporary dvi file and make a permanent ps file. I don't know very
much elisp, so I asked how I might do that in this newsgroup earlier
this year and Kevin Rodgers kindly suggested the following:

(add-hook 'tex-mode-hook		; or whatever it's called
	  (lambda ()
	    (set (make-local-variable 'tex-dvi-print-command)
		 (format "dvips * -o %s.ps"
			 (file-name-sans-extension
			  (file-name-nondirectory buffer-file-name))))))

With this added to my .emacs file, I can edit the file test1.tex and
then 

  C-c C-b     tex it (to a temp file)
  C-c C-v     view it (from that temp file)
  C-c C-p     dvips it (from that temp file to test1.ps)

and I save the ps file.

I hope this helps,

Tim

Re: Problem with Latex / compile dvi postscript

[Kester Clegg]

"Tim Heaney" <heaney@cablespeed.com> writes:

> does not put you in TeX mode), then try
> 
>   http://mirrors.sunsite.dk/auctex/www/auctex/

He is using latex, therefore IMHO I would go straight to auctex and
reftex, they really offer the perfect latex editing environment.

I just wish C-c C-c would default to pdflatex, rather than latex!  :-)

-- 
************************************************************************
Kester Clegg				Dept. of Computer Science,
Research Assistant (UTC)		University of York, 
Tel (01904) 43 27 49			email: kester at cs.york.ac.uk
************************************************************************

Re: Problem with Latex / compile dvi postscript

[Kai Großjohann]

Kester Clegg <kester@cs.york.ac.uk> writes:

> I just wish C-c C-c would default to pdflatex, rather than latex!  :-)

See variable TeX-command-default.  But then the auto-detection of the
viewing command doesn't work anymore.  Oh, well...

-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: Problem with Latex / compile dvi postscript

[Kester Clegg]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Kester Clegg <kester@cs.york.ac.uk> writes:
> 
> > I just wish C-c C-c would default to pdflatex, rather than latex!  :-)
> 
> See variable TeX-command-default.  But then the auto-detection of the
> viewing command doesn't work anymore.  Oh, well...

I can't find a TeX-command-default variable.

I think the only way to do it is to write a pdflatex mode, which just
seems silly.  I can't get the default of C-c C-c to use pdflatex rather
than latex despite playing around with every variable in there!  

It would be great to get a default of pdflatex, which could somehow send
a refresh to xpdf, but these are just idle trimmings...  I can type
pdflatex once and then use history.  :-)


 '(LaTeX-command-style (quote (("." "pdflatex
 '\\nonstopmode\\input{%t}'") ("^l" "latex"))))
 '(LaTeX-menu-max-items 30) '(LaTeX-version "pdflatex")
 '(TeX-command-list (quote (("TeX" "tex '\\nonstopmode\\input %t'"
 TeX-run-TeX nil t) ("TeX Interactive" "tex %t" TeX-run-interactive nil
 t) ("LaTeX" "%l '\\nonstopmode\\input{%t}'" TeX-run-LaTeX nil t)
 ("LaTeX Interactive" "%l %t" TeX-run-interactive nil t) ("LaTeX2e"
 "latex2e '\\nonstopmode\\input{%t}'" TeX-run-LaTeX nil t) ("View" "%v "
 TeX-run-silent t nil) ("Print" "%p %r " TeX-run-command t nil) ("Queue"
 "%q" TeX-run-background nil nil) ("File" "dvips %d -o %f "
 TeX-run-command t nil) ("BibTeX" "bibtex %s" TeX-run-BibTeX nil nil)
 ("Index" "makeindex %s" TeX-run-command nil t) ("Check" "lacheck %s"
 TeX-run-compile nil t) ("Spell" "<ignored>" TeX-run-ispell-on-document
 nil nil) ("Other" "" TeX-run-command t t) ("pdflatex" "pdflatex
 '\\nonstopmode\\input{%t}'" TeX-run-LaTeX nil t) ("Makeinfo" "makeinfo
 %t" TeX-run-compile nil t) ("Makeinfo HTML" "makeinfo --html %t"
 TeX-run-compile nil t) ("AmSTeX" "amstex '\\nonstopmode\\input %t'"
 TeX-run-TeX nil t))))
 '(TeX-default-mode (quote latex-mode))
 '(TeX-force-default-mode t)
 '(TeX-printer-default "pp23")
 '(TeX-quote-after-quote t)
 '(TeX-view-style (quote (("^a5$" "xdvi %d -paper a5") ("^landscape$"
"xdvi %d -paper a4r -s 4") ("." "xdvi %d") ("^p" "xpdf %d"))))
 '(reftex-plug-into-AUCTeX t)

(add-hook 'LaTeX-mode-hook 'turn-on-reftex) ; AUCTeX LaTeX mode

-- 
************************************************************************
Kester Clegg				Dept. of Computer Science,
Research Assistant (UTC)		University of York, 
Tel (01904) 43 27 49			email: kester at cs.york.ac.uk
************************************************************************

Re: Problem with Latex / compile dvi postscript

[Kai Großjohann]

Kester Clegg <kester@cs.york.ac.uk> writes:

> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Kester Clegg <kester@cs.york.ac.uk> writes:
>> 
>> > I just wish C-c C-c would default to pdflatex, rather than latex!  :-)
>> 
>> See variable TeX-command-default.  But then the auto-detection of the
>> viewing command doesn't work anymore.  Oh, well...
>
> I can't find a TeX-command-default variable.

I can't believe it.  Your Emacs installation must be really out of
whack!  First you see strange stuff with Gnus, now your AUC-TeX
doesn't have the TeX-command-default variable.

I'm afraid of a more fundamental problem with your Emacs installation.

When you open a *.tex file (containing LaTeX source code), do you see
a `LaTeX' and a `Command' menu bar item?  If so, then you should be
using AUC-TeX, and there surely a TeX-command-default variable is
defined.  Type C-h v TeX-command-default RET from that *.tex buffer.
What does Emacs say?

-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: Problem with Latex / compile dvi postscript

[Kester Clegg]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> When you open a *.tex file (containing LaTeX source code), do you see
> a `LaTeX' and a `Command' menu bar item?  If so, then you should be
> using AUC-TeX, and there surely a TeX-command-default variable is
> defined.  

Sorry Kai, I simply did M-x customize-variable, which didn't find it.  

> Type C-h v TeX-command-default RET from that *.tex buffer.  What does
> Emacs say?

TeX-command-default's value is "LaTeX"
Local in buffer RefactoringCodeTN0221.tex; global value is nil

Documentation:
The default command for TeX-command in the current major mode.


If M-x customize-variable doesn't pick it up, how does one change it?


-- 
************************************************************************
Kester Clegg				Dept. of Computer Science,
Research Assistant (UTC)		University of York, 
Tel (01904) 43 27 49			email: kester at cs.york.ac.uk
************************************************************************

Re: Problem with Latex / compile dvi postscript

[Kai Großjohann]

Kester Clegg <kester@cs.york.ac.uk> writes:

> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> When you open a *.tex file (containing LaTeX source code), do you see
>> a `LaTeX' and a `Command' menu bar item?  If so, then you should be
>> using AUC-TeX, and there surely a TeX-command-default variable is
>> defined.  
>
> Sorry Kai, I simply did M-x customize-variable, which didn't find it.  

I put things like

%%% Local Variables:
%%% TeX-compile-command: "PDFLaTeX"
...other.lines.here...
%%% End:

at the end of some of my *.tex files.  My entry in TeX-command-list
is called "PDFLaTeX" with that capitalization, you might have a
different entry.

-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: Problem with Latex / compile dvi postscript

[Dr. Ing. Dieter Jurzitza]

Dear listmembers,
if anybody is interested in a patch that allows the usage of pdflatex and
acrobat reader (i.E) really integrated with automatic detection of the presence
of more up-to-date .pdf-files come back to me.

I offered to submit a patch to the auctex mailing list, but there was hardly
any interest.

The issue is the hard coded dvi-extension within auctex that makes it
impossible to adapt auctex as-is to a different output format (might be xml or
whatever in the future...)

Take care


Dieter

On 03-Dec-2002 Kai Großjohann wrote:
> Kester Clegg <kester@cs.york.ac.uk> writes:
> 
***

-- 
-----------------------------------------------------------
E-Mail: Dr. Ing. Dieter Jurzitza <dieter.jurzitza@t-online.de>
Date: 04-Dec-2002
Time: 21:24:54                 |
                                \
                 /\_/\           |
                | ~x~ |/-----\   /
                 \   /-       \_/
  ^^__   _        /  _  ____   /
 <°°__ \- \_/     |  |/    |  |
  ||  ||         _| _|    _| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
-----------------------------------------------------------

Re: Problem with Latex / compile dvi postscript

[Kester Clegg]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> I put things like
> 
> %%% Local Variables:
> %%% TeX-compile-command: "PDFLaTeX"
> ...other.lines.here...
> %%% End:
> 
> at the end of some of my *.tex files.  My entry in TeX-command-list
> is called "PDFLaTeX" with that capitalization, you might have a
> different entry.

Interesting, I've never seen that before.  
I'll give it a go.  :-)

-- 
************************************************************************
Kester Clegg				Dept. of Computer Science,
Research Assistant (UTC)		University of York, 
Tel (01904) 43 27 49			email: kester at cs.york.ac.uk
************************************************************************

Re: Problem with Latex / compile dvi postscript

[Kester Clegg]

"Dr. Ing. Dieter Jurzitza" <dieter.jurzitza@t-online.de> writes:

> if anybody is interested in a patch that allows the usage of pdflatex
> and acrobat reader (i.E) really integrated with automatic detection of
> the presence of more up-to-date .pdf-files come back to me.

Can you get AR to behave the way xdvi does, i.e. reload the new output
file automatically when it receives focus, or like xpdf, on hitting 'r'
or turning a page?  That would be useful!

> 
> I offered to submit a patch to the auctex mailing list, but there was
> hardly any interest.
> 

I think that's because a lot of people are still using latex.  Most of
our dept uses latex rather than pdflatex.  And some, like those in
Linguistics, make heavy use of pstricks.  pdftricks is a bit flaky.

> 
> The issue is the hard coded dvi-extension within auctex that makes it
> impossible to adapt auctex as-is to a different output format (might
> be xml or whatever in the future...)
> 

Can you give a bit more detail?

-- 
************************************************************************
Kester Clegg				Dept. of Computer Science,
Research Assistant (UTC)		University of York, 
Tel (01904) 43 27 49			email: kester at cs.york.ac.uk
************************************************************************

Re: Problem with Latex / compile dvi postscript

[Kai Großjohann]

Kester Clegg <kester@cs.york.ac.uk> writes:

> "Dr. Ing. Dieter Jurzitza" <dieter.jurzitza@t-online.de> writes:
>
>> if anybody is interested in a patch that allows the usage of pdflatex
>> and acrobat reader (i.E) really integrated with automatic detection of
>> the presence of more up-to-date .pdf-files come back to me.
>
> Can you get AR to behave the way xdvi does, i.e. reload the new output
> file automatically when it receives focus, or like xpdf, on hitting 'r'
> or turning a page?  That would be useful!

I use Ctrl+W to close the current file, then Ctrl+CursorLeft to go
back.  That has the effect of reloading the current file.

But this fails if AR has more than one file open.

Actually, I rather liked it, but now I've gone back to xdvi because
of source specials and forward/backward search.  I miss the
nicely-looking anti-aliasing, though.

It seems that latex+dvips+ps2pdf produces nice PDF files, too.
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: Problem with Latex / compile dvi postscript

[Stefan Monnier <foo@acm.com>]

>>> if anybody is interested in a patch that allows the usage of pdflatex
>>> and acrobat reader (i.E) really integrated with automatic detection of
>>> the presence of more up-to-date .pdf-files come back to me.
>> 
>> Can you get AR to behave the way xdvi does, i.e. reload the new output
>> file automatically when it receives focus, or like xpdf, on hitting 'r'
>> or turning a page?  That would be useful!

It would probably be an afternoon hack if we had the source.
But why bother since we can use gv or xpdf instead.

> But this fails if AR has more than one file open.

AR is not too bad when reading someone else's PDF but when you're
developing your own, its UI sucks rocks.

> Actually, I rather liked it, but now I've gone back to xdvi because
> of source specials and forward/backward search.  I miss the
> nicely-looking anti-aliasing, though.

I've started to like ActiveDVI, especially together with WhyzzyTeX.
It also supports colors.  The only problem is that it didn't support
all the font-tricks of LaTeX last time I tried it.


        Stefan