From: Alex S. <gr...@go...> - 2002-09-19 00:18:56
|
Mac OS X 10.1.5, latest CVS of Fire. When I "Toggle Buddy Window Trasparency", the buddy list contents go black, and the window loses its shadow. I'm guessing blacking out the buddy list is *not* the expected outcome ;) Alex |
From: Jason T. <tow...@ma...> - 2002-09-19 00:36:09
|
On Wednesday, September 18, 2002, at 05:18 PM, Alex Satrapa wrote: > Mac OS X 10.1.5, latest CVS of Fire. > > When I "Toggle Buddy Window Trasparency", the buddy list contents go > black, and the window loses its shadow. > > I'm guessing blacking out the buddy list is *not* the expected outcome > ;) Update to the latest and rebuild. The fix is checked in... We were calling a function which is only available on 10.2 and generating an exception. -Jason |
From: Alex S. <gr...@go...> - 2002-09-19 04:31:20
|
On Thursday, September 19, 2002, at 10:35 , Jason Townsend wrote: > Update to the latest and rebuild. The fix is checked in... Is there a Project Builder equivalent to "cvs update -dP"? It seems that when I do a CVS update, it only checks the stuff that is highlighted (ie: the project file, a particular folder, or a particular file). Seems a bit backwards that I should need to use command-line CVS to maintain the code that Project Builder is supposed to be responsible for. Alex |
From: Jason T. <tow...@ma...> - 2002-09-20 01:40:23
|
On Wednesday, September 18, 2002, at 09:31 PM, Alex Satrapa wrote: > On Thursday, September 19, 2002, at 10:35 , Jason Townsend wrote: >> Update to the latest and rebuild. The fix is checked in... > > Is there a Project Builder equivalent to "cvs update -dP"? It seems > that when I do a CVS update, it only checks the stuff that is > highlighted (ie: the project file, a particular folder, or a > particular file). > > Seems a bit backwards that I should need to use command-line CVS to > maintain the code that Project Builder is supposed to be responsible > for. I always use command line CVS, since I haven't figured out how to set up Project Builder to work with CVS over SSH which is required to modify the repository. It works very well, and is fairly easy to use, especially if all you need to do is update to the latest TOT sources. If you are using Project Builder, you should select the top level item (represents the whole project) and it will update all files the project refers to. This can sometimes have problems if new directories/files were added and aren't referred to in your version of the project. Maybe others on the list can recommend a good GUI CVS client? I used to use Mac CVS Pro and Mac CVS Client on Mac OS 9, but as far as I know they don't support > 31 character filenames in their Mac OS X incarnations... jCVS might work. -Jason |
From: Alex S. <gr...@go...> - 2002-09-20 02:13:21
|
On Friday, September 20, 2002, at 11:41 , Jason Townsend wrote: > It works very well, and is fairly easy to use, especially if all you > need to do is update to the latest TOT sources. Oh... I'm familiar with all the usual CVS stuff - branching, merging, marking releases, yadda yadda. I was just concerned that something as simple as "cvs update -d" wasn't available through the CVS menu in Project Builder. > If you are using Project Builder, you should select the top level item > (represents the whole project) and it will update all files the project > refers to. Okay, I'm obviously clicking the wrong way - when I do this, it seems to only update the .pbproj file. I had to do the CVS update from the command line to get the changes to whatever it was that was supposed to make the "Toggle Buddy Window Transparency" item actually function like "Toggle Buddy Window Blackout". Catchya Alex |
From: Graham B. <gb...@ta...> - 2002-09-20 15:20:35
|
On Thursday, Sep 19, 2002, at 20:41 US/Central, Jason Townsend wrote: > > I always use command line CVS, since I haven't figured out how to set > up Project Builder to work with CVS over SSH which is required to > modify the repository. > Here is how I did it.... I added this to my .tcshrc: setenv CVS_RSH ssh And I set up ssh agent to work within all my shells. Once the agent has the RSA keys, then Project Builder can connect to the CVS via SSH. Here is how I set up the ssh agent: I have a script called launch-ssh-agent in the bin directory in my home dir with the following: #!/bin/sh if ! test -f /tmp/$USER-ssh-agent; then ssh-agent > /tmp/$USER-ssh-agent-temp grep -v echo - < /tmp/$USER-ssh-agent-temp >& /tmp/$USER-ssh-agent rm /tmp/$USER-ssh-agent-temp fi and in my .tcshrc I have these two lines: ~/bin/launch-ssh-agent source /tmp/{$USER}-ssh-agent This may not be the most secure way of doing the agent, but no one else uses my computer, so it is fine with me. Hope this helps. > > -Jason > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > fire-development mailing list > fir...@li... > https://lists.sourceforge.net/lists/listinfo/fire-development > > ---------------------------------------------- Graham Booker Texas A&M University gb...@ta... Graduate Student in ELEN ---------------------------------------------- |
From: Alex S. <gr...@go...> - 2002-09-21 07:34:06
Attachments:
ssh-enabler-script
|
On Saturday, September 21, 2002, at 01:20 , Graham Booker wrote: > Here is how I did it.... > I added this to my .tcshrc: > setenv CVS_RSH ssh It also works if you add the key "CVS_RSH" with the string value "ssh" to your ~/.MacOSX/environment.plist file. If you're working consistently from one CVS repository, you can also store a "CVS_ROOT" in the environment.plist file too. > if ! test -f /tmp/$USER-ssh-agent; then > ssh-agent > /tmp/$USER-ssh-agent-temp A long time ago, the OpenSSH people stopped using directories like this because it was trivially easy to guess where a particular user's SSH authentication socket would be hidden. SSH now uses random sequences in ssh-<sequence> to store your authentication socket. I use zsh, and I have my ssh-enabler script run from my ~/.zshrc - note that my script is intended to be run from hosts that mount my home directory from a common "home" server. It works as-is for a stand-alone machine, with a little redundancy in directories. What I *don't* have yet is a script to kill the ssh-agent when I log out - so when I log out I usually have an ssh-agent running that still has my keys in it. This is bad from the paranoid point of view (in much the same way that it's bad for Fire to be storing my GPG passphrase in memory). With the supplied script, I still have to open a terminal session to type in my passphrase (but I'll only be asked for the passphrase the first time I open a terminal session, until the machine is shut down or rebooted). |
From: Steven W. R. <mai...@ge...> - 2002-10-11 21:36:55
|
yahoo_process_notify I am getting a packet which only has a key of 16, value "Error: failed to validate user freegeek" This means msg is nil, which then causes the subsequent g_strncasecmp to crash Steve |