Open tvraman opened 7 months ago
"T. V. Raman" @.***> writes:
- ( ) text/plain (*) text/html
here is an example. I suggest we not use async emacs to clean up the psessions dir? /home/raman/.emacs.d/elisp-objects/extended-command-history.el: @. (pid 571531), Cannot resolve lock conflict in batch mode Psession: auto saving session done Opening input file: No such file or directory, /home/raman/.emacs.d/elisp-objects/psession-save-buffers-alist.el Psession: auto saving session done /home/raman/.emacs.d/elisp-objects/psession-save-buffers-alist.el: @. (pid 571532), Cannot resolve lock conflict in batch mode Psession: auto saving session done [3 times]
I never hit this even trying to reproduce your bug during one month with a 60s delay. However it seems there is some thing new in your report with this message: "Cannot resolve lock conflict in batch mode". After grepping emacs source it seems this message comes from "userlock.el", so I guess you are using this feature and it is the culprit, can you tell me how you use this and why (so that i can reproduce).
Thanks.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.*Message ID: @.***>
-- Thierry
I'm not knowingly using user-lock.el -- what should I look for in my setup?
--
following up to myself; doing a grep inside my elpa dir showed that folding-mode which I have used for nearly 30 years was calling userlock; I've uninstalled that package for now since I've mostly moved on from using it.
Will report back in a week if that fixes the issue.
--
"T. V. Raman" @.***> writes:
- ( ) text/plain (*) text/html
following up to myself; doing a grep inside my elpa dir showed that folding-mode which I have used for nearly 30 years was calling userlock; I've uninstalled that package for now since I've mostly moved on from using it.
Will report back in a week if that fixes the issue.
Thanks, but AFAIU the function ask-user-about-lock
maybe called by
emacs if another user edit the same file and BTW there is a lock file,
do you have another emacs opened that use also psession?
-- Thierry
No, I am on a laptop and only run one emacs session.
--
here is an example. I suggest we not use async emacs to clean up the psessions dir? /home/raman/.emacs.d/elisp-objects/extended-command-history.el: raman@raman9 (pid 571531), Cannot resolve lock conflict in batch mode Psession: auto saving session done Opening input file: No such file or directory, /home/raman/.emacs.d/elisp-objects/psession-save-buffers-alist.el Psession: auto saving session done /home/raman/.emacs.d/elisp-objects/psession-save-buffers-alist.el: raman@raman9 (pid 571532), Cannot resolve lock conflict in batch mode Psession: auto saving session done [3 times]