From: Eli Zaretskii <eliz@gnu.org>
To: lemue301171@freenet.de
Cc: 46293@debbugs.gnu.org
Subject: bug#46293: Windows 10: emacs freeze on kill emacs
Date: Thu, 04 Feb 2021 17:21:07 +0200 [thread overview]
Message-ID: <83pn1frh98.fsf@gnu.org> (raw)
In-Reply-To: <0e5dd81bfb0f6d86655dbff8b0ebffba@api.mail.freenet.de> (lemue301171@freenet.de)
> Date: Thu, 04 Feb 2021 10:00:55 GMT
> From: lemue301171@freenet.de
>
> If an file name is used, which is obviously invalid for some operations,
> the following can happen:
> 1. The file gets opened anyway, although an error message states
> otherwise:
> - File exists, but cannot be read
> - File mode specification error: (file-error Unlocking file Invalid argument
> //collaboration.dummyname.com@SSL/DavWWWRoot/subjects/foo bar.docx)
> 2. Trying to close the buffer triggers simmilar errors
> 3. Trying to exit emacs leads to a question wheter the file shall be saved.
> - Selecing No now again leads to similar error message, but now emacs also freezes (is unresponsive and
> GUI is no longer updated).
> - Emacs must be killed via task-manager.
Thanks, but we need a more concrete test case to see what happens in
these cases and how to fix that. Could you please provide a full
detailed recipe to reproduce this starting from "emacs -Q"?
next prev parent reply other threads:[~2021-02-04 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 10:00 bug#46293: Windows 10: emacs freeze on kill emacs lemue301171
2021-02-04 15:21 ` Eli Zaretskii [this message]
2021-02-07 14:13 ` Frank Roland
2021-02-07 15:32 ` Eli Zaretskii
2021-05-16 14:33 ` Lars Ingebrigtsen
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=83pn1frh98.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46293@debbugs.gnu.org \
--cc=lemue301171@freenet.de \
/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).