bug#47205: 27.1.91; [bug] unexpected input event interrupted expand-file

[LinSun]

Hi Eli,

 

No effect after add the dbus-event into ` while-no-input-ignore-events`, output still be t.

$ emacs --batch --eval "(message \"%s %s\" (catch 'input

(let* ((while-no-input-ignore-events '(dbus-event))

(throw-on-input 'input))

(expand-file-name \"a.iso/b\" \"/\"))) last-input-event)"

 

The work around is execute “(require ‘trampe-archive)” before eval the statement, output is expanded path:

$ emacs --batch --eval "(require 'tramp-archive)" --eval "(message \"%s %s\" (catch 'input

(let ((throw-on-input 'input)) (expand-file-name \"a.iso/b\" \"/\"))) last-input-event)"

 

From: Eli Zaretskii
Sent: Thursday, March 18, 2021 16:21
To: LinSun
Cc: michael.albinus@gmx.de; 47205@debbugs.gnu.org
Subject: Re: bug#47205: 27.1.91; [bug] unexpected input event interrupted expand-file

 

> Cc: 47205@debbugs.gnu.org

> Date: Thu, 18 Mar 2021 08:27:19 +0800

> From:  LinSun via "Bug reports for GNU Emacs,

>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>

>

> > which problem have you encountered? Or is it just the docstring?

>

> It’s from the issue https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_bbatsov_helm-2Dprojectile_issues_154&d=DwIDaQ&c=8lBT5Jra4Bm5rFhLVR7k1wx3__gIUgr523Abjhgq6Gg&r=6xk5MptCw9C5cby5Hg_N-g&m=EmFfZjQE9VJNjK7pHjDEmisfcl1ldVrjm-uYcGUt15Q&s=7aTI3m35I_H4x7Mt9XlkUo5sFYfTtO3RVucG6-tK7SE&e= ,

>

> “[bug] `helm-projectile-find-file' empty candidate when there is "*.iso/" folder”

>

> Through the traceback I attached in first mail, the dbus event cause a unexpected return value in line

>

> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_emacs-2Dhelm_helm_blob_26d4e9e4d38a143d7dfb2fe206eacbc326944532_helm.el-23L4649&d=DwIDaQ&c=8lBT5Jra4Bm5rFhLVR7k1wx3__gIUgr523Abjhgq6Gg&r=6xk5MptCw9C5cby5Hg_N-g&m=EmFfZjQE9VJNjK7pHjDEmisfcl1ldVrjm-uYcGUt15Q&s=315IlVgey3O_eEx2bEadou9Fga0ofs1zXu2S3T4Ss8E&e= ,

>

> Then it’s function will show nothing.

 

Is this because helm uses while-no-input or throw-on-input?  If so,

does it help to bind while-no-input-ignore-events to a list that

includes this kind of dbus events?