--- Begin Message ---
Subject: |
24.3.50; inotify-add-watch fails in batch mode |
Date: |
Sat, 09 Feb 2013 22:35:49 +0800 |
On latest trunk, `make check' fails with
2 unexpected results:
FAILED ert-test-record-backtrace
FAILED inotify-file-watch-simple
The first of this is Bug#13064 (still not fixed; I couldn't disentangle
the mess of CL-isms and closures involved in that bug). The second
failure is relatively new: apparently, inotify-file-watch-simple works
when Emacs is interactive but fails in batch mode.
Another way to see this is to create a file with the contents
(let* ((temp-file (make-temp-file "inotify-simple"))
(events 0)
(wd
(inotify-add-watch temp-file t (lambda (ev)
(setq events (1+ events))))))
(unwind-protect
(progn
(with-temp-file temp-file
(insert "Foo\n"))
(sit-for 5)
(message ">> %d <<" events))
(inotify-rm-watch wd)))
and run `emacs -batch -l foo.el'. This prints ">> 0 <<", indicating
that the inotify watcher failed to run. If you repeat omitting -batch,
">> 4 <<" is printed, as expected.
In GNU Emacs 24.3.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4)
of 2013-02-09 on tsparkle
Bzr revision: 111704 address@hidden
Windowing system distributor `The X.Org Foundation', version 11.0.11301000
Configured using:
`configure --with-x-toolkit=gtk3 CFLAGS=-g --no-create --no-recursion'
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#13662: 24.3.50; inotify-add-watch fails in batch mode |
Date: |
Fri, 17 Jan 2014 12:56:51 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
Chong Yidong <address@hidden> writes:
> Another way to see this is to create a file with the contents
>
> (let* ((temp-file (make-temp-file "inotify-simple"))
> (events 0)
> (wd
> (inotify-add-watch temp-file t (lambda (ev)
> (setq events (1+ events))))))
> (unwind-protect
> (progn
> (with-temp-file temp-file
> (insert "Foo\n"))
> (sit-for 5)
> (message ">> %d <<" events))
> (inotify-rm-watch wd)))
>
> and run `emacs -batch -l foo.el'. This prints ">> 0 <<", indicating
> that the inotify watcher failed to run. If you repeat omitting -batch,
> ">> 4 <<" is printed, as expected.
Should be fixed with r116052. Instead of `sit-for', one needs to apply
`read-event'.
Best regards, Michael.
--- End Message ---