Gentoo Archives: gentoo-user

From: gentuxx <gentuxx@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Developmnet Environment for PHP and PERL
Date: Wed, 09 Nov 2005 02:20:18
Message-Id: 43715A8E.1040308@gmail.com
In Reply to: [gentoo-user] Developmnet Environment for PHP and PERL by Michael Shaw
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Michael Shaw wrote:
5
6 > What editor do people use for PHP and Perl development. I'm looking
7 > for something with syntax highlighting and such, so that rules ut vi
8 > or gedit.
9 >
10 > Thanks,
11 > Mike
12
13 I seems like you've got a lot of good suggestions here, so I'll just
14 throw my 2¢ out into the pot too!
15
16 For perl, I use vim for quick edits and kate for larger projects. It
17 doesn't auto-tab the way I think it should, but that's probably just a
18 configuration that I haven't given it yet. ;-)
19
20 I like bluefish for HTML|PHP|CSS, but the CSS and PHP colorization is
21 a little jumpy. Sometimes it'll do it, sometime it won't. So then I
22 started using gphpedit for JUST PHP. bluefish is nice for (X)?HTML,
23 and OK for CSS, but more often than not, I find myself comfy with PHP
24 and CSS in gphpedit.
25
26 I might have to look into eclipse though.....that sounds interesting.
27 And I worked with emacs while I was working on some documentation for
28 the Fedora Documentation Project, I could probably handle that if the
29 plug-ins worked right.
30
31 Anyway, my top pick for perl is kate, for PHP is gPHPEdit.
32
33 Cheers!
34
35 - --
36 gentux
37 echo "hfouvyAdpy/ofu" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
38
39 gentux's gpg fingerprint ==> 34CE 2E97 40C7 EF6E EC40 9795 2D81 924A
40 6996 0993
41 -----BEGIN PGP SIGNATURE-----
42 Version: GnuPG v1.4.1 (GNU/Linux)
43
44 iD8DBQFDcVqOLYGSSmmWCZMRAk8tAJ4zn4IRuwmgx/rOIAwi701dti+aJQCfS3jt
45 8czaaR9XrRvTJW2p2WNBTwY=
46 =9/bd
47 -----END PGP SIGNATURE-----
48
49 --
50 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] Developmnet Environment for PHP and PERL Michael Shaw <mshaw@×××××.com>