# Skipping profile parts while running through BBEdit

tags: bbedit  macOS  secrets

In Putting environment values in the keychain, I noted how I moved a bunch of sensitive info into the Keychain, but set env variables in the shell when I got a log-in shell. That has worked well, except for running a program through BBEdit. Every time I run a program, all that work is redone as BBEdit gets a new interactive shell. It takes a couple seconds for the secrets to load, and that’s annoying.

This isn’t a big deal. I have to figure out how to test whether BBEdit is the thing that started this shell. It turns out to be easy. I write a program to dump the environment:

I see I have plenty to choose from, and BBEDIT_CLIENT_INTERACTIVE looks like the best option:

Now I check that BBEDIT_CLIENT_INTERACTIVE is empty before I load up my secrets: