Just a note about using BBEdit for editing commit messages: I use 
'/usr/local/bin/bbedit --wait --resume' for that purpose, mainly to allow the 
commit message to be written before returning control to the invoking process. 
The "--wait" means "wait for document to be closed in BBEdit" and "--resume" 
means "restore focus to the invoking application when the document is closed in 
BBEdit".

HTH

On 14/06/2012, at 13:34 , Phil Dobbin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 13/06/2012 23:25, bobPCL wrote:
> 
>> I can open a terminal window in Mac Lion and run the command:
>> 
>>> bbedit file.name
>> 
>> and bbedit works, and says it is in /usr/bin/bbedit.
>> 
>> If I try to put in my .profile: export EDITOR='/usr/bin/bbedit' I get
>> "-bash: edit: command not found". Or the same thing happens if I put the
>> command in .bashrc. Or if I leave off the /usr/bin and put it in either
>> place. Always the same error.
>> 
>> That being said if I put /usr/bin/edit that works (but not for bbedit).
>> 
>> Would someone please let me know what I'm doing wrong? I'm running from
>> an account with admin access.
> 
> Try:
> 
> `export EDITOR=/usr/bin/bbedit` (without the backticks)
> 
> in your bash_profile (assuming when you installed the command line tools
> you chose `/usr/bin/`).
> 
> Similarly, you can use:
> 
> `export GIT_EDITOR=/usr/bin/bbedit`
> 
> for your git commit messages if you don't want to pass the `m` flag on
> your commits.
> 
> That will work if you run your shell as a login shell (see
> <https://rvm.io/support/faq/#shell_login> from the wonderful Wayne E.
> Seguin for a brief explanation).
> 
> Also, unfortunately, there is no `sudo update-alternatives --config
> editor` on OS X as there is GNU/Linux to make this scenario plainer.
> Blame FreeBSD :-)
> 
> Cheers,
> 
>  Phil...
> 
> - -- 
> But masters, remember that I am an ass.
> Though it be not written down,
> yet forget not that I am an ass.
> 
>       Wm. Shakespeare - Much Ado About Nothing
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQEcBAEBAgAGBQJP2Vu3AAoJEKpMeDHWT5ADsE8IAKtqYGtydTQouQBToMV+tfea
> jquUKm5RfcyLwyh3zCVaqyurDl4bWFNJ75YYo+5BW5TrqIDnN6gPMMH1aEqEo5zA
> 2AhGl6zu+OMIdhxVNBie7Pd6quGjXs204sj9yJAVDSPZJK22fqduUmgvedIS1QHb
> cgsj1lA+bMAXDzG7BdXXNG2o8leNvYe6kB4VzzMZc7dCV2MRAWyX0gleJek453Fx
> ox79gwmXmqJZhxprN6CdU6ShgUpAGBy7V1hXwtQF2mA3yjo3GzNRG5UhqaGFytZT
> AJBO6Grh4HryCRFKTB+IoFqI6/2kLvS9EtW8deEs764wPCx+9f4JvNx8qYSFg/I=
> =Fl2o
> -----END PGP SIGNATURE-----
> 

-- 
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 "[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>

Reply via email to