mnewman, sounds like you have the problem I used to have as I mentioned in prior posts. I couldn't figure out where the extra sourcing was coming from. I tried commenting out the sourcing from various user defined files as well as changing the order of their presence but to no avail.

Are you on 10.2.3? And is this redundancy only in xterm or in terminal.app or both? Also, is it with your $PATH and $INFOPATH but not in your $MANPATH? That's how it was for me, and with either/or in xterm or terminal.app.

What TiMan was showing in his post was that you can use cat and grep to find the actual source in those files, /sw/bin/init.sh and /sw/bin/init.csh. In his examples, if you issue the command line, you should get the second line in the output for each. Try it and you will see.

Sorry. What I meant is, if you have fink installed, it adds /usr/X11R6/bin to your path. If you add /usr/X11R6/bin to your path yourself, it will appear twice. Clear as mud? What I illustrated above was where in the fink file (/sw/bin/init.sh or /sw/bin/init.csh) /usr/X11R6/bin gets added to your path. So, if you have fink installed, and you've manually added /usr/X11R6/bin to your path, stop manually adding it, and the redundancy should disappear. Let me know how it turns out.

OK - Fink is installed and I see how it adds /usr/X11R6/bin.

As far as I know, I've removed all references to /usr/X11R6/bin from any of my customization files. But, I still have two iterations in when I look at the path in xterm, but only one when I look in Terminal.app.

Also, when I start Terminal.app I get this:

"Too many ('s."

Any idea where that's coming from? The only files I've knowingly edited are .xinitrc and .tcshrc

Here they are:

.tcshrc:

source /sw/bin/init.csh
if( ! $?DISPLAY ) then
setenv DISPLAY :0.0
endif
set autolist

.xinitrc:

source /sw/bin/init.sh
/usr/X11R6/bin/quartz-wm

I think your problem is in your ~/.tcshrc file. There must an extra `\n` which doesn't show on the screen. Delete all what's there and type it again by hand, don't copy/paste.


Cheers...

Did that. Still get the "too many ('s" line when I start up Terminal.app.

Looked for all these files:

/etc/csh.cshrc
/usr/share/init/tcsh/rc
/usr/share/init/tcsh/environment
~/Library/init/tcsh/environment.mine
/usr/share/init/tcsh/tcsh.defaults
~/Library/init/tcsh/rc.mine
/usr/share/init/tcsh/aliases
~/Library/init/tcsh/aliases.mine
/usr/share/init/tcsh/completions
~/Library/init/tcsh/completions.mine
/etc/csh.login
/usr/share/init/tcsh/login
~/Library/init/tcsh/path
~/Library/init/tcsh/login.mine
~/.tcshrc
(~/.cshrc)
~/.login
~/.history
~/.cshdirs

I don't have any of the "init" directories shown and the only files I have do not mention /usr/X11R6/bin. As far as I can see, the only initialization file I have that mentions /usr/X11R6/bin is the one that belongs to Fink.

Nevertheless, my path has two /usr/X11R6/bin's.

What a mystery....

I'm on 10.2.3.

I don't have $INFOPATH or $MANPATH defined.

The reduncancy only is in xterm, not terminal.app. But, I do have that odd error ("too many 0's") when I start terminal.app.

thanks

I see. Please, do the same as I told you above (delete all and write by hand) to your ~/.cshrc file.


Cheers...

You source /sw/bin/init.csh in your tcshrc, and /sw/bin/init.sh in your .xinitrc. That's unnecessary. Comment out "source /sw/bin/init.sh" in .xinitrc so it looks like this:

#source /sw/bin/init.sh

and test.

I'm fairly certain you have the same problem I described in above posts. In your xterm, you can type 'env' without the single quotes and see all path info including $MANPATH and $INFOPATH, (infopath is only if you have installed the texinfo system but you should have a manpath). But that's all kind of moot since the problem is probably in $PATH and, if you had it, $INFOPATH.

BTW, I never had a source line in my ~/.xinitrc. Yet, I still had the redundancies from an xterm and not a terminal window. But since it was at the end of the path, I didn't worry about it much.

