summaryrefslogtreecommitdiff
path: root/lisp/filenotify.el
diff options
context:
space:
mode:
authorMattias EngdegÄrd <mattiase@acm.org>2019-05-19 22:43:31 +0200
committerMattias EngdegÄrd <mattiase@acm.org>2019-05-19 22:47:31 +0200
commit6d5a8175b34e02fc42c965b5cf6e83c954390f0b (patch)
treef47a8907b7210f40bd099027b9c1964310c37d72 /lisp/filenotify.el
parent613565494d048ec758d5051484a17fdeccd42f00 (diff)
downloademacs-6d5a8175b34e02fc42c965b5cf6e83c954390f0b.tar.gz
Comment out inexplicable condition in filenotify
* lisp/filenotify.el (file-notify-callback): Comment out condition that does not seem to make any sense. All it seems to do is allowing notifications for files on the form DIR/X/X when we really just are watching DIR/X/Y.
Diffstat (limited to 'lisp/filenotify.el')
-rw-r--r--lisp/filenotify.el14
1 files changed, 10 insertions, 4 deletions
diff --git a/lisp/filenotify.el b/lisp/filenotify.el
index 26b83ce66c0..d77046d2871 100644
--- a/lisp/filenotify.el
+++ b/lisp/filenotify.el
@@ -238,11 +238,17 @@ EVENT is the cadr of the event in `file-notify-handle-event'
(string-equal
(file-notify--watch-filename watch)
(file-name-nondirectory file))
+
;; Directory matches.
- (string-equal
- (file-name-nondirectory file)
- (file-name-nondirectory
- (file-notify--watch-directory watch)))
+ ;; FIXME: What purpose would this condition serve?
+ ;; Doesn't it just slip through events for files
+ ;; having the same name as the last component of the
+ ;; directory of the file that we are really watching?
+ ;;(string-equal
+ ;; (file-name-nondirectory file)
+ ;; (file-name-nondirectory
+ ;; (file-notify--watch-directory watch)))
+
;; File1 matches.
(and (stringp file1)
(string-equal