From: "Hrvoje Nikšić" <hniksic@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [NonGNU ELPA] Htmlize version 1.57
Date: Thu, 26 Aug 2021 11:44:00 +0200 [thread overview]
Message-ID: <CAK291fqesq5ebF4jpyOpy=-GnMZ8sHkg9-S6qfHhamPjc9g2qg@mail.gmail.com> (raw)
In-Reply-To: <85pmu0zi7d.fsf@elpa.gnu.org>
Hi,
Is there a way to have ELPA track the "stable" branch rather than
"master"? The email is just wrong, as htmlize 1.57 has *not* been
released - I've just pushed the version bump to the branch that holds
development ("master").
Hrvoje
On Thu, Aug 26, 2021 at 11:08 AM ELPA update <do.not.reply@elpa.gnu.org> wrote:
>
> Version 1.57 of package Htmlize has just been released in NonGNU ELPA.
> You can now find it in M-x package-list RET.
>
> Htmlize describes itself as:
> Convert buffer text and decorations to HTML.
>
> More at https://elpa.nongnu.org/nongnu/htmlize.html
>
> Recent NEWS:
>
> htmlize NEWS -- history of user-visible changes.
>
> * Changes in htmlize 1.51
>
> ** `htmlize-face-overrides' can be used to override Emacs's face
> definitions.
>
>
> * Changes in htmlize 1.47
>
> ** GNU Emacs 21 is no longer supported.
>
>
> * Changes in htmlize 1.45
>
> ** Correctly handle :inherit specifying a list of faces. (This bug
> would cause an error in AUX TeX buffers.)
>
>
> * Changes in htmlize 1.44
>
> ** Faces specified in the `face' property are now prioritized the same
> way that Emacs redisplay does it: faces that appear earlier have
> precedence over those that appear later.
>
>
> * Changes in htmlize 1.41
>
> ** `before-string' and `after-string' overlay properties are now
> recognized by htmlize and inserted into the HTML.
>
> ** Images specified by `display' property are recognized and inserted
> into the HTML as <img src=...>.
>
> *** If the image data comes from a file, the image will be rendered as
> a relative URI that would resolve to that file. Images whose data
> comes from a string will be rendered inline as data: URIs. The flag
> `htmlize-force-inline-images' can be used to force inserting *all*
> images inline as data: URIs.
>
> ** The image's ALT text will be the text that the `display' property is
> replacing, if non-empty.
>
> ** Arbitrary links can now be added to the generated HTML. If htmlize
> encounters buffer text with `htmlize-link' property, it will wrap the
> text in <a href="uri">...</a>. If the property value is a string, it
> is interpreted as the URI. If it is a list, it should be a property
> list whose currently only defined key is :uri.
next parent reply other threads:[~2021-08-26 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85pmu0zi7d.fsf@elpa.gnu.org>
2021-08-26 9:44 ` Hrvoje Nikšić [this message]
2021-08-26 15:03 ` [NonGNU ELPA] Htmlize version 1.57 Stefan Monnier via Users list for the GNU Emacs text editor
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='CAK291fqesq5ebF4jpyOpy=-GnMZ8sHkg9-S6qfHhamPjc9g2qg@mail.gmail.com' \
--to=hniksic@gmail.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).