From: Michael Albinus <michael.albinus@gmx.de>
To: John Wiegley <johnw@gnu.org>
Cc: 29450@debbugs.gnu.org
Subject: bug#29450: 26.0.90; No check for nil in some filenotify functions
Date: Thu, 11 Jan 2018 10:13:11 +0100 [thread overview]
Message-ID: <87fu7chi6w.fsf@gmx.de> (raw)
In-Reply-To: <m24lnt5kv6.fsf@newartisans.com> (John Wiegley's message of "Wed, 10 Jan 2018 15:56:13 -0800")
John Wiegley <johnw@gnu.org> writes:
Hi,
Sorry to jump in such late; I've overlooked this thread before.
>>>> I've been getting several errors with a backtrace like nil(48). This is
>>>> likely because some package has done something wrong, but even still,
>>>> filenotify should be more defensive.
>>>
>>> Can you show a full backtrace like that?
>
> I worked around this with (setq auto-revert-use-notify nil). If it doesn't
> happen for anyone else, you can close it. I'll look into it again if I ever
> decide to re-enable this.
I still would like to see a full backtrace. You have quoted
--8<---------------cut here---------------start------------->8---
(when-let* ((watch (gethash descriptor file-notify-descriptors)))
(let ((handler (find-file-name-handler
(file-notify--watch-directory watch)
'file-notify-rm-watch)))
--8<---------------cut here---------------end--------------->8---
I have the feeling that it isn't the return value of
`find-file-name-handler' being nil, but rather the
`file-notify--watch-directory' call.
Best regards, Michael.
next prev parent reply other threads:[~2018-01-11 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 6:18 bug#29450: 26.0.90; No check for nil in some filenotify functions John Wiegley
2017-11-26 15:39 ` Eli Zaretskii
2018-01-10 0:28 ` Glenn Morris
2018-01-10 23:56 ` John Wiegley
2018-01-11 9:13 ` Michael Albinus [this message]
2018-02-05 6:48 ` John Wiegley
2018-02-05 7:45 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu7chi6w.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=29450@debbugs.gnu.org \
--cc=johnw@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.