GNU bug report logs - #56499
28.1; Unable to open large file

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juan José García Ripoll <juanjose.garcia.ripoll <at> csic.es>
Cc: 56499 <at> debbugs.gnu.org
Subject: bug#56499: 28.1; Unable to open large file
Date: Mon, 11 Jul 2022 20:28:35 +0300

> From: Juan José García Ripoll
>  <juanjose.garcia.ripoll <at> csic.es>
> Date: Mon, 11 Jul 2022 19:09:49 +0200
> 
> 
> I am trying to load a file with
> (find-file-literally "~/OneDrive/Mail/archive/Archives-2017.mbox")
> either as lisp code or using key commands. Any alternative leads to a
> lisp error with the following backtrace
> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
>   file-truename(nil)
>   find-file-noselect-1(#<buffer Archives-2017.mbox<juanj/OneDrive/Mail/archive>> "~/OneDrive/Mail/archive/Archives-2017.mbox" nil t "~/OneDrive/Mail/archive/Archives-2017.mbox" (281474976939729 250058804))
>   find-file-noselect("~/OneDrive/Mail/archive/Archives-2017.mbox" nil t)
>   find-file-literally("~/OneDrive/Mail/archive/Archives-2017.mbox")
>   eval-expression((find-file-literally "~/OneDrive/Mail/archive/Archives-2017.mbox") nil nil 127)
>   funcall-interactively(eval-expression (find-file-literally "~/OneDrive/Mail/archive/Archives-2017.mbox") nil nil 127)
>   command-execute(eval-expression)
> All this was done from a bare emacs (using -Q)

Does this happen with any file?  If not, what is special about this
file?

It sounds like buffer-file-name is nil for the buffer where the file
is visited, and I don't think I understand how could that happen with
a regular file.

In any case, I cannot reproduce this with random files I tried here.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.