emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
To: Bastien <bzg@gnu.org>, Achim Gratz <Stromeko@nexgo.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: BUG! Re:  Byte compiler warnings in org-clock.el
Date: Fri, 13 Jul 2012 14:04:38 +0100 (BST)	[thread overview]
Message-ID: <1342184678.51826.YahooMailNeo@web29805.mail.ird.yahoo.com> (raw)
In-Reply-To: <87liiosful.fsf@gnu.org>

Da: Bastien <bzg@gnu.org>
Inviato: Venerdì 13 Luglio 2012 1:46

> Achim Gratz <Stromeko@nexgo.de> writes:

> > The corresponding defvar should probably be moved:
probably not.

@Achim that's why I wanted to have the last version: to report bugs, 
as stated in the documentation  [[info:org#Feedback]]

"For bug reports, please first try to reproduce the bug with the
latest version of Org available"

> Done, thanks.

Unfortunately this introduces a bug:

In a new file (with a pending clock)

with Org-mode version 7.8.11 (3ecd7a9ad03323 

when I try to start a clock I get the error:

Symbol's function definition is void: org-clock-in-last 
Debugger entered--Lisp error: (void-function org-clock-in-last)

whereas I can clock in with version: Org-mode version 7.8.11 (1fe42fd0b 
[and the pending clock is resolved]

If the file is already opened and after M-x org-reload
I the current clock is closed 
when one try to clock in a new subheading
the last subtree is clocked-in 



  reply	other threads:[~2012-07-13 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 18:25 Byte compiler warnings in org-clock.el Achim Gratz
2012-07-12 23:46 ` Bastien
2012-07-13 13:04   ` Giovanni Ridolfi [this message]
2012-07-14  7:01     ` BUG! " Bastien
2012-07-13 18:40   ` Achim Gratz
2012-07-14  6:59     ` New keybinding C-c C-x C-q for ̀org-clock-cancel' (was: Byte compiler warnings in org-clock.el) Bastien
2012-07-14 17:14       ` Samuel Wales

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=1342184678.51826.YahooMailNeo@web29805.mail.ird.yahoo.com \
    --to=giovanni.ridolfi@yahoo.it \
    --cc=Stromeko@nexgo.de \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


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