GNU bug report logs -
#28655
25.2; Problem with find-file-noselect
Previous Next
Reported by: Live System User <nyc4bos <at> aol.com>
Date: Sat, 30 Sep 2017 18:43:01 UTC
Severity: minor
Tags: moreinfo, wontfix
Found in version 25.2
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #8 received at 28655 <at> debbugs.gnu.org (full text, mbox):
Live System User wrote:
> The partion where my /home directory is mounted became
> unrelatedly readonly.
>
> When I tried to visit a file, readonly "C-x C-r"
> `(find-file-read-only),` I got the following
> *Backtrace* (see below).
[...]
> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
> file-truename(nil)
> find-file-noselect-1(#<buffer dt.el<2>> "~/dt.el" nil nil "~/dt.el" (6637 64770))
> find-file-noselect("~/dt.el" nil nil t)
> find-file("~/dt.el" t)
> find-file--read-only(find-file "~/dt.el" t)
> find-file-read-only("~/dt.el" t)
> funcall-interactively(find-file-read-only "~/dt.el" t)
> call-interactively(find-file-read-only nil nil)
> command-execute(find-file-read-only)
I can't reproduce this. I tried with:
mount -t tmpfs -o size=10m tmpfs /mnt/
HOME=/mnt emacs-25.2 -Q &
...
mount -r -o remount /mnt/
and C-x C-r continues to work fine.
The above backtrace isn't detailed enough to debug this issue.
I can only guess that buffer-file-name somehow became nil.
How, I have no idea.
This bug report was last modified 7 years and 232 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.