emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: stardiviner <numbchild@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-capture got file userlock error when I capture on second time.
Date: Wed, 22 Mar 2023 11:38:51 +0000	[thread overview]
Message-ID: <87y1npnhh0.fsf@localhost> (raw)
In-Reply-To: <CAL1eYu+KRZrQZNN+YtBZFZTZ4X7tcnt-ALQ0s=YEcLC+fuJXnw@mail.gmail.com>

stardiviner <numbchild@gmail.com> writes:

> When I org-capture from elfeed-entry buffer (I defined custom functions to
> extract elfeed entry buffer content) in the second time and later, the
> bellowing error raised up. The first-time capture is fine.
>
> Here is the error backtrace:
> #+begin_example
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   expand-file-name(nil)
>   userlock--check-content-unchanged("~/Org/Tasks/Tasks.org")

This looks like some interaction between Org setting `buffer-file-name'
to nil in *Capture* buffer and Emacs' file locking machinery. Maybe.
Maybe Emacs bug. I have no better ideas.

I also see nothing wrong we do on Org side.

-- 
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:[~2023-03-22 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 12:53 [BUG] org-capture got file userlock error when I capture on second time stardiviner
2023-03-22 11:38 ` Ihor Radchenko [this message]
2023-03-23  4:07   ` [CANCELED] " Christopher M. Miles

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