Yes, I downloaded Lingon and made a periodic job with it, as well as another "keepalive," which worked. Thanks for letting me know about it!
On May 29, 9:18 pm, Sesquipedalian <[EMAIL PROTECTED]> wrote: > Yes. Google launchd to learn more, and/or read the man pages for > launchd, launchctl, and launchd.plist. The main thing you will be > interested in is the launchd.plist. As mentioned above, Lingon > (http://www.macupdate.com/info.php/id/19879) is a nice, free GUI for > making lauchd.plists. > > On May 29, 9:36 am, Daniel <[EMAIL PROTECTED]> wrote: > > > Thanks! And I'll probably figure this out for myself, but can it do > > periodic actions? Like to replace cron, which has been disabled in > > Tiger? > > > On May 28, 11:06 am, Sesquipedalian <[EMAIL PROTECTED]> wrote: > > > > Yes, it will work for pretty much any native application. Java > > > applications and the like may or may not work, but it never hurts to > > > try. If you want, you can use the freeware Lingon to give you a nice > > > graphical interface for making launch agents. They are very > > > versatile, and can do much more than just this sort of very simple > > > action. > > > > On May 28, 9:57 am, Daniel <[EMAIL PROTECTED]> wrote: > > > > > That is an awesome method that I did not know about. Everybody, > > > > ignore my way—this is much better. > > > > > I assume that works for any application? Just change the "Label" and > > > > the name of the file to match, and then change the "ProgramArguments" > > > > to the other program's path? > > > > > On May 27, 9:39 am, Sesquipedalian <[EMAIL PROTECTED]> wrote: > > > > > > I accomplish this by using a launch agent to start QS instead of a > > > > > login item. The one I use also automatically restarts QS if it ever > > > > > crashes. > > > > > > To use this method, first remove QS from your login items (you can do > > > > > this by unchecking "Start at login" in QS's preferences). Then save > > > > > the following text into a plain text file called > > > > > com.jonstovell.QuicksilverKeepAlive.plist in ~/Library/LaunchAgents. > > > > > > Next time you log in, QS should start much sooner in the login > > > > > process. Note that this assumes that Quicksilver is installed in your > > > > > Applications folder. If you have it somewhere else, modify the path > > > > > near the bottom of the plist to point to the proper location of > > > > > Quicksilver.app (but leave the stuff from "Contents" onward alone). > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" > > > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> > > > > > <plist version="1.0"> > > > > > <dict> > > > > > <key>Disabled</key> > > > > > <false/> > > > > > <key>KeepAlive</key> > > > > > <dict> > > > > > <key>SuccessfulExit</key> > > > > > <false/> > > > > > </dict> > > > > > <key>Label</key> > > > > > <string>com.jonstovell.QuicksilverKeepAlive</string> > > > > > <key>ProgramArguments</key> > > > > > <array> > > > > > > > > > > <string>/Applications/Quicksilver.app/Contents/MacOS/Quicksilver</ > > > > > string> > > > > > </array> > > > > > </dict> > > > > > </plist> > > > > > > On May 26, 7:59 am, Sciamachy <[EMAIL PROTECTED]> wrote: > > > > > > > I now use QS as the main method for launching my apps, so it would > > > > > > make sense for it to load first of all the toolbar apps that load up > > > > > > on login (I have a bunch of them so, given that QS loads next to > > > > > > last > > > > > > at the moment, I have quite a wait till I can use it). Any ideas?
