unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Xah <xahlee@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs vs. TextMate (not trying to start an editor war)
Date: Thu, 10 Jul 2008 10:45:24 +0200	[thread overview]
Message-ID: <4875CC24.4070704@gmail.com> (raw)
In-Reply-To: <8f5e7835-91fb-4f34-a913-f08f9762301b@l42g2000hsc.googlegroups.com>

Xah wrote:
> (of course emacs fans will tell you about several elisp code on the
> web there that does multi modes... but the sheer fact to shop around,
> install, get them to work is a pain and rather not trivial.
> for those interested, see http://www.emacswiki.org/cgi-bin/wiki/MultipleModes
> )

Xah, did you ever try nXhtml? In that case what where you missing? Did 
you have to "shop around"?

> I think to have emacs work with today's web dev needs out of the box
> is one of the most important need for emacs.
> (see http://xahlee.org/emacs/modernization_of_elisp.html )
> 
> Even for working with pure static html pages, emacs's default html
> mode is quite lacking.
> The default html mode in emacs 22 (released in 2007), is at a level of
> ~1998's commercial html editors. (of course emacs has redeeming
> qualities, i.e. its elisp system and all, that keeps us still sticking
> with emacs)
> 
> Web development is my primary area of expertise. I have to work with
> html mixed with css, javascript, php, perl a lot. Fortunately, lacking
> proper syntax coloring isn't much problem. (after all, 99.99% web
> pages out there are so badly formed)







  reply	other threads:[~2008-07-10  8:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.14482.1215674117.18990.help-gnu-emacs@gnu.org>
2008-07-10  8:29 ` Emacs vs. TextMate (not trying to start an editor war) Xah
2008-07-10  8:45   ` Lennart Borgman (gmail) [this message]
2008-07-10  8:58   ` Xah
2008-07-10 17:22     ` Cezar Halmagean
2008-07-10 19:52       ` Joel J. Adamson
     [not found] <m263re6zi8.fsf@cezar@mixandgo.com>
2008-07-10  7:43 ` Bastien
2008-07-10  8:09 ` Lennart Borgman (gmail)
2008-07-10 16:29   ` Cezar Halmagean
2008-07-10 16:36     ` Lennart Borgman (gmail)
2008-07-10 16:41       ` Cezar Halmagean
2008-07-12  4:14         ` William Xu
2008-07-10 16:56       ` Cezar Halmagean
2008-07-10 22:07         ` Lennart Borgman (gmail)
2008-07-24 23:08         ` Cezar Halmagean
2008-07-10 19:47 ` Joel J. Adamson
2008-07-10 19:57   ` Cezar Halmagean
2008-07-10 20:05     ` Joel J. Adamson
2008-07-10 20:17       ` Cezar Halmagean
     [not found]       ` <mailman.14507.1215721063.18990.help-gnu-emacs@gnu.org>
2008-07-10 23:55         ` Miles Bader
2008-07-11  2:21           ` Cezar Halmagean
     [not found]           ` <mailman.14529.1215743109.18990.help-gnu-emacs@gnu.org>
2008-07-11  4:44             ` Miles Bader
2008-07-11 15:31               ` Tom Tromey
2008-07-11 23:11                 ` Lennart Borgman (gmail)
     [not found]   ` <mailman.14504.1215719886.18990.help-gnu-emacs@gnu.org>
2008-07-11  4:46     ` Tim X
2008-07-11  6:39       ` Cezar Halmagean
2008-07-11  9:26       ` William Xu
2008-07-11 14:42         ` Charles philip Chan
     [not found]       ` <mailman.14533.1215758403.18990.help-gnu-emacs@gnu.org>
2008-07-12  4:22         ` Tim X
2008-07-10  6:10 Cezar Halmagean
2008-07-10  8:11 ` Charles philip Chan

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4875CC24.4070704@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=xahlee@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).