[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[CANCELED] Re: [BUG] org-capture got file userlock error when I capture
Christopher M. Miles
[CANCELED] Re: [BUG] org-capture got file userlock error when I capture on second time.
Thu, 23 Mar 2023 12:07:00 +0800
mu4e 1.8.14; emacs 30.0.50
Ihor Radchenko <firstname.lastname@example.org> writes:
> stardiviner <email@example.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:
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> 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.
First, Ihor, I need to thank you. With your hints. I try to figure out
what things might get involved between Org setting `buffer-file-name'
and *Capture* buffer.
1. I try to set `org-capture-mode-hook`, `org-mode-hook' etc to nil.
2. Use bug-hunter to bisect my emacs config, the first start, the
problem does not occurred, this is weird, even I tried many times.
3. Then I use comment to bisect my init.el, try to figure out the
reason. Still not found. And the problem not occurred.
4. I start Emacs again with original config. Now the problem gone. I
restart Emacs many times, problem still not occurred. Weird.
[ stardiviner ]
I try to make every word tell the meaning that I want to express without
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
Description: PGP signature