unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Juan José García-Ripoll" <juanjose.garcia.ripoll@csic.es>
Cc: Eli Zaretskii <eliz@gnu.org>, 56499@debbugs.gnu.org
Subject: bug#56499: 28.1; Unable to open large file
Date: Tue, 12 Jul 2022 15:33:21 +0200	[thread overview]
Message-ID: <87y1wywj4u.fsf@gnus.org> (raw)
In-Reply-To: <86fsj7y2oz.fsf@csic.es> ("Juan José García-Ripoll"'s message of "Mon, 11 Jul 2022 19:33:16 +0200")

Juan José García-Ripoll <juanjose.garcia.ripoll@csic.es> writes:

> The file is living in OneDrive in Windows 10/11. I will try with other
> files in the same file system, but it has hit me hard this week, which
> I am in remote mode.

As Eli says, buffer-file-name apparently being nil in this case, and
that's very odd.

Could there be a special file name handler for OneDrive that's doing
something odd?

What does

M-: (find-file-name-handler "~/OneDrive/Mail/archive/Archives-2017.mbox" 'insert-file-contents) RET

say?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-07-12 13:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 17:09 bug#56499: 28.1; Unable to open large file Juan José García Ripoll
2022-07-11 17:28 ` Eli Zaretskii
2022-07-11 17:33   ` Juan José García-Ripoll
2022-07-12 13:33     ` Lars Ingebrigtsen [this message]
2022-07-12 13:46       ` Juan Jose Garcia Ripoll
2022-07-12 13:51         ` Eli Zaretskii
2022-07-13  8:22           ` Juan Jose Garcia Ripoll
2022-07-13 11:46             ` Eli Zaretskii
2022-07-13 16:11               ` Juan Jose Garcia Ripoll
2022-07-14  7:01                 ` Eli Zaretskii
2022-07-12 13:55         ` Lars Ingebrigtsen
2022-07-12 16:10           ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1wywj4u.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56499@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juanjose.garcia.ripoll@csic.es \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).