From: ken <gebser@mousecar.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: additional functionality for html-helper-mode
Date: Wed, 24 May 2017 14:27:59 -0400 [thread overview]
Message-ID: <ab1cb802-e922-394b-c643-27fec2566bde@mousecar.com> (raw)
In-Reply-To: <CAP_d_8WxnwxQ5rmz_v-N5ta8e9sPTjp+SbM8OyBRA=YCdvto_Q@mail.gmail.com>
On 05/24/2017 12:46 AM, Yuri Khan wrote:
> On Wed, May 24, 2017 at 5:13 AM, Jean-Christophe Helary
> <jean.christophe.helary@gmail.com> wrote:
>
>>> However, it doesn't seem to understand html, i.e., only affects CSS definitions enclosed within curly braces, { and }.
>> Ok, a quick search with "html, folding, emacs) brought these:
> Keep in mind that with regard to HTML there are two possible
> interpretations of folding.
>
> * One is folding the contents between two paired tags: <p>{{…}}</p>.
> * Another is folding the contents after a heading up to (but not
> including) the next heading of that or higher level on the same level
> of element nesting: <h2>Foo</h2>{{…}}<h1>Bar</h1>.
>
> The first is what a typical general-purpose folding library is going
> to implement. The second can arguably be called “understanding HTML”,
> and is what Ken is asking for.
>
> (And no, I don’t have any experience with HTML folding in Emacs.)
>
Good distinction. Completely correct. And hideshow couldn't do either.
next prev parent reply other threads:[~2017-05-24 18: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 [this message]
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
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=ab1cb802-e922-394b-c643-27fec2566bde@mousecar.com \
--to=gebser@mousecar.com \
--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).