emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: emacs-orgmode@gnu.org
Subject: Re: reevaluating org-x11idle-exists-p with new org-clock-x11idle-program-name
Date: Wed, 26 May 2021 15:47:46 +0200	[thread overview]
Message-ID: <878s41wqrh.fsf@free.fr> (raw)
In-Reply-To: 87o8czw6od.fsf@free.fr

Julien Cubizolles <j.cubizolles@free.fr> writes:

> Tim Cross <theophilusx@gmail.com> writes:
>> Julien Cubizolles <j.cubizolles@free.fr> writes:
>>> I'm using a custom python program to display x11 idle time. I've set
>>> org-clock-x11idle-program-name accordingly but org-x11idle-exists-p is
>>> still nil. I'm guessing it's defvar'ed in org-clock.el before
>>> org-clock-x11idle-program-name is set. Evaluating the defvar of
>>> org-x11idle-exists-p afterwards indeed sets it to t.
>>> I could do (setq org-x11idle-exists-p t) but there must be a better way
>>> to handle the definition of a new org-clock-x11idle-program-name.
>> How are you setting org-clock-x11idle-program-name? In your init file or
>> via custom? 
> Setting it via custom works thanks. Somehow org was loaded by some
> dependency before I explicitly used (require 'org). I guess I could also
> use some use-package configuration.

Actually it doesn't… Even with org-clock-x11idle-program-name set via
custom, org-x11idle-exists-p is still nil at startup. And
custom-set-variables is set at the very beginning of my init file. I'll
file an issue.

Julien Cubizolles

      reply	other threads:[~2021-05-26 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24  7:40 reevaluating org-x11idle-exists-p with new org-clock-x11idle-program-name Julien Cubizolles
2021-05-24 13:37 ` Tim Cross
2021-05-25  8:37   ` Julien Cubizolles
2021-05-26 13:47     ` Julien Cubizolles [this message]

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=878s41wqrh.fsf@free.fr \
    --to=j.cubizolles@free.fr \
    --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).