GNU bug report logs -
#66993
[PATCH] project.el: avoid asking user about project-list-file lock
Previous Next
Full log
Message #121 received at 66993-done <at> debbugs.gnu.org (full text, mbox):
> From: Spencer Baugh <sbaugh <at> catern.com>
> Date: Fri, 10 Nov 2023 12:48:36 +0000 (UTC)
> Cc: Spencer Baugh <sbaugh <at> janestreet.com>, dmitry <at> gutov.dev,
> 66993 <at> debbugs.gnu.org
>
> > Thanks, that's what I thought: this loses information. The "Cannot
> > resolve lock conflict in batch mode" part is important, since it
> > explains the "file-locked" part. So please include the missing text
> > in the list passed to 'signal' as its DATA argument, so as not to lose
> > this explanation.
>
> OK, how about this? Which makes Emacs print:
>
> Error: file-locked ("/home/sbaugh/file" "sbaugh <at> earth (pid 1852838)" "Cannot resolve lock conflict in batch mode")
> mapbacktrace(#f(compiled-function (evald func args flags) #<bytecode -0x1f22147a251783b>))
> debug-early-backtrace()
> debug-early(error (file-locked "/home/sbaugh/file" "sbaugh <at> earth (pid 1852838)" "Cannot resolve lock conflict in batch mode"))
> signal(file-locked ("/home/sbaugh/file" "sbaugh <at> earth (pid 1852838)" "Cannot resolve lock conflict in batch mode"))
> ask-user-about-lock("/home/sbaugh/file" "sbaugh <at> earth (pid 1852838)")
> write-region("foo" nil "~/file")
> eval((write-region "foo" nil "~/file") t)
> command-line-1(("--eval" "(write-region \"foo\" nil \"~/file\")"))
> command-line()
> normal-top-level()
> /home/sbaugh/file: sbaugh <at> earth (pid 1852838), Cannot resolve lock conflict in batch mode
Thanks, installed on master, and closing the bug.
This bug report was last modified 1 year and 268 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.