I tried adding the fink "test -r ..." line but it didn't change the $PATH 
in X11 (other .xinitrc changes did take)?
Is there an errant space or character in there?

As for the display export, I thought there was a reason that you did not 
want to explicitly set that, but that must be my bad memory or based on 
some other issue (will it do bad things to other things)?

I also tried Alex's solution, for example:
xterm -ls
...and it said "xterm Xt error: Can't open display:"
...which, of course, is fixed after doing an "export DISPLAY=:0"
However, there must be a nice set of instructions for doing this 
permanently?  Perhaps the following:
1) Edit .cshrc to export DISPLAY=:0
(will this be bad to do, in general)?
2) The next trick is the $PATH, which I somehow have to edit in .xinitrc - 
anyone have any ideas on the best way to override the PATH without 
breaking it on Tiger, and preferably without having to keep changing it 
to match Terminal's whenever (if ever) that changes?
3) When an X-app opens it sits there waiting for me to click the mouse 
with the corner pointer - any way to get it to just open and not wait for 
me to click the mouse to put the window somewhere?

I normally use X11 great for ssh -X and -Y, but this local stuff is a bit 
different.

Sorry if this is way off-topic...?

Thanks,
-Matt


On Fri, 12 May 2006, Christopher Bort wrote:

> On 05/12/06 at 10:55, Matt Kozak wrote:
>
>> Fink has inserted the needed $PATH to Terminal, but not to X11.  Can
>> anyone tell me how (or the "best" way) to make their paths identical so
>> that they can find the same stuff, especially fink's sw/ stuff?
>
> I don't know if it's the best way, but I've simply added the same line to
> my .xinitrc as the fink set-up script adds to you're shell's start-up
> script:
>
> test -r /sw/bin/init.sh && . /sw/bin/init.sh
>
>> If I figured out how to do this with Panther, I'm not sure how it may
>> be different on Tiger, if at all?  Now that I think about it, I was
>> using X-Darwin on Panther, so maybe it's an Apple X11 thing?  If I
>> run the stuff from Terminal, it acts like there's no X-environment.
>> Perhaps that's another issue entirely?
>
> You need to tell your shell what display to use (e.g., for bash you'd use
> something like `export DISPLAY=:0`).
> --
> Christopher Bort
> <[EMAIL PROTECTED]>
> <http://www.thehundredacre.net/>
>

Matthew Kozak
Systems Programmer/Administrator
--------------------------------
Haskin Shellfish Research Lab
6959 Miller Avenue
Port Norris, NJ 08349-3167
email: [EMAIL PROTECTED]
phone: 856-785-0074 x4325
fax: 856-785-1544
web: http://hsrl.rutgers.edu


_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to