From: David O'Toole <dto@gnu.org>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 4.68
Date: Sat, 17 Mar 2007 07:38:41 -0400 [thread overview]
Message-ID: <m3ejnom75q.fsf@gnu.org> (raw)
In-Reply-To: <b21e6a719e5c39840831e1ecd328e4a4@science.uva.nl> (Carsten Dominik's message of "Fri\, 16 Mar 2007 18\:08\:33 +0100")
Hi everyone,
I'll set aside some time this week to straighten out these
problems. Sorry I haven't been too vocal on the orgmode list lately, I
have been working on other things.
Is there anything else people want me to add/fix in org-publish while
I am at it?
Carsten Dominik <dominik@science.uva.nl> writes:
> On Mar 16, 2007, at 12:11, Bastien wrote:
>> * org-publish issues
>>
>> C-c C-e A (org-publish-all) won't save the window configuration,
>> depending on what buffers are to be saved and published.
>>
>> Using timestamps for org-publish is *very convenient*. But forcing
>> re-publication of all the pages (C-u C-c C-e a), makes emacs
>> complains
>> about missing directories in ~/.org-timestamps when a project has not
>> been normally published first (with C-c C-e P or C-c C-e A). I think
>> forced re-publication should create these directories itself.
>
> I have forwarded this mail to David O'Toole, to find out if he still
> feels responsible for changes in org-publish. Lets wait if he responds.
--
David O'Toole
dto@gnu.org
http://dto.freeshell.org/notebook/
next prev parent reply other threads:[~2007-03-17 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 4:31 Org-mode version 4.68 Carsten Dominik
2007-03-16 11:11 ` Bastien
2007-03-16 17:08 ` Carsten Dominik
2007-03-16 18:39 ` Bastien
2007-03-18 7:00 ` Carsten Dominik
2007-03-17 11:38 ` David O'Toole [this message]
2007-03-31 21:58 ` T. V. Raman
2007-05-21 6:36 ` Carsten Dominik
2007-03-19 14:21 ` Alex Fu
2007-03-20 12:14 ` Carsten Dominik
2007-03-21 6:59 ` Carsten Dominik
2007-03-21 8:58 ` Bastien
2007-03-22 8:25 ` Leo
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=m3ejnom75q.fsf@gnu.org \
--to=dto@gnu.org \
--cc=dominik@science.uva.nl \
--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).