From: Ihor Radchenko <yantar92@posteo.net>
To: inigoserna@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: Possible bug: org-capture fails when emacs started as daemon
Date: Sun, 13 Aug 2023 08:37:37 +0000 [thread overview]
Message-ID: <87fs4nl4mm.fsf@localhost> (raw)
In-Reply-To: <87350opi0t.fsf@gmx.com>
Iñigo Serna <inigoserna@gmx.com> writes:
> As I see the error message is defined in either
> `make-indirect-buffer' or `rename-buffer' functions, and the first
> one is called from `org-capture-make-indirect-buffer'.
> How could I investigate further the issue? Any hints?
`org-capture-get-indirect-buffer' constructs a name of a new capture
buffer as
(setq bname (concat prefix "-" base))
(while (buffer-live-p (get-buffer bname))
(setq bname (concat prefix "-" (number-to-string (cl-incf n)) "-" base)))
So, I can see the error happening when the buffer is not live, but yet
exists for some reason.
AFAIK, `get-buffer' check Vbuffer_alist, which should contain only live
buffers. If it is not the case, something fishy may be going on in Emacs.
I'd try to check the value of (get-buffer "CAPTURE-todo.org") and see if
it is a killed buffer or not.
--
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>
next prev parent reply other threads:[~2023-08-13 8:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 12:14 Possible bug: org-capture fails when emacs started as daemon Iñigo Serna
2023-08-12 17:05 ` Morgan Willcock
2023-08-13 15:09 ` Iñigo Serna
2023-08-13 8:37 ` Ihor Radchenko [this message]
2023-08-13 15:29 ` Iñigo Serna
2023-08-13 15:38 ` Ihor Radchenko
2023-08-15 16:53 ` Morgan Willcock
2023-08-15 16:57 ` Ihor Radchenko
2023-08-15 18:57 ` Eli Zaretskii
2023-08-16 9:25 ` Iñigo Serna
2023-08-16 14:04 ` Eli Zaretskii
2023-08-16 14:59 ` Iñigo Serna
2023-08-16 15:00 ` Stefan Monnier
2023-08-16 15:44 ` Iñigo Serna
2023-08-16 17:04 ` Eli Zaretskii
2023-08-16 17:46 ` Stefan Monnier
2023-08-17 7:53 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs4nl4mm.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=inigoserna@gmail.com \
/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.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).