all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: Bruno Barbier <brubar.cs@gmail.com>,
	emacs-orgmode@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Strange warnings from htmlize.el
Date: Thu, 01 Aug 2024 15:16:42 +0000	[thread overview]
Message-ID: <87jzh0b7dx.fsf@localhost> (raw)
In-Reply-To: <e03dd01f-8db9-421d-bedf-8f098259ff83@libero.it>

Angelo Graziosi <angelo.g0@libero.it> writes:

>> This warning is from Org. It's telling you that you need to install the
>> htmlize package in your new Emacs.
>
> If ORG is in Emacs core and it needs this package, shouldn't the package 
> be in core too?

That's out of our control.
htmlize is not strictly required.  But without htmlize, code in the code
blocks is not colored.

Note that what is now a warning used to be a message.  Now, it is more
visible, which was the reason why this was promoted to warning.

> In any case I have "fixed" this removing the language from #+BEGIN_SRC. 
> For example:
>
> -#+BEGIN_SRC sh
> +#+BEGIN_SRC
>
> which for me is enough.

You can also:
1. Suppress the warning
2. Set `org-html-htmlize-output-type' to nil to tell Org not to try coloring

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2024-08-01 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 21:55 Strange warnings from htmlize.el Angelo Graziosi
2024-08-01 11:26 ` Bruno Barbier
2024-08-01 15:04   ` Angelo Graziosi
2024-08-01 15:16     ` Ihor Radchenko [this message]
2024-08-04 18:44       ` Ihor Radchenko

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

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

  git send-email \
    --in-reply-to=87jzh0b7dx.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=angelo.g0@libero.it \
    --cc=brubar.cs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.