From: Michael Shaw <mshaw@dowco.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Developmnet Environment for PHP and PERL
Date: Tue, 08 Nov 2005 22:19:57 -0800 [thread overview]
Message-ID: <4371950D.1090109@dowco.com> (raw)
In-Reply-To: <1131516510.10228.0.camel@spok.local.sporn-it.com>
Heinz Sporn wrote:
>Am Dienstag, den 08.11.2005, 19:07 -0500 schrieb Thomas Tuttle:
>
>
>>On November 08 at 13:33 EST, Michael Shaw hastily scribbled:
>>
>>
>>>What editor do people use for PHP and Perl development. I'm looking for
>>>something with syntax highlighting and such, so that rules ut vi or gedit.
>>>
>>>
>>I can offer three suggestions:
>>
>>1. vim. If you set it up right (just a few lines in ~/.vimrc), it will
>>do syntax highlighting properly.
>>
>>2. jedit. It's java-based, but relatively light, supports many file
>>types (although it is a tad Java-centric), and has good plugins.
>>
>>
>
>Want to second jEdit for it's platform independency and many nice
>plugins.
>
>
>
>>3. bluefish. It's not language-centric, but I *think* it has PHP
>>support (I might be wrong), and it's a good "web development" editor.
>>
>>Hope this helps.
>>
>>
>>
Alright, I'll give jEdit a try to. Thanks to everyone for all their
suggestions.
Mike
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-09 6:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 18:33 [gentoo-user] Developmnet Environment for PHP and PERL Michael Shaw
2005-11-08 18:42 ` John Jolet
2005-11-08 19:55 ` Catalin Trifu
2005-11-08 20:01 ` Billy Holmes
2005-11-08 21:42 ` A. Khattri
2005-11-08 22:25 ` Michael Shaw
2005-11-08 23:24 ` Renat Golubchyk
2005-11-09 3:19 ` Michael Shaw
2005-11-10 17:46 ` A. Khattri
2005-11-08 22:00 ` b.n.
2005-11-08 22:06 ` Stuart Herbert
2005-11-08 22:29 ` Michael Shaw
2005-11-09 0:07 ` Thomas Tuttle
2005-11-09 6:08 ` Heinz Sporn
2005-11-09 6:19 ` Michael Shaw [this message]
2005-11-09 2:10 ` gentuxx
2005-11-09 3:21 ` Michael Shaw
2005-11-09 10:21 ` Stoian Ivanov
2005-11-09 15:13 ` Michael Crute
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4371950D.1090109@dowco.com \
--to=mshaw@dowco.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox