macfidelity

Nachdem ich neulich hier schon ein Programm vorgestellt habt mit dem man unter Windows sehr einfach Text-Dateien vergleichen kann, fehlt natürlich noch eine Lösung für Mac OS X

Wie so oft gibt es unterschiedliche Wege wie man unter Mac OS X Dateien vergleichen kann, ich will das ganze wie folgt untergliedern:

• Betriebssystemeigene Lösungen
• Fremd-Anbieter Software

Read the rest of this entry »

I have mentioned CPUPalette some days ago. Today i have found another nice hint on macosxhints regarding the installation of a Processor System Pref.Panel

Quote from the hint:

Hidden in the Developer Tools package, there is a System Preferences panel that serves the same purpose as this hint about the CPU Palette.

After installing Xcode, navigate to /Developer  » Extras  » PreferencePanes, and then double-click on Processor.prefPane to install it. The Processor panel will add itself in the Hardware (not Other) section within System Preferences.

Using this panel, you can do everything you can do with the CPU Palette, minus the graphs but plus some L2 Cache and frontside bus info. The best part, however, is the fact that you can use the panel to add a menu bar item that replaces CPU Palette. From the menu bar icon, you’ll have access to the preference pane, the option to use two or one cores, and the CPU Palette itself.

Edit: i think that works in Tiger / 10.4 too.

About ack:

ack is a tool like grep, aimed at programmers with large trees of heterogeneous source code.

ack is written purely in Perl, and takes advantage of the power of Perl’s regular expressions.

Found that via DaringFireball.net

Quote from the project page:

Top 10 reasons to use ack instead of grep.

1. ack is pure Perl, so it runs on Windows just fine.
2. The standalone version uses no non-standard modules, so you can put it in your ~/bin without fear.
3. Searches recursively through directories by default, while ignoring .svn, CVS and other VCS directories.
   • Which would you rather type?
     $ grep pattern $(find . | grep -v .svn)
     $ ack pattern
4. ack ignores most of the crap you don’t want to search
   • VCS directories
   • blib, the Perl build directory
   • backup files like foo~ and #foo#
   • binary files, core dumps, etc
5. Ignoring .svn directories means that ack is faster than grep for searching through trees.
6. Lets you specify file types to search, as in –perl or –nohtml.
   • Which would you rather type?
     $ grep pattern $(find . -name ‘*.pl’ -or -name ‘*.pm’ -or -name ‘*.pod’ | grep -v .svn)
     $ ack –perl pattern

   Note that ack’s –perl also checks the shebang lines of files without suffixes, which the find command will not.

7. File-filtering capabilities usable without searching with ack -f. This lets you create lists of files of a given type.
   $ ack -f –perl > all-perl-files
8. Color highlighting of search results.
9. Uses real Perl regular expressions, not a GNU subset.
10. Allows you to specify output using Perl’s special variables
    • Example: ack ‘(Mr|Mr?s)\. (Smith|Jones)’ –output=’$&’
11. Many command-line switches are the same as in GNU grep:
    -w does word-only searching
    -c shows counts per file of matches
    -l gives the filename instead of matching lines
    etc.
12. Command name is 25% fewer characters to type! Save days of free-time! Heck, it’s 50% shorter compared to grep -r.

If you have XCode Tools / Developer Tools installed on a Mac with more then 1-Core take some minutes and check CPUPalette.app in

/Library/Application Support/HWPrefs/CPUPalette.app

Source: macosxhints.com

It will provide you with CPU usage information, as well as let you disable one or more cores.