On Sun, May 26, 2002 at 03:16:32PM -0600, Idris S Hamid wrote:
> kpsewhich -expand-var=\$TEXMF
>
> worked for my texmf-var. I guess TeXLive does it automatically for windows,
> for I never had to that there. Is there a reason TeXLive does not configure
> texmf-var for UNIX immediately upon inst
kpsewhich -expand-var=\$TEXMF
worked for my texmf-var. I guess TeXLive does it automatically for windows,
for I never had to that there. Is there a reason TeXLive does not configure
texmf-var for UNIX immediately upon installation?
Thnx & best wishes
Idris
--
Dr. Idris S Hamid
Department of
> for I never had to that there. Is there a reason TeXLive does not configure
> texmf-var for UNIX immediately upon installation?
While TeX Live contains teTeX, it has it's own installation procedure. You
are asking at the wrong list. Please, consult the TeX Live documentation
for the right plac
On Sunday 26 May 2002 07:50, Thomas Esser wrote:
> > 1. I can't get my path commands to stick. When I issue
> > export PATH=$PATH:/usr/TeX/bin/i386-linux
> > I have to reissue it each time I log in and sometimes more often. I have
> > issued this command as root, and the problem still wont go away
On Sunday 26 May 2002 10:09, David Kastrup wrote:
> chmod +x /usr/TeX/bin/i386-linux/oxdvi
It works now! But unfortunately it only works on regular TeX files and crashes
on 16-bit dvi files. This is sad, since it worked well in fpTeX (owindvi).
Now it's onto testing odvips:-)
Thnx again!
Best
> :~> /usr/TeX/bin/i386-linux/oxdvi -version
> xdvi(k) version 22.40b for Omega
That's ok, So the script and the binary behind it both work.
> I use KDE, which can make links to various programs through such shell
> scripts. So when I mouse-click on the xdvi shell script (or a link to it),
I
> What happens if you start a shell and type
>/usr/TeX/bin/i386-linux/oxdvi -version
> in it?
:~> /usr/TeX/bin/i386-linux/oxdvi -version
xdvi(k) version 22.40b for Omega
Copyright (C) 1990-2001 Paul Vojta.
Primary author of Xdvi: Paul Vojta;
Xdvi-k maintainers:
:
There is NO WARRANTY of anyth
Idris Samawi Hamid <[EMAIL PROTECTED]> writes:
> >Just check if the oxdvi script exists in
> /usr/TeX/bin/i386-linux.
>
> Oh it's definitely there! I even tried to edit it to no
> avail. Clicking on it gives
>
> Couldn't find the program 'oxdvi''
chmod +x /usr/TeX/bin/i386-linux/oxdvi
And c
> avail. Clicking on it gives
> Couldn't find the program 'oxdvi''
What happens if you start a shell and type
/usr/TeX/bin/i386-linux/oxdvi -version
in it?
BTW: what do you mean by "Clicking on it"? Which application are you
using to start oxdvi by "Clicking on it"?
Thomas
>Just check if the oxdvi script exists in
/usr/TeX/bin/i386-linux.
Oh it's definitely there! I even tried to edit it to no
avail. Clicking on it gives
Couldn't find the program 'oxdvi''
But clicking on the xdvi script works fine.
About texmf-var, I just dumped my stuff into the texmf-
var cr
On Sun, May 26, 2002 at 09:38:59AM +0200, David Kastrup wrote:
> Ok, that settles .profile. Now why is your advice bad, bad, bad for
> the system-wide configuration, as well? Because we nowadays have
> Linux distributions that can be upgraded. And /etc/profile is sure to
> be under the control
Greg Black <[EMAIL PROTECTED]> writes:
> David Kastrup wrote:
>
> | Ok, that settles .profile. Now why is your advice bad, bad, bad for
> | the system-wide configuration, as well? Because we nowadays have
> | Linux distributions that can be upgraded. And /etc/profile is sure to
> | be under t
David Kastrup wrote:
| Ok, that settles .profile. Now why is your advice bad, bad, bad for
| the system-wide configuration, as well? Because we nowadays have
| Linux distributions that can be upgraded. And /etc/profile is sure to
| be under the control of the upgrade process which will require
Thomas Esser <[EMAIL PROTECTED]> writes:
> > 1. I can't get my path commands to stick. When I issue
> > export PATH=$PATH:/usr/TeX/bin/i386-linux
> > I have to reissue it each time I log in and sometimes more often. I have
> > issued this command as root, and the problem still wont go away;
>
>
> 1. I can't get my path commands to stick. When I issue
> export PATH=$PATH:/usr/TeX/bin/i386-linux
> I have to reissue it each time I log in and sometimes more often. I have
> issued this command as root, and the problem still wont go away;
environment variables are only passed to child proces
> 1. I can't get my path commands to stick. When I issue
> export PATH=$PATH:/usr/TeX/bin/i386-linux
> I have to reissue it each time I log in and sometimes more often. I have
> issued this command as root, and the problem still wont go away;
To be more precise, I have to reexport the path each
Dear folk,
I am just switching (finally!) to Linux from Windows (Suse 8.0) and I'm
running into a number of configuration problems (note that I am very new to
Linux/Unix as well). I installed teTeX from TeXLive6 (Suse actually has a
more recent teTeX but I need Omega1.15:->):
1. I can't get m
17 matches
Mail list logo