emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Serghei Iakovlev <lists@serghei.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-refile-get-targets wrong-type-argument [9.6.15 (release_9.6.15 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Date: Sun, 22 Sep 2024 09:27:28 +0000	[thread overview]
Message-ID: <87wmj4qbr3.fsf@localhost> (raw)
In-Reply-To: <m1h6adb3mt.fsf@serghei.pl>

[ Adding Org mailing list back to the CC ]

> -(defun my-org-opened-buffer-files ()
> -  "Return the list of org files currently opened in Emacs."
> -  (delq nil
> -        (mapcar (lambda (x)
> -                  (if (and (buffer-file-name x)
> -                           (string-match "\\.org$"
> -                                         (buffer-file-name x)))
> -                      (buffer-file-name x)))
> -                (buffer-list))))
> -

> It was added as part of one of my experiments, and I apparently don't
> need this functionality at all.  So, I can easily remove it to test
> this hypothesis. Unfortunately, I don't have any other leads at the
> moment.
>
> I would greatly appreciate any advice on how to investigate this
> further or understand the root cause of the problem.

What you might do is adding
a check whether `org-complex-heading-regexp' is nil in any of the
buffers returned by your `my-org-opened-buffer-files' and raise an error
telling which buffer it is.

You may then check what's up with that buffer.

Best,
Ihor

Serghei Iakovlev <lists@serghei.pl> writes:

> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.orgmode as well.
>
>
>> My only guess is that some of your Org buffers is not properly
>> initialized somehow. Maybe the timer is triggering in the middle of Org
>> mode loading or something?
>
> I find it challenging to pinpoint the exact cause of the issue.
> However, I can provide some additional context that might help.  The
> problem seems to occur when I'm not using my laptop—often at night,
> which aligns with the time `run-with-idle-timer' is triggered.
> During these moments, my configuration and environment are relatively
> static, as the workstation is idle.  I usually leave it in that state
> in the evening, and the problem is only noticeable in the morning.
>
> It's worth noting that the issue doesn't happen consistently — not
> every night or even every week.  It just occasionally arises, leaving
> me puzzled about what might need adjustment or modification to
> prevent it.  Given its sporadic nature, I'm at a loss for how to
> reproduce it consistently.
>
> There is literally one lead, and it's this code snippet that I just
> removed from my configuration:
>
> --8<---------------cut here---------------start------------->8---
> diff --git a/init.el b/init.el
> index d18e70c..fbb0d62 100644
> --- a/init.el
> +++ b/init.el
> @@ -1685,21 +1685,10 @@
>  (define-key my-keyboard-map (kbd "b") #'my/org-move-bookmark-to-notes)
>
>  ;;;;; Org Refile
> -(defun my-org-opened-buffer-files ()
> -  "Return the list of org files currently opened in Emacs."
> -  (delq nil
> -        (mapcar (lambda (x)
> -                  (if (and (buffer-file-name x)
> -                           (string-match "\\.org$"
> -                                         (buffer-file-name x)))
> -                      (buffer-file-name x)))
> -                (buffer-list))))
> -
>  ;; Refile targets include this file and any file contributing
>  ;; to the agenda - up to 4 levels deep.
>  (setq org-refile-targets
>        '((nil :maxlevel . 4)  ; nil means current buffer
> -        (my-org-opened-buffer-files :maxlevel . 4)
>          (org-agenda-files :maxlevel . 4)))
>
>  ;; Targets start with the file name allows creating level 1 tasks.
> --8<---------------cut here---------------end--------------->8---
>
> It was added as part of one of my experiments, and I apparently don't
> need this functionality at all.  So, I can easily remove it to test
> this hypothesis. Unfortunately, I don't have any other leads at the
> moment.
>
> I would greatly appreciate any advice on how to investigate this
> further or understand the root cause of the problem.
>
>
> -- 
> Serghei Iakovlev

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-09-22  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 14:34 [BUG] org-refile-get-targets wrong-type-argument [9.6.15 (release_9.6.15 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Serghei Iakovlev
2024-09-16 19:13 ` Ihor Radchenko
2024-09-18 11:30   ` Serghei Iakovlev
2024-09-22  9:27     ` Ihor Radchenko [this message]
2024-11-22 17:41       ` 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

  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=87wmj4qbr3.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=lists@serghei.pl \
    /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).