Re: xdvi question

[Christopher Pinon]

Thanks to those who replied to my question about xdvi.  I guess that I'll
just turn off the column of buttons and learn all the keystrokes.  It's a
bit too bad (though understandable) that the size of the column of 
buttons is hardwired into xdvi.  If this were the only worry in life ... 
:-)

Christopher Pinon

xdvi question

[Christopher Pinon]

I may be missing the obvious, but is there a way to make xdvi's column of
buttons shorter (hence smaller) so that it will fit on a small screen?  
The geometry setting fixes the window size, but it doesn't seem to affect
the size of the column of buttons (the lower buttons are still hidden).  
(I won't say how small my screen is, but I can see just to the bottom of
the Previous button.  How many buttons can't I see? :-( )

Thanks,
Christopher Pinon

Re: xdvi question

[Joost Kremers]

On Mon, Jul 08, 2002 at 03:28:10PM +, Christopher Pinon wrote:
 I may be missing the obvious, but is there a way to make xdvi's column of
 buttons shorter (hence smaller) so that it will fit on a small screen?  

not that i know of. you can make the buttons disappear altogether with
`x' or by starting xdvi with the `-expert' option. (and also by
setting `xdvi.expert: True' in ~/.Xdefaults.)

 The geometry setting fixes the window size, but it doesn't seem to affect
 the size of the column of buttons (the lower buttons are still hidden).  
 (I won't say how small my screen is, but I can see just to the bottom of
 the Previous button.  How many buttons can't I see? :-( )

all the functions are available through keystrokes. see `man xdvi'
section KEYSTROKES to see what they are.

-- 
Joost Kremers
Life has its moments
http://baserv.uci.kun.nl/~jkremers/

MakeTeXPK xdvi question

[Vic Tisone]

We are currently in the process of upgrading our TeX installation
from teTeX_.4 to teTeX-1.0 and have them running in parallel---In
the older version when a user was running xdvi and there was a 
missing pk font, I beleive MakeTeXPK would go into action in creating the 
needed font and depositing into the correct texmf/fonts directory 
for future use and then finish the xdvi of the document. Below are the lines
in the old teTeX_.4's MakeTeXPK script that looks to allow users
to do this.
-
donames='set x `MakeTeXnames $NAME $DPI $MODE $DEST`
PKDEST=$2
PKDESTDIR=`echo $PKDEST | sed s/^[^\/]*$/./; s/\/[^\/]*$//`
PKNAME=`basename $PKDEST`
GFNAME=$NAME.${DPI}gf'

eval $donames

# Allow fonts to be read and written (especially in case we make
# directories) by everyone.
umask 0
---

I have checked the new teTeX_1.0's MakeTeXPK which calls maketexpk
for simlar comment lines to turn this type of action on but
can not find any that are apparent. I have checked the font directory 
permissions and they are the same as in the previous TeX installation.
I have been running a test latex doc on both installations to make sure
they behave the simlar before releasing them for general use. I have 
only set the TEXINPUTS varaible to what is below for the new installation in 
regards to TeX.

.:/home/tisone/Macros://:/opt/share/pub/tex//

When I run xdvi on the test doc using the new version of TeX,
I get the following output with the KPSE_DEBUG_PATHS turned on.
It is only the bottom part of the output before it bails.
When I use the older version's xdvi, the dvi file comes up fine
and I can see that necessary font was made by a user a some point
in time. Below is the messages I get when I use the new xdvi on
the same dvi file.

---

This is METAFONT, Version 2.7182 (Web2C 7.3.1)
kdebug:Search path for base files (from texmf.cnf)
kdebug:  = /hagar/d/tisone/louise:!!/opt/share/newtex/texmf/web2c
kdebug:  before expansion = .:$TEXMF/web2c
kdebug:  application override path = (none)
kdebug:  application config file path = (none)
kdebug:  texmf.cnf path = .:$TEXMF/web2c
kdebug:  compile-time path = .:/tmp/build/tetex/texmf/web2c
kdebug:  default suffixes = .base
kdebug:  other suffixes = (none)
kdebug:  search only with suffix = 0
kdebug:  numeric format value = 5
kdebug:  runtime generation program = (none)
kdebug:  extra program args = (none)
kdebug:  program enabled = 0
kdebug:  program enable level = 0
! Variable cx has been obliterated.
to be read again 
   ;
* \mode:=cx;
   mag:=0+240/300; nonstopmode; input cmr10
? 
! Emergency stop.
to be read again 
   ;
* \mode:=cx;
   mag:=0+240/300; nonstopmode; input cmr10
Transcript written on mfput.log.
grep: can't open cmr10.log
mktexpk: `mf \mode:=cx; mag:=0+240/300; nonstopmode; input cmr10' failed to make 
cmr10.240pk.
xdvi.bin: Can't find font cmr10.240pk
xdvi.bin: Not all pixel files were found


Any suggestions or help in the right direction would be well appreicated

--Vic

Victor P. Tisone   Computer System Management Team (CSMT)
[EMAIL PROTECTED]voice: (303)497-1519  fax: (303)497-1589
High Altitude Observatory  P.O. Box 3000 Boulder CO 80307  USA