Search results

I believe that ~/bin is already part of the shell path. If you put rar in a folder called bin in your home directory then it will be found by the shell. (You may have to run the "rehash" command if the terminal is already open, although I don't think this command exists in bash.) I don't...

Oh, I dunno. PB isn't all that bad. I use it daily for writing cross-platfrom C++ code and have had no significant issues. But let me see if I understand your question correctly. Are you saying that ProjectBuilder is destroying your source files? Or are you saying that PB is using too much...

Well, a perl program is just a text file containing perl source code. At the top of a perl script is a line like this: #!/usr/bin/perl The file must be made executable... chmod ug+x myscript.pl ...and must be owned by the user or group that wishes to run the script. chown...

Woof. Sounds pretty bad. I've had one or two icons do odd things, but never the whole bunch. Does your machine have at least 256MB of RAM? Have you tried using Disk Utility to Repair Permissions? Would you consider doing an Archive And Install to put a fresh copy of Jaguar on your machine?

An article on MacCentral today indicated that Panther's version of TextEdit is going to be able to open .doc files. And some have suggested that Apple is working on an internal project that will supercede Office v.X. It's only a rumor at this point, so don't start stacking your pennies.

Not yet, but Steve Jobs suggested that others should get on the bandwagon and make it happen. Perhaps an open source project will arise on SourceForge one of these days.

Quite so. For some reason only known to its creators bash uses completely different shell scripting conventions than [t[c]sh]].

Aha. There's also KisMac (a "wireless sniffer") and a front-end for tcpdump called MacSniffer.

Excellent. I for one look forward to a definitive answer!

Sorry about the PC guys. Annoying little freaks, aren't they? PCs are not the answer. More often they are the problem. I mean, obviously PCs haven't done anything to educate their users about Unix, which leaves them with a narrow and skewed view of how OS's are supposed to work. But enough...

Good work, JB. I had no idea it was in Fink's unstable tree. I think I'll do as you suggest and get that unstable tree after all!

Another option is the freeware utility named ShellSilver which simply makes scripts with the .sh extension run in the Terminal. The best option by far is the program DropScript which converts any shell script or perl script into an application. You won't get to see any output, but if your...

I'm trying now to build it from source, and it's got a set of dependencies that aren't included by default on Mac OS X. So I'm doing a bit of downloading with Fink to satisfy the missing pieces. We'll see how it goes. The first broken dependency was "ltdl.h" from libtool. It's actually on my...

Well, I suppose you can use the diff command creatively: ls -1 /first/path >/tmp/d1 ls -1 /second/path >/tmp/d2 diff /tmp/d1 /tmp/d2 To embed into a shell script just change /first/path to "$1" and /second/path to "$2" and the script will do the substitutions for you.

Is the RAM in your system supplied by Apple or did you buy it elsewhere? Mac OS X is very stingy about the quality of the RAM.

Did you also install Apple's X11-developer package? It's available from the same page as X11 itself.

One thing you should definitely do is disable file indexing and delete the existing indexes. 1. Open the Finder's Preferences. 2. Click the "Select..." button at the bottom. 3. Uncheck all the languages. Another thing to do is run the program "Monolingual," which removes all extra...

Quite so, Zammy. Uninstall is an option that installers can provide, but most simply don't. However, most installers are .pkg files, and you can explore these with the utility Pacifist. I'm not sure, but Pacifist may be able to uninstall files indicated by a given package.

You might have better luck with CURL also. That's how I've always invoked PHP scripts.

That's a good question. Generally speaking, if you edit a file that has odd characters you'll see a set of two characters glommed together to represent it. Chances are the character encoding is Unicode, so that's a good place to start....