emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Ihor Radchenko <yantar92@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Bug: html-postamble string does not allow space [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/27.2/lisp/org/)]
Date: Thu, 17 Nov 2022 08:49:40 +1100	[thread overview]
Message-ID: <865yfed0nu.fsf@gmail.com> (raw)
In-Reply-To: <87wn8ekm7v.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

>> This is all an aside to the actual bug, so please don't miss that
>> (unless it has been fixed) i.e. a org-html-postamble string with a space
>> in it does not work.
> I am confused here.
> The original bug talked specifically about situation like
> #+options: html-postamble:"test with spaces"
> Are you saying that you cannot have spaces in org-html-postamble
> variable? If yes, could you please provide a reproducer?

To be honest, it was so long ago when I looked into verifying this
issue, I no longer recall the precise details. My memory was that just
having a space in the footer triggered the issue - it didn't have to be
only when the value was set via #+options, but I could be wrong. If you
cannot reproduce the bug just using spaces set, for example, with a
setting in org-publish-project-alist, then I'd say the issue is

My main concern here was that it wasn't clear whether the underlying
issue had been addressed and while the doc improvements are great, I
didn't want the actual triggering issue to get lost amongst all the


  parent reply	other threads:[~2022-11-16 21:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 16:35 Bug: html-postamble string does not allow space [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/27.2/lisp/org/)] Pierre Balayé
2022-06-13  2:45 ` Tim Cross
2022-10-07  8:05   ` Ihor Radchenko
2022-10-30 22:02     ` Tim Cross
2022-10-31  1:22       ` Ihor Radchenko
2022-10-31  1:54         ` Tim Cross
2022-11-02  4:35           ` Ihor Radchenko
2022-11-16  4:50             ` Ihor Radchenko
2022-11-16 21:49             ` Tim Cross [this message]
2022-11-17  5:49               ` Ihor Radchenko
2022-11-17  4:56 ` 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:

  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=865yfed0nu.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    --cc=yantar92@posteo.net \


* 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


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).