unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juan Jose Garcia Ripoll <juanjose.garcia.ripoll@csic.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 56499@debbugs.gnu.org
Subject: bug#56499: 28.1; Unable to open large file
Date: Wed, 13 Jul 2022 10:22:09 +0200	[thread overview]
Message-ID: <20220713102209.Horde.2zgWs8EuCB8PAyQ_XunK-VF@webmail.csic.es> (raw)
In-Reply-To: <83bktuxwu9.fsf@gnu.org>

[-- Attachment #1: Sólo texto --]
[-- Type: text/plain, Size: 1332 bytes --]

  Apologies for the noise. I have found out that this problem is  
related to "metered connections". On those ones, Emacs cannot trigger  
opening of the file and is not capable of returning the right error  
message. Once I disable the option "metered connection" from the  
network, Emacs operates as expected. I suspect this cannot really be  
attributed to Emacs, except for the lack of error message in the first  
situation.

Eli Zaretskii <eliz@gnu.org> escribió:

>> Date: Tue, 12 Jul 2022 15:46:40 +0200
>> From: Juan Jose Garcia Ripoll <juanjose.garcia.ripoll@csic.es>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 56499@debbugs.gnu.org
>>
>> 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.
>
> Does the problem only happen with files that are not downloaded from
> the cloud?  What if you tell OneDrive to download that file, then  
> tryagain -- does the problem go away then?
   Juan José García Ripoll

Instituto de Física Fundamental, CSIC
Calle Serrano 113b, Madrid 28006, Spain
Phone: (+34) 915616800 (dial 943107 when hearing the voice)
http://quinfog.iff.csic.es / http://juanjose.garciaripoll.com

[-- Attachment #2: Mensaje HTML --]
[-- Type: text/html, Size: 2313 bytes --]

  reply	other threads:[~2022-07-13  8:22 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 [this message]
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=20220713102209.Horde.2zgWs8EuCB8PAyQ_XunK-VF@webmail.csic.es \
    --to=juanjose.garcia.ripoll@csic.es \
    --cc=56499@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).