|
|
a few observations...
if those settings are configured in your .login or .profile, they won't carry over to the subshell launched by screen. make sure they're set in .tcshrc or .bashrc.
a few observations...
mithras,
a few observations...
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.
a few observations...
bluehz, your $PATH must have /sw before /usr/bin and then you should see:
Kills XDarwin
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.
Re: Kills XDarwin
bluehz,
Re: Kills XDarwin
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.
Re: Kills XDarwin
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?
a few observations...
Sorry I didn't make this clear before. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.15 seconds |
|