procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix execution of MS-Windows app execution aliases in Eshell

Browse source 
* lisp/eshell/esh-ext.el (eshell-script-interpreter): Check for 0-size
files (bug#71655).
This commit is contained in:
Jim Porter 2024-06-22 12:45:19 -07:00
parent fffab032b0
commit 130c3efa10
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
lisp/eshell/esh-ext.el
View file

@ -301,7 +301,17 @@ Return nil, or a list of the form:
(INTERPRETER [ARGS] FILE)"
(let ((maxlen eshell-command-interpreter-max-length))
(if (and (file-readable-p file)
(file-regular-p file))
(file-regular-p file)
;; If the file is zero bytes, it can't possibly have a
;; shebang. This check may seem redundant, but we can
;; encounter files that Emacs considers both readable and
;; regular, but which aren't *actually* readable. This can
;; happen, for example, with certain kinds of reparse
;; points like APPEXECLINK on NTFS filesystems (MS-Windows
;; uses these for "app execution aliases"). In these
;; cases, the file size is 0, so this check protects us
;; from errors.
(> (file-attribute-size (file-attributes file)) 0))
(with-temp-buffer
(insert-file-contents-literally file nil 0 maxlen)
(if (looking-at "#![ \t]*\\([^ \r\t\n]+\\)\\([ \t]+\\(.+\\)\\)?")