emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: David Masterson <dsmasterson92630@outlook.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: :auto-sitemap in org-publish-project-alist ??
Date: Tue, 06 Oct 2020 12:22:06 +0200	[thread overview]
Message-ID: <87lfgju01d.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <SJ0PR03MB561590737B490270E32812729B310@SJ0PR03MB5615.namprd03.prod.outlook.com> (David Masterson's message of "Thu, 01 Oct 2020 17:13:08 -0700")

Hello,

David Masterson <dsmasterson92630@outlook.com> writes:

> David Masterson <dsmasterson92630@outlook.com> 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 "init.org"
>> 	 :with-toc nil)))
>>
>>
>> If I publish my files, sitemap.org is made in a buffer and written to a
>> file,  Thereafter, org-publish always says sitemap.org 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?

Regards,
-- 
Nicolas Goaziou


  reply	other threads:[~2020-10-06 10:23 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 [this message]
2020-10-07  4:00     ` David Masterson

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=87lfgju01d.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=dsmasterson92630@outlook.com \
    --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).