From: Ihor Radchenko <yantar92@posteo.net>
To: Cooper Oscarfono <bleat@baaa.sh>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-publish producing <nil> element tags instead of honoring what is specified in :html-divs
Date: Thu, 30 Mar 2023 09:57:22 +0000 [thread overview]
Message-ID: <87h6u2ef3x.fsf@localhost> (raw)
In-Reply-To: <08517f41-7998-68cb-d544-60cc36392567@baaa.sh>
Cooper Oscarfono <bleat@baaa.sh> writes:
> In attempting to convert the divs generated for preamble, content, and
> postamble, by specifying, what I believe to be the appropriate setting
> within org-publish-project-alist :
>
>
> :html-divs '((preamble "header" :id "preamble")
> (content "main" :id "content")
> (postamble "footer" :id "postamble"))
>
>
> Instead of generating <header id="preamble"...</header>, <main
> id="content">...</main>, and <footer id="postamble">...</footer>, as
> expected, I am generating: <nil id="nil" class="status">...</nil>, <nil
> id="nil" class="content">...</nil>, and <nil id="nil"
> class="status">...</nil>, respectively.
Looks like double quoting.
You likely have something like
(setq org-publish-project-alist '(... :html-divs '(...)) ...).
Because of nested "'", the actual value of :html-divs is set to
(quote (...)) and Org is not able to get preamble/contents/postamble
part from there.
To illustrate try the following
(setq test '(:a '((preamble "a" "b"))))
(assq 'preamble (plist-get test :a))
and then the same but without double quoting
(setq test '(:a ((preamble "a" "b"))))
(assq 'preamble (plist-get test :a))
--
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>
prev parent reply other threads:[~2023-03-30 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 5:27 org-publish producing <nil> element tags instead of honoring what is specified in :html-divs Cooper Oscarfono
2023-03-30 9:57 ` Ihor Radchenko [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6u2ef3x.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bleat@baaa.sh \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).