At 17:19 -0700 6/20/12, mason k wrote: >Thanks. I went and refreshed my memory on how Mac handles environment, and >ended up at this <http://stackoverflow.com/a/4567308/86432>stackoverflow >answer answer, and went with ~/.launchd.conf > >On Tuesday, June 19, 2012 12:32:35 PM UTC-4, Rich Siegel wrote: > >On Tuesday, June 19, 2012, mason k ><<mailto:mason.kra...@gmail.com>mason.kra...@gmail.com> wrote: > >>bbedit doesn't seem to be sourcing ~/.profile or ~/.bashrc before it runs. > >GUI applications don't get your bash (or other shell) >customizations; you need to use ~/.MacOSX/environment.plist. See ><<http://developer.apple.com/library/mac/#qa/qa1067/_index.html>http://developer.apple.com/library/mac/#qa/qa1067/_index.html>. > >R.
BBEdit and other applications can be run from a Terminal session. If you start up BBEdit using the bbedit tool to open a file with a command you will become a process as a child of Terminal.app which will have your environment and other settings in .tcshrc for me or .profile for folks who didn't learn the Apple command line in MPW. I start up a BBEdit worksheet that way and use stored startup lines inside which open other text files when I want them. -- Applescript syntax is like English spelling: Roughly, though not thoroughly, thought through. -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
