all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] [bug] clocking in suddenly does not work any more [9.7-pre (release_9.6.18-1197-ga250fc @ /home/grfz/src/org-mode/lisp/)]
Date: Tue, 27 Feb 2024 00:22:08 +0100	[thread overview]
Message-ID: <87msrmyfof.fsf@no.lan> (raw)
In-Reply-To: <87wmqrdlnh.fsf@no.lan>

Dear org-mode users and developers,
* Gregor Zattler <grfz@gmx.de> [2024-02-26; 21:18 +01]:
> I used to clock in (and out) on a certain node several
> times a day.  Also today, but this suddenly does not
> work any more, it inserts only a
>
> CLOCK:
>
> (with preceeding blank) but no following time stamp and

wrong: with succeeding blank, sorry English is not my
first language.

> I get the message: "org-clock-sum-current-item: Wrong
> type argument: fixnump, nil"
>
> This still works with emacs -Q, so is somehow related
> to my configuration, but I get this error even with my
> whole emacs.d replaced by the backup from yesterday and
> ~/.cache/emacs/ ~/.cache/org-persist/ org-clock-save.el
> deleted.

I played a bit around.  If I delete the following part
of the LOGBOOK:

ClOCK: [2024-02-26 Mo 11:35]--[2024-02-26 Mo 11:40] =>  0:05
- Clocking out at [2024-02-26 Mo 11:40]

it works again.  The "l" in "ClOCK" is not
capitalized.  I wonder how I managed to change that
single letters capitalization.

For me the problem is solved, although I do not
understand, why emacs -Q does not stumble over this
while my configured Emacs does....


Regards, Gregor

Canceled, I hope this works for woof!


  reply	other threads:[~2024-02-26 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 20:18 [BUG] [bug] clocking in suddenly does not work any more [9.7-pre (release_9.6.18-1197-ga250fc @ /home/grfz/src/org-mode/lisp/)] Gregor Zattler
2024-02-26 23:22 ` Gregor Zattler [this message]
2024-02-27 12:59 ` Ihor Radchenko

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

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

  git send-email \
    --in-reply-to=87msrmyfof.fsf@no.lan \
    --to=telegraph@gmx.net \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.