Your odd error, as you call it, could be from incorrect spacing in some of your lines. You reported, "too many ('s.", originally. And I think that is what you meant when you next reported the similar, "too many 0's", above. Anyway, try adding a space in between the "if" and the "(".

If that doesn't work, check the end of every line and make certain you don't have a space at the end where it shouldn't be. You can do this in a couple of different ways, but as sao suggests, if you retype the whole thing you will get it right being careful about those spaces.

I got rid of my .xinitrc file.

I still have two iterations of the /usr/X11R6/bin path in my xterm environment.

Here's what the two customization files I have left look like:

Last login: Thu Jan 16 16:26:18 on ttyp2
Welcome to Darwin!
Too many ('s.
[Newmans-iBook:~] mnewman% cat .tcshrc
source /sw/bin/init.csh
if ( ! $?DISPLAY) then
setenv DISPLAY :0.0
endif
set autolist

[Newmans-iBook:~] mnewman% cat .login
## System-wide tcsh login file
#


# Set paths
set path = ( \
. \
~/bin \
/Developer/Tools /Developer/Applications \ /usr/local/bin /usr/bin /bin \
/usr/local/sbin /usr/sbin /sbin
)

[Newmans-iBook:~] mnewman% env
HOME=/Users/mnewman
SHELL=/bin/tcsh
USER=mnewman
LANG=en_US
PATH=/sw/bin:/sw/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
QDTEXT_ANTIALIASING=1
QDTEXT_MINSIZE=12
__CF_USER_TEXT_ENCODING=0x1F5:0:0
TERM=vt100
TERMCAP=����
TERM_PROGRAM=Apple_Terminal
TERM_PROGRAM_VERSION=81
LOGNAME=mnewman
HOSTTYPE=macintosh
VENDOR=apple
OSTYPE=darwin
MACHTYPE=powerpc
SHLVL=1
PWD=/Users/mnewman
GROUP=staff
HOST=Newmans-iBook.local.
MANPATH=/sw/share/man:/sw/man:/usr/local/share/man:/usr/local/man:/usr/share/man:/usr/X11R6/man
INFOPATH=/sw/share/info:/sw/info:/usr/local/share/info:/usr/local/lib/info:/usr/local/info:/usr/share/info
PERL5LIB=/sw/lib/perl5
DISPLAY=:0.0
[Newmans-iBook:~] mnewman%

I fixed the space between 'if' and '(' by manually retyping the whole file, as suggested.

Thanks for your patience, but I'm still at a loss.

By the way, when I still had the .xinitrc file, but commented out the 'source' statement, that caused the xterm window to draw behind the Mac menu bar, leaving the top of the xterm window hidden. Removing the entire .xinitrc file fixed that.

mnewman, what window manager are you using for the X window system? If it's Apple's X11, I haven't messed with that yet and so I can't comment on that. I just use windowmaker. But if getting rid of your ~/.xinitrc is working for you, I guess that's okay.

Sorry my suggestion with the spaces didn't work for you. I assume you're using a text editor to make the changes, like pico? Please confirm what editor you use.

Could you try leaving out the 'if' line entirely? I don't use it, just the 'setenv Display :0.0'.

I hope the format of your set path area of your ~/.login is more like this:The open and close parenthesis should line up perfectly. Also, the escape, ( \ ), characters are only at the end of the visual line but mean to continue on the next line. I don't know for certain if this would make the difference for you but the format should be neater in this way. I suspect that you've copied and pasted bits and pieces of code into your config files, possibly from a browser, which can add spaces and newline, ( \n ), into your code or just make things messy.

You posted your ~/.tcshrc and ~/.login. But what about your ~/.cshrc? Are you still using it? Please post it if you are.

The env that you posted was from terminal.app and not xterm, correct? It shows the paths are perfectly the way you wanted them less the /Developer/Tools and /Developer/Applications, right? Let's see the xterm with that env command which will show your redundancy; (a shorter way would be 'echo $PATH' and then 'echo $MANPATH' and then 'echo $INFOPATH', without the single quotes of course).

Thatch, I hope I can answer all your questions:

I am using Apple's quaartz.wm. It doesn't seem to need an .xinitrc. In fact, if I use one, every x11 application I open is hidden under the Mac menu bar.
I am using pico.
It turns out the "too many ('s" message came because I was missing an escape on the last line of the set path statement....
I'm not. I wouldn't know what to put in a .cshrc file that can't go in the .tcshrc file.
Correct.
Here it is:

PWD=/Users/mnewman
QDTEXT_ANTIALIASING=1
USER=mnewman
LANG=en_US
DISPLAY=:0.0
SHLVL=2
SHELL=/bin/tcsh
HOME=/Users/mnewman
PATH=/sw/bin:/sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/mnewman:/usr/X11R6/bin:/usr/X11R6/bin
__CF_USER_TEXT_ENCODING=0x1F5:0:0
QDTEXT_MINSIZE=12
_=/usr/X11R6/bin/xterm
TERM=xterm
WINDOWID=4194318
LOGNAME=mnewman
HOSTTYPE=macintosh
VENDOR=apple
OSTYPE=darwin
MACHTYPE=powerpc
GROUP=staff
HOST=Newmans-iBook.local.
MANPATH=/sw/share/man:/sw/man:/usr/local/share/man:/usr/local/man:/usr/share/man:/usr/X11R6/man
INFOPATH=/sw/share/info:/sw/info:/usr/local/share/info:/usr/local/lib/info:/usr/local/info:/usr/share/info
PERL5LIB=/sw/lib/perl5

Thanks again for your help and patience.

mnewman, thanks for answering all the questions. I see now, as you said, that you didn't include an escape near the end of your path. Glad you figured it out. So, now back to the redundancy in the path.

I just have one more suggestion. Move the 'source /sw/bin/init.csh' line to just after your path in ~/.login. Hopefully, that will get rid of the redundancy and include your /Developer/Tools and /Developer/Applications. For me, and this was a while back, it did include all that I needed but didn't fix the extra /usr/X11R6/bin in my path. But I hope it works for you.

I see in your env output that you have SHLVL=2. Are you running the xterm side by side with terminal? I have found that to cause some strange irregularities. I would just test one application at a time, xterm or terminal. And to test changes made in xterm, I usually had to quit XDarwin and launch it again, unlike terminal.app where I could just rehash or exit the window and start a new one again to see the changes. I don't know about Apple's X11 though.

I made this change and it did remove the redundancy. Do you know why?

I don't think that Apple's X11 is processing my .login file. Take a look at the following. It shows my .login file, my .tcshrc file, the env from xterm and my env from terminal.app. None of the path specified in the .login file is in the xterm environment:

BTW - I do sometimes have both terminal.app and xterm open at the same time. For purposes of gathering the above, I had them open one at a time.

[edit: readability -mt]

there are no binary executables in /Developer/Applications so it is specious to have this in the path.

apple's X11 xterm is not a login shell, so it doesn't source login startup items, i.e., ~/.login (tcsh)

I've just been re-reading this thread and realize that I don't have a /usr/share/init/ directory.

I wonder why not? Where should it have come from?

Whew, this is an old post. That referred to OS 10.1, so if you're using 10.2 you'll want to check /usr/share/tcsh/examples.

The order that the sourcing is called upon makes the difference.
I agree and also wonder why mnewman wants the developer tools called before /usr/*.
I thought that was a 'given'. But apparently the thread did need updating for Jaguar.

mnewman,
About those instructions in /usr/share/tcsh/examples/README; the second part of that file is residual from OS 10.1, and so the file is not exactly accurate. You can still utilize the customization part if you want although, other than the aliases.mine, I didn't find those files to always work correctly in Jaguar. The important part is the first part. Once you get those sourcing's made up as instructed, then please check your env and post the results.

well, it doesn't really matter as long as you know the binaries are unique. all the binaries in /developer/tools are unique, here, so i don't see a problem.

if a different GetFileInfo were installed in /usr/local/bin , it would never get called with his path config.

there is a modest performance penalty to scan many path elements, but hashing minimizes this.

there are only a few tools in /developer/tools that i ever want to run, and they're symlink'd in ~/bin/ so i don't have more path elements than are necessary.

OIC, that's true enough. It just didn't look the same as what I was used to seeing.

Another thing too.... what about his having the dot (.) directory in his path? Isn't that supposed to be a security risk of some sort?