I see similar behavior. I cannot get any diffs using BBEdit since the
9.1 update.
I mainly use the flow in the 'Browse' view in the local workspace. I
select a changed file and click on 'Remote Changes' where normally I
would see the "Getting list of changes" sheet followed by switching to
BBEdit
Huge essential feature for me too. I've written BBEdit support (it
didn't get past their google group moderation), and was writing here
in hopes for a debugging lead, as it seems to point to something with
command line diff. You could write BBEdit support too, to give it more
weight.
--~--~---
Huge essential feature for me too. I've posted to the BBEdit google
group, written BBEdit support and was writing here in hopes for a
debugging lead, as it seems to point to something with command line
diff. You could write BBEdit support too, to give it more weight.
--~--~-~--~~--
Same problem here.
On Dec 16, 6:41 pm, echo wrote:
> Huge essential feature for me too. I've posted to the BBEdit google
> group, written BBEdit support and was writing here in hopes for a
> debugging lead, as it seems to point to something with command line
> diff. You could write BBEdit suppor
Hi everyone,
Thanks to the great folks over at BareBones Software we know exactly
why this problem is occuring, we're working to get it fixed asap.
Sorry for the trouble, a fix will be out soon.
All the best,
- Dirk
the Versions team
On Dec 17, 5:05 pm, Tim Gray wrote:
> Same problem here.
>
Appreciate the communication and prompt turnaround!
On Dec 19, 3:13 pm, Dirk Stoop wrote:
> Hi everyone,
>
> Thanks to the great folks over at BareBones Software we know exactly
> why this problem is occuring, we're working to get it fixed asap.
>
> Sorry for the trouble, a fix will be out soon.
Thanks Dirk. Given the nature of the (likely) fix or the problem is
it then going to not work with previous versions of BBEdit?
On Dec 19, 3:13 pm, Dirk Stoop wrote:
> Hi everyone,
>
> Thanks to the great folks over at BareBones Software we know exactly
> why this problem is occuring, we're w
Hi Haikuti,
We're planning to remain compatible with older versions too. Versions
currently uses the BBEdit bbdiff command line tool from it's
uninstalled location in the application bundle, which changed in 9.1.
We're investigating using BBEdit's AppleEvent interface in the next
releas
Would it make sense to use the INSTALLED version first and if not
found in the installed path: /usr/bin/bbdiff
If not found only then use the uninstalled version in the bundle?
On Dec 21, 12:03 pm, Dirk Stoop wrote:
> Hi Haikuti,
>
> We're planning to remain compatible with older versions too.
Yes, that would absolutely make sense.
But using the AppleEvent interface in BBEdit makes even more sense,
for the following two reasons:
1. The location of the bbdiff command line tool inside the application
bundle might change again in a later release (the location of this
file inside the app
Seems like you'll essentially be reimplementing their command line
tool, which doesn't make sense on the surface of it.
Any performance hit for using the apple event?
The only reason I can think of to *not* use the installed version of
the command line tool is you might have someone who doesn't
For a quick fix when you have the command line tools installed: create
a symlink of the bbdiff command line tool in BBEdit.app/Contents/
Resources/ (that's where it used to be).
In the terminal (when BBEdit is put in /Applications), type:
ln -s /usr/bin/bbdiff /Applications/BBEdit.app/Contents/
Thanks for the work-around. Worked like a charm, and should hol me
over until the next release of Versions.
On Dec 24 2008, 5:51 pm, mac joost wrote:
> For a quick fix when you have the command line tools installed: create
> a symlink of the bbdiff command line tool in BBEdit.app/Contents/
> Res
Ditto - Thanks this did the trick. I did notice in that dir that there
is a bbdiff1
On Jan 7, 11:19 am, Bala wrote:
> Thanks for the work-around. Worked like a charm, and should hol me
> over until the next release of Versions.
>
> On Dec 24 2008, 5:51 pm, mac joost wrote:
>
> > For a quick fix
On Dec 22 2008, 5:02 am, Dirk Stoop wrote:
> 1. The location of the bbdiff command line tool inside the application
> bundle might change again in a later release (the location of this
> file inside the app is not a way to interact with it that's endorsed
> or recommended by BareBones Software
I agree with others who suggested in essence that anyone serious
enough to be using Subversion will have the BBEdit's command tools
installed.
I use Subversion seriously, but don't use BBEdit as my primary editor,
and don't recall whether I have the tools installed or not. You're
welcome t
On 11 Feb 2009, at 19:37, Quinn Taylor wrote:
>> I agree with others who suggested in essence that anyone serious
>> enough to be using Subversion will have the BBEdit's command tools
>> installed.
>
> I use Subversion seriously, but don't use BBEdit as my primary
> editor, and don't recall whe
On Feb 12, 2009, at 5:29 AM, Paul Willis wrote:
On 11 Feb 2009, at 19:37, Quinn Taylor wrote:
I agree with others who suggested in essence that anyone serious
enough to be using Subversion will have the BBEdit's command tools
installed.
I use Subversion seriously, but don't use BBEdit as m
> You've taken AlanR's comment out of context. The discussion is about
> people who are using BBEdit for diff and how Versions should access
> it. AlanR is saying that people who are using BBEdit and subversion
> are likely to have also installed the included BBEdit command line
> tools (a
19 matches
Mail list logo
