Org-mode mailing list
 help / color / mirror / Atom feed
From: David Masterson <>
Subject: Re: :auto-sitemap in org-publish-project-alist ??
Date: Tue, 06 Oct 2020 21:00:38 -0700
Message-ID: <> (raw)
In-Reply-To: <> (Nicolas Goaziou's message of "Tue, 06 Oct 2020 12:22:06 +0200")

Nicolas Goaziou <> writes:

> Hello,
> David Masterson <> writes:
>> David Masterson <> writes:
>>> My org-publish-project-alist kind of looks like this:
>>> (setq org-publish-project-alist
>>>       '(("orgfiles"
>>> 	 :base-directory "~/DSM/MyOrg/"
>>> 	 :base-extension "org"
>>> 	 :publishing-directory "~/Publish/html/"
>>> 	 :publishing-function org-html-publish-to-html
>>> 	 :headline-levels 6
>>> 	 :section-numbers t
>>> 	 :makeindex t
>>> 	 :auto-sitemap t
>>> 	 :exclude ""
>>> 	 :with-toc nil)))
>>> If I publish my files, is made in a buffer and written to a
>>> file,  Thereafter, org-publish always says has been changed
>>> on disk and asks about updating it.  Since it is a generated file, that
>>> shouldn't be necessary.
>>> Is there a way to turn that off and just have it overwrite the file?
>> Anyone seeing this?
> No. Could you M-x toggle-degug-on-quit, reproduce it, C-g when you're
> asked about updating the file, and send the backtrace?

I'm confused -- now it works!  Maybe when I updated to 9.4?  The
org-publish process seems to be taking a lot longer to walk thru the
files like it is checking more deeply.  It rebuilds the sitemap file and
runs it thru latex to produce a pdf which is correct.

I'll keep an eye on it and see if the problem comes back.

David Masterson

      reply	other threads:[~2020-10-07  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-26  5:34 :auto-sitemap in org-publish-project-alist David Masterson
2020-10-02  0:13 ` :auto-sitemap in org-publish-project-alist ?? David Masterson
2020-10-06 10:22   ` Nicolas Goaziou
2020-10-07  4:00     ` David Masterson [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:

  List information:

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

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone