Portable Thunderbird is the popular Mozilla Thunderbird email program packaged as a cross-platform portable app, so you can take your email, drafts, cache, newsgroups, and saved passwords with you. It works on both Macs and PCs.
How It Works
Cross-platform Portable Thunderbird works by using John Haller’s excellent Portable Thunderbird 1.5 on the Windows side of things, and a little script he made on the Mac side of things. The script basically changes your user profile every time you start Thunderbird so that it works on Mac and PC. The reason why is simple: as I am sure some of you have figured out, Windows Thunderbird profiles are not completely compatible with Mac Thunderbird, only certian files. So he made a script that keeps compatibility between Mac and PC, time consuming, I know, but it works.
Check it out at: http://www.theplaceforitall.com/portablethunderbird/
Also, check out: http://portableapps.com/
“PHP security holes have a name — quite often it was Stefan Esser who found and reported them. Now Esser has quit the PHP security team. He feels that his attempt to make PHP safer “from the inside” is futile. Basic security issues are not addressed sufficiently by the developers. Zeev Suraski, Zend’s CTO of course disagrees and urges Stefan to work with the PHP development team instead of working against it. But given the number of remote code execution holes in PHP apps this year, Esser might have a point. And he plans to continue his quest for security holes in PHP. Only that from now on, he will publish them after reasonable time — regardless if a patch is available or not.”
Zeev Suraski wrote in to protest: “I’m quoted as if I ‘point fingers at inexperienced developers,’ and of course, there’s no link to that — because it’s not true! The two issues — security problems in Web apps written in PHP, and security problems in PHP itself — are two distinct issues. Nobody, including myself, is saying that there are no security problems in PHP — not unlike pretty much any other piece of software. Nobody, I think, argues the fact that there have been many more security problems at the application level, then there were at the language level. I never replied to Stefan’s accusations of security problems in PHP saying ‘that’s bull, it’s all the developers’ fault,’ and I have no intention to do it in the future.”
I always use vim when editing PHP files… but, I don’t have a good .vimrc.
About the only thing I have is the completion dictionary; provided by Rasmus:
or (as Wez stated), wget ‘http://viewcvs.php.net/viewcvs.cgi/*checkout*/phpdoc/funclist.txt’ -O php-funclist.txt
cat php-funclist.txt.new php-lang-constructs.txt | egrep -v ‘^#’ | sort | uniq > php-funclist.txt
that php-lang-constructs.txt has this in it:
# language constructs for completion, not found in the regular funclist
As, well as the PEAR coding standards:
Also, I show the line numbers by default:
I was thinking about adding SVN Commit and maybe PHP parser check with ‘!php -l %’
So, I guess what I am asking is if you use vim could you share your .vimrc