From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: juanjose.garcia.ripoll@csic.es, 56499@debbugs.gnu.org
Subject: bug#56499: 28.1; Unable to open large file
Date: Tue, 12 Jul 2022 19:10:07 +0300 [thread overview]
Message-ID: <83v8s2wbvk.fsf@gnu.org> (raw)
In-Reply-To: <8735f6wi3o.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 12 Jul 2022 15:55:39 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, 56499@debbugs.gnu.org
> Date: Tue, 12 Jul 2022 15:55:39 +0200
>
> Juan Jose Garcia Ripoll <juanjose.garcia.ripoll@csic.es> writes:
>
> > I tried evaluating find-file-name-handler as suggested and it returns
> > nil. I suspect it is due to OneDrive (and now also Nextcloud's)
> > virtual files, which live online until requested. Somehow opening the
> > file does not trigger the required download.
>
> It should be transparent to Emacs, but perhaps the OS/OneDrive is
> returning an odd value to Emacs which confuses Emacs? I don't use
> Windows and OneDrive, so I can't test myself. I guess the relevant code
> is in `insert-file-contents', which is implemened in C, so it's not
> trivial to debug.
>
> Eli, do you have any ideas?
Not at this time.
I asked Juan Jose a question, and I will try to find a machine with
OneDrive files to try to reproduce this.
prev parent reply other threads:[~2022-07-12 16:10 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
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 [this message]
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=83v8s2wbvk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56499@debbugs.gnu.org \
--cc=juanjose.garcia.ripoll@csic.es \
--cc=larsi@gnus.org \
/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).