Opened 9 years ago
Closed 9 years ago
#24875 closed Bug (duplicate)
inotify broken with vim, dev server does not restart
| Reported by: | Chris Bainbridge | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Commit 15f82c7 ("used pyinotify as change detection system when
available") introduced a regression where editing a file in vim with
default settings (writebackup=auto) would no longer cause the dev server
to be restarted. On a write, vim moves the monitored file to a backup
path, and then creating a new file in the original. The new file is not
monitored as it has a different inode. Fix this by also watching for
inotify events IN_DELETE_SELF and IN_MOVE_SELF.
Attachments (1)
Change History (3)
by , 9 years ago
| Attachment: | 0001-Detect-moved-file-when-using-inotify-polling.patch added |
|---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
This was already reported in #23882
Note:
See TracTickets
for help on using tickets.
I'm unable to reproduce this, but maybe my vim is configured differently. I have vim 7.4.52 (default that comes with Ubuntu 14.04).
:set writebackup?yieldswritebackup(no mention of "auto"). Could you clarify how to reproduce? Thanks!