Re: OT: CVS clients and BBEdit diff tool ...
At 5:57 PM +1100 12/3/02, Ken Williams wrote: On Tuesday, December 3, 2002, at 05:07 PM, Rob Barris wrote: Could someone use Inline.pm to talk to the Carbon API and the desktop database? Then you could look up any app by its creator code (I would wager). Have a look at Mac::MoreFiles (part of Mac::Carbon), which does exactly this. -Ken Or use an alternate form of the open command in Applescript and let the Finder look the app up by it's creator code for you. Or use the `open` command directly, instead of through AppleScript. Or TIMTOWTDI. -Jeff Lowrey
Re: OT: CVS clients and BBEdit diff tool ...
Bruce A. Burdick, Jr. [EMAIL PROTECTED] wrote on 12/1/02 at 11:28p: I had to change 'BBEdit' to 'BBEdit 6.5' to allow this to work in my environment. [...] Naturally, this patch'll probably break other systems. A general solution might try one and then the other. You could also just change the name of your BBEdit application from BBEdit 6.5 to BBEdit. There's nothing magic about the app's file name, so this shouldn't break anything. It won't break *compiled* applescripts, since they store a reference to application, not the name of the app. As a general solution for not-yet-compiled applescripts, such as those embedded in Perl scripts, I'm not sure what to suggest, other than not including version info in application file names. :^) -- John Gruber | Daring Fireball: Mac Punditry and Curmudgeonry [EMAIL PROTECTED] |http://daringfireball.net
Re: OT: CVS clients and BBEdit diff tool ...
On Monday, December 2, 2002, at 10:01 PM, John Gruber wrote: Bruce A. Burdick, Jr. [EMAIL PROTECTED] wrote on 12/1/02 at 11:28p: I had to change 'BBEdit' to 'BBEdit 6.5' to allow this to work in my environment. [...] Naturally, this patch'll probably break other systems. A general solution might try one and then the other. You could also just change the name of your BBEdit application from BBEdit 6.5 to BBEdit. There's nothing magic about the app's file name, so this shouldn't break anything. It won't break *compiled* applescripts, since they store a reference to application, not the name of the app. As a general solution for not-yet-compiled applescripts, such as those embedded in Perl scripts, I'm not sure what to suggest, other than not including version info in application file names. :^) Could someone use Inline.pm to talk to the Carbon API and the desktop database? Then you could look up any app by its creator code (I would wager). Rob
Re: OT: CVS clients and BBEdit diff tool ...
On Tuesday, December 3, 2002, at 05:07 PM, Rob Barris wrote: Could someone use Inline.pm to talk to the Carbon API and the desktop database? Then you could look up any app by its creator code (I would wager). Have a look at Mac::MoreFiles (part of Mac::Carbon), which does exactly this. -Ken
Re: OT: CVS clients and BBEdit diff tool ...
On Thursday, November 28, 2002, at 01:23 AM, Pete Prodoehl wrote: This may (or may not) work for you, I wrote a script to do a diff with two files via the command line, and if they really are different, it opens them both in BBEdit. It's here: http://zymm.com/raster/code/src/diffem_pl.txt I've really been smitten with the FileMerge application (at /Developer/Applications/FileMerge), but unfortunately it doesn't seem to be scriptable so this kind of wrapper would be tougher to write. -Ken
Re: OT: CVS clients and BBEdit diff tool ...
On Wednesday, November 27, 2002, at 03:39 pm, Peder Axensten wrote: I want to get started with CVS and BBEdit, how to I run a server? There's nothing in the BBEdit manual... Any good sources of info would be appreciated! If you're doing local development you might find http://developer.apple.com/internet/macosx/cvsoverview.html Of use. Adrian
Re: OT: CVS clients and BBEdit diff tool ...
This may (or may not) work for you, I wrote a script to do a diff with two files via the command line, and if they really are different, it opens them both in BBEdit. It's here: http://zymm.com/raster/code/src/diffem_pl.txt Pete Ray Zimmerman wrote: for Perl development on OS X, of course :-) [snip] BBEdit diff: I want a bbdiff command-line program. Something that will let me type: bbdiff file1 file2 or bbdiff dir1 dir2 to initiate a file comparison or multi-file comparison in BBEdit. Ideally, Bare Bones would include something like this along side the bbedit command-line tool, but I was wondering if anyone has created (or could easily create) such a tool via a Perl script making some AppleScript calls or something?
Re: OT: CVS clients and BBEdit diff tool ...
I want to get started with CVS and BBEdit, how to I run a server? There's nothing in the BBEdit manual... Any good sources of info would be appreciated! /Peder
Re: OT: CVS clients and BBEdit diff tool ...
On Wednesday, November 27, 2002, at 10:39 AM, Peder Axensten wrote: I want to get started with CVS and BBEdit, how to I run a server? There's nothing in the BBEdit manual... Any good sources of info would be appreciated! Setting up a server is beyond the scope of the BBEdit manual I'm afraid. We put up some FAQs yesterday. http://www.barebones.com/cgi-bin/faq/ faqgroup.pl?BBEdit_Features#Features_-_1 To set up a server that you can do CVS over ssh with is relatively easy. First, turn on the sshd daemon on the machine. Setup a CVS repository. (cvs init - see cvs manual - FWIW the little O'Reilly pocket reference for about $10 is quite helpful.). Import a project, then check out into a sandbox and you are off to the races. (This all assumes a propert CVS_RSH = ssh and CVSROOT = :ext:user@host:/path/to/repository) Setting up a pserver is a bit more involved because you've got to get xinetd or inetd listening properly, but if you can use ssh you probably don't want to use pserver since everything is cleartext. Jim -- Jim Correia [EMAIL PROTECTED]
Re: OT: CVS clients and BBEdit diff tool ...
At 9:08 AM -0500 11/27/02, Jim Correia wrote (regarding my comments on MacCVS Pro): I think the problem is more than line feeds. The repository file gets written out as (this may be wrong since it is from memory) server:blahblahblah for an ssh type repository when the command line cvs expects :ext:blahblahblah. Ah ... I was using pserver, which seemed to work OK as soon as I changed the CRs to LFs. -- Ray Zimmerman / e-mail: [EMAIL PROTECTED] / 428-B Phillips Hall Sr Research / phone: (607) 255-9645 / Cornell University Associate / FAX: (815) 377-3932 / Ithaca, NY 14853
Re: OT: CVS clients and BBEdit diff tool ...
At 9:08 AM -0500 11/27/02, Jim Correia wrote: On Wednesday, November 27, 2002, at 08:42 AM, Ray Zimmerman wrote: BBEdit diff: I want a bbdiff command-line program. Something that will let me type: bbdiff file1 file2 or bbdiff dir1 dir2 to initiate a file comparison or multi-file comparison in BBEdit. Ideally, Bare Bones would include something like this along side the bbedit command-line tool, but I was wondering if anyone has created (or could easily create) such a tool via a Perl script making some AppleScript calls or something? I'm sure somebody has at some point. I just wrote one here. It isn't a full fledged tool in that it doesn't give you usage and doesn't have an error checking for arguments and such, but if you always supply both arguments and they are valid, it should do the job. snip Share and enjoy. Sweet ... thanks. Isn't OS X great! -- Ray Zimmerman / e-mail: [EMAIL PROTECTED] / 428-B Phillips Hall Sr Research / phone: (607) 255-9645 / Cornell University Associate / FAX: (815) 377-3932 / Ithaca, NY 14853
Re: OT: CVS clients and BBEdit diff tool ...
BBEdit diff:
I want a bbdiff command-line program. Something that will let me type:
bbdiff file1 file2
or
bbdiff dir1 dir2
to initiate a file comparison or multi-file comparison in BBEdit.
Ideally, Bare Bones would include something like this along side the
bbedit command-line tool, but I was wondering if anyone has created
(or could easily create) such a tool via a Perl script making some
AppleScript calls or something?
bbedit-compare.pl:
#!/usr/bin/perl
use warnings;
use strict;
use File::Spec::Unix;
my $file1 = shift or Usage();
my $file2 = shift or Usage();
compare_in_bbedit( $file1, $file2 );
sub Usage {
print STDERR Usage: bbedit-compare.pl file1 file2\n;
exit( 1 );
}
sub compare_in_bbedit {
my( $file1, $file2 ) = @_;
$file1 = File::Spec::Unix-rel2abs( $file1 );
$file2 = File::Spec::Unix-rel2abs( $file2 );
do_osa_script( EOM );
tell app BBEdit
compare POSIX file $file1 against POSIX file $file2
activate
end tell
EOM
}
sub do_osa_script {
my( $script ) = @_;
my $fh;
open( $fh, | /usr/bin/osascript /dev/null ) or die cant open
osascript $!;
print $fh $script;
close( $fh );
}
Enjoy,
Peter.
--
http://www.interarchy.com/ http://download.interarchy.com/
