all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "Alejandro Pérez Carballo" <apc@umass.edu>
Cc: 58964@debbugs.gnu.org
Subject: bug#58964: 28.2; `file-notify--handle-event` setting callback function to nil
Date: Thu, 03 Nov 2022 08:46:35 +0100	[thread overview]
Message-ID: <87fsf0bhus.fsf@gmx.de> (raw)
In-Reply-To: <m2v8nxzfy5.fsf@umass.edu> ("Alejandro Pérez Carballo"'s message of "Wed, 02 Nov 2022 08:41:38 -0400")

Alejandro Pérez Carballo <apc@umass.edu> writes:

Hi Alejandro,

> The following minimal configuration can be used to trigger the bug on my
> end, replacing “~/tmp/test.el” with a path to a file of your choice:
>
>     (require 'filenotify)
>     (require 'autorevert)
>     (require 'subr-x)
>     (global-auto-revert-mode)
>     
>     (save-window-excursion
>       (find-file "~/tmp/test.el"))
>
> Once that’s loaded, calling this:
>
>     (file-notify--handle-event (car (hash-table-keys file-notify-descriptors)) '(renamed attribute-changed deleted) (expand-file-name "~/tmp/test.el") nil)
>
> gives me an error
>
>     file-notify--call-handler: Symbol’s function definition is void: nil

This is not a valid call of `file-notify--handle-event', see its
docstring how it shall be applied.

Furthermore, this function is an internal one which shouldn't be called
from outside filenotify.el. What's your use case for this?

Best regards, Michael.





  reply	other threads:[~2022-11-03  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 12:41 bug#58964: 28.2; `file-notify--handle-event` setting callback function to nil Alejandro Pérez Carballo
2022-11-03  7:46 ` Michael Albinus [this message]
2022-11-04  0:11   ` Alejandro Pérez Carballo
2022-11-04 13:09     ` 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=87fsf0bhus.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=58964@debbugs.gnu.org \
    --cc=apc@umass.edu \
    /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.