Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'a few observations...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
a few observations...
Authored by: thatch on Nov 14, '02 08:59:08PM

mithras,

My settings are already in ~/.tcshrc. Color, as well as case insensitive tab completion and save merge history, has worked fine without screen invoked. So, I've never had a reason to change the $TERM env variable.

It occurred to me that maybe the system installed version of screen is different from the latest build ported through fink. Upon checking, I found that the system version in 10.2.1 is 3.09.10 (FAU) 4-Sep-01 and the fink version is 3.9.11-1. I will upgrade and see if it makes any difference.

I'll carry this onto the forums from here on out should I need to continue. Thanks for your reply.



[ Reply to This | # ]
a few observations...
Authored by: bluehz on Nov 15, '02 11:17:48PM

I also have two version of screen - the newer being in my fink install. Other than the obvious (calling by path) is there an easy way to get cmd to default to teh fink install in the case of identical commands like this. For example - unlaltered - if I type screen - I get the /usr/bin/screen as opposed to the fink.



[ Reply to This | # ]
a few observations...
Authored by: thatch on Nov 16, '02 03:14:15AM

bluehz, your $PATH must have /sw before /usr/bin and then you should see:

% which screen
/sw/bin/screen



[ Reply to This | # ]
Kills XDarwin
Authored by: bluehz on Nov 17, '02 07:41:20AM

I noticed after initiating this hint - I was no longer able to launch XDarwin. I don't normally use .cshrc and .tcshrc (instead keeping old style ~/Library/init/tcsh file), but I created .cshrc and .tcshrc file just for this hint. I could then no longer launch XDarwin, Delete teh two "dot" files and XDarwin launches fine again.



[ Reply to This | # ]
Re: Kills XDarwin
Authored by: thatch on Nov 17, '02 06:07:56PM

bluehz,

Using the old style /Library/init/tcsh/*.mine file in Jaguar can cause problems. I'd recommend using only the ~/.tcshrc and ~/.login files to tweak your environment stuff, except for aliases.mine which still seems to work fine for me. See the hint on this site for re-establishing your .mine file functionality if you are on Jaguar.



[ Reply to This | # ]
Re: Kills XDarwin
Authored by: bluehz on Nov 18, '02 08:38:14AM

I have sorta been meaning to switch to the new style - but every time I make attempts at switching - I get more problems than good. I guess the old style is just comfortable...hahahah (weird to say about pure unix guts...ehhh). I'll take a look and see if I can find the articles talking about this on OS X Hints and see if I can give it another shot. Not sure how my enabling the .tcshrc will help with this hint since it clearly caused a problem with my XDarwin once enabled.



[ Reply to This | # ]
Re: Kills XDarwin
Authored by: bluehz on Nov 19, '02 11:33:24AM

I have read the docs on old-style tcsh dir and fail to see any problems generated from this method. Can you point me to some specific docs?



[ Reply to This | # ]
a few observations...
Authored by: mithras on Nov 18, '02 11:19:48AM

Sorry I didn't make this clear before.

Screen *changes* the $TERM environment variable when it starts up. That variable is commonly checked by terminal programs when they are deciding how to display their output. So programs that worked fine when $TERM was not set, or was set to 'Apple Terminal' or somesuch, might stop working under screen.

So adding a line in your .tcshrc to change $TERM back to blank or whatever it was before might fix things.



[ Reply to This | # ]