emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kondo Kenji <t60500@mail.ecc.u-tokyo.ac.jp>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: Kondo Kenji <t60500@mail.ecc.u-tokyo.ac.jp>,
	Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Bug: org-publish-current-project reverses the force	flag.
Date: Thu, 28 Feb 2008 08:45:24 +0900	[thread overview]
Message-ID: <87lk56neuj.wl%t60500@mail.ecc.u-tokyo.ac.jp> (raw)
In-Reply-To: <8E0EE7D9-D622-4F1D-8C90-16F5DF03F196@science.uva.nl>


Hmm. I tried the git version but timestampes didn't work with C-c C-e P
when `org-publish-use-timestamps-flag' is t.

Is it OK in your environment?

--
Kondo Kenji

At Wed, 27 Feb 2008 16:14:40 +0100,
Carsten Dominik wrote:
> 
> Thanks, I believe this is now fixes as well, please let me know if not.
> 
> - Carsten
> 
> On Feb 26, 2008, at 5:46 PM, Kondo Kenji wrote:
> 
> >
> > Thank you but I'm afraid there still exists one problem to fix.
> >
> > When `org-publish-use-timestamps-flag' is t,
> > `C-c C-e P' or `M-x org-publish-current-project'
> > publishes not only changed files but also unchanged files.
> >
> > --
> > Kondo Kenji
> >
> > At Tue, 26 Feb 2008 16:02:31 +0100,
> > Carsten Dominik wrote:
> >>
> >> Indeed, there was a bug, I have fixed it ow, available in the git
> >> repository, or later
> >> in the next release (5.23).
> >>
> >> Thanks for the report.
> >>
> >> - Carsten
> >>
> >> On Feb 25, 2008, at 7:23 PM, t60500@mail.ecc.u-tokyo.ac.jp wrote:
> >>
> >>>
> >>> Hi.
> >>>
> >>> I've found (maybe) a bug.
> >>>
> >>> With org 5.22a (org-publish.el version 1.80 b),
> >>> org-publish-current-project reverses the force flag
> >>> when passing the flag to org-publish.
> >>>
> >>> Thanks.
> >>>
> >>> -- 
> >>> Kondo Kenji <kondo@misojiro.t.u-tokyo.ac.jp>
> >>>
> >>>
> >>> _______________________________________________
> >>> Emacs-orgmode mailing list
> >>> Remember: use `Reply All' to send replies to the list.
> >>> Emacs-orgmode@gnu.org
> >>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> >>
> >>
> >>
> >> _______________________________________________
> >> Emacs-orgmode mailing list
> >> Remember: use `Reply All' to send replies to the list.
> >> Emacs-orgmode@gnu.org
> >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 

  reply	other threads:[~2008-02-27 23:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 18:23 Bug: org-publish-current-project reverses the force flag t60500
2008-02-26  8:06 ` Carsten Dominik
2008-02-26 12:20   ` Kondo Kenji
2008-02-26 14:19     ` Carsten Dominik
2008-02-26 15:02 ` Carsten Dominik
2008-02-26 16:46   ` Kondo Kenji
2008-02-27 15:14     ` Carsten Dominik
2008-02-27 23:45       ` Kondo Kenji [this message]
2008-02-28  1:14         ` Bastien
2008-02-28  2:51           ` Kondo Kenji

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=87lk56neuj.wl%t60500@mail.ecc.u-tokyo.ac.jp \
    --to=t60500@mail.ecc.u-tokyo.ac.jp \
    --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).