re: revised html-mode.el

paolo petta <paolo@venedig.ai.univie.ac.at>
Errors-To: listmaster@www0.cern.ch
Date: Wed, 20 Apr 1994 12:17:48 --100
Message-id: <199404201012.AA02483@moskau.ai.univie.ac.at>
Errors-To: listmaster@www0.cern.ch
Reply-To: paolo@venedig.ai.univie.ac.at
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: paolo petta <paolo@venedig.ai.univie.ac.at>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: re: revised html-mode.el
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: ELM [version 2.3 PL11]
X-Mailer: ELM [version 2.3 PL11]
Content-Length: 1544
[original message by Daniel W. Connolly ]
> p.s. I've resumed hacking on html-mode... I started with a little
> ditty that attempts to put in all these missing <P> tags to bring
> a doc up to date... it also sticks "<!DOCTYPE ..." at the top.
> 
> I also changed the "html-add-code" etc. to work on the region, like a
> good little word processor should: you select some text with the mouse
> and choose Emphasize from the menu, and it wraps the selection with
> <em>...</em>. How many times to you go "hmmm.. I think I'm going to
> write some emphasized text..." versus "ah... that span of text should
> be marked as CODE." Headers are the same way... type in the header,
> select it, then make it a header.
> 
> This way is _much_ easer for hand-converting text documents into HTML.
> Anybody interested?
> 

Would it be feasible to have a "merger" of this hacked html-mode and
the hm--html-menus package (available at e.g. info.cern.ch (pub/www/contrib),
sunsite.unc.edu (/pub/Linux/apps/editors/emacs/) and
ftp.rrzn.uni-hannover.de (in /pub/unix/editors/lemacs/contrib)?

e.g. hm--html-menus has supported the "work on selection" for a long time...
Perhaps if Heiko Muenkel (the author) were willing to accept/coordinate
patches, extensions, etc. much effort could be saved... 

paolo

ps.: While this message is motivated because I hate always having to
     choose between n packages for the same job, each of which
     supporting some handy/nice feature the others don't, I readily
     admit that this issue has (very?) low priority..