From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: additional functionality for html-helper-mode
Date: Wed, 24 May 2017 21:27:30 +0200 [thread overview]
Message-ID: <87k256jbrx.fsf@debian.uxu> (raw)
In-Reply-To: 471dcac4-db8a-8789-3056-f08348c4816d@mousecar.com
ken <gebser@mousecar.com> writes:
>>> Would it be possible to integrate that
>>> functionality into html-helper-mode so that
>>> chapters could be selectively collapsed or
>>> expanded? For example, I might have: I use the
>>> built-in `html-mode' for my primitive or
>>> 90s-looking pages and as for editing I never had
>>> any problems or felt the need to do code fold, but
>>> some people who do HTML insist web-mode.el is much
>>> better and there code folding is available
>>> probably exactly as you describe it:
>>> http://web-mode.org
>>
> Thanks for the suggestion, but I didn't want to have to
> learn a new editor.
A new editor? Sweet heaven, no! Here is what it says
on the web site:
web-mode.el is an autonomous emacs major-mode for
editing web templates. HTML documents can embed
parts (CSS/JavaScript) and blocks (client/server
side).
Does "autonomous" mean it is implemented as
a standalone editor? What kind of "Emacs mode" is
that?!
> Though it's off-topic, I would add that I use
> html-helper-mode to edit quite sophisticated web
> pages which aren't '90s-looking at all, but which
> incorporate web 2.0 features and CSS
Well, you are allowed to use CSS...
> and columns, graphics, and much more. Of course
> I wouldn't write an entire CMS with
> html-helper-mode, but then I wouldn't attempt it in
> any emacs mode; it would be much more sensible to
> use Joomla, Wordpress or Drupal...
...but not that :)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-05-24 19:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 22:34 additional functionality for html-helper-mode ken
2017-05-22 22:53 ` Jean-Christophe Helary
2017-05-23 17:43 ` ken
2017-05-23 22:13 ` Jean-Christophe Helary
2017-05-24 4:46 ` Yuri Khan
2017-05-24 18:27 ` ken
2017-05-25 22:47 ` John Ankarström
2017-05-24 18:25 ` ken
2017-05-23 0:29 ` Emanuel Berg
2017-05-23 18:49 ` ken
2017-05-24 19:27 ` Emanuel Berg [this message]
2017-05-25 21:58 ` ken
2017-05-26 6:26 ` Yuri Khan
2017-05-26 12:39 ` Emanuel Berg
2017-05-26 13:34 ` Yuri Khan
2017-05-26 21:05 ` Emanuel Berg
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=87k256jbrx.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).