Can you do a "which emacs" to see which one is being called?
On Thu, 21 Nov 2002, Viktor Haag wrote:
> Massimo Marino writes:
> > Viktor,
> >
> > I checked the PATH and indeed you got it right. Now, shouldn't
> > this be taken care by init.sh ?
>
> It should be. You can check to make sure tha
Massimo Marino writes:
> Viktor,
>
> I checked the PATH and indeed you got it right. Now, shouldn't
> this be taken care by init.sh ?
It should be. You can check to make sure that /sw/bin/init.sh
exists and does reset the PATH.
Then you should check that you don't re-reset the PATH *after*
i
Viktor,
I started looking at all sym links and they all looked fine: if I issue
directly those ones then the correct emacs starts and emacs opens its
window.
I checked the PATH and indeed you got it right. Now, shouldn't this be
taken care by init.sh ?
On Thursday, November 21, 2002, at 10:52
Massimo Marino writes:
> If I issue emacs --v the reply is again 21.1.1 and cannot open
> its own window on Xfree86 and currently it is the only app
> which cannot do that. All others work fine (nedit, xterm,
> Eterm, external clients) so it is not a problem of DISPLAY
> setting.
This sound
K guys, now this is weird.
I removed emacs with Fink, then physically removed emacs from my system, included debian package and tar file. I downloaded again emacs21.2 tar, rebuilt and installed. All went smoothly without errors.
If I issue emacs --v the reply is again 21.1.1 and cannot open its
