From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#51883: 29.0.50; Command to get accidentally deleted frames back Date: Mon, 17 Jan 2022 15:00:35 +0200 Message-ID: <83mtjuwm8c.fsf@gnu.org> References: <87czn1gfb1.fsf@web.de> <83fsrhztvn.fsf@gnu.org> <87lf19g529.fsf@web.de> <838rx9zs9r.fsf@gnu.org> <87h7bxg2d8.fsf@web.de> <835ysdzq4s.fsf@gnu.org> <87czmlg1rz.fsf@web.de> <227d35a5bc25a5f57453@heytings.org> <87zgppekxe.fsf@web.de> <227d35a5bcdae0a85f4d@heytings.org> <87v90dekii.fsf@web.de> <227d35a5bc14f7b3c75c@heytings.org> <87r1b1ejif.fsf@web.de> <227d35a5bc16d5c159ac@heytings.org> <87fsrg8ep4.fsf@web.de> <87bl22n7ut.fsf@web.de> <877dcqn5kx.fsf@web.de> <86h7bur9yi.fsf@mail.linkov.net> <864k68ujbx.fsf@mail.linkov.net> <861r1aoi9i.fsf@mail.linkov.net> <867daz1jo1.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7479"; mail-complaints-to="usenet@ciao.gmane.io" Cc: michael_heerdegen@web.de, gregory@heytings.org, 51883@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 17 15:00:05 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9SYH-0001o2-1e for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 17 Jan 2022 15:00:05 +0100 Original-Received: from localhost ([::1]:54218 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n9SYG-0007eJ-1Y for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 17 Jan 2022 09:00:04 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33146) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9Rd8-0002sc-Jj for bug-gnu-emacs@gnu.org; Mon, 17 Jan 2022 08:01:10 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52042) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n9Rd8-0004ae-7I for bug-gnu-emacs@gnu.org; Mon, 17 Jan 2022 08:01:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1n9Rd8-00043V-7I for bug-gnu-emacs@gnu.org; Mon, 17 Jan 2022 08:01:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 17 Jan 2022 13:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51883 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 51883-submit@debbugs.gnu.org id=B51883.164242445615569 (code B ref 51883); Mon, 17 Jan 2022 13:01:02 +0000 Original-Received: (at 51883) by debbugs.gnu.org; 17 Jan 2022 13:00:56 +0000 Original-Received: from localhost ([127.0.0.1]:44945 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n9Rd1-000433-Td for submit@debbugs.gnu.org; Mon, 17 Jan 2022 08:00:56 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60558) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n9Rcz-00042p-CB for 51883@debbugs.gnu.org; Mon, 17 Jan 2022 08:00:54 -0500 Original-Received: from [2001:470:142:3::e] (port=36442 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9Rct-0004YZ-EZ; Mon, 17 Jan 2022 08:00:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=RJrMMKHUo45NflbSAUYHpgdyZy6NdMwZxyrq79GU8so=; b=dLqwut7Huc0j QaseWRawHogF1g+KAw/ecEgplrHN13mgW+uGN5IelvjPf3aGcgbHSpYUHswZgfq4iafH66dtQiuhw 5lxJd1dQMqYiCWA1j7iwvJHKbPYcHOAxntY5t64PuZzs3zY/C/OT7Iea+D+Lb27lFwltodaVDIFNF uEpuNMtamjOVVJCxACJG/L5CMubaFhQGZ0uyMTAVjsbO4BWjhWCv1AbgXih7b5fYJ9YrccbHxVzUS RiTH0lSPWTzhFyhtc4+heQH32iasogPpR9wW8nQvXgbfEojpMdGBUsIeifBEUCQTscKY7qzmWVgt5 ivO72d4RPAcDKsMLxzA46Q==; Original-Received: from [87.69.77.57] (port=3136 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9Rcr-0003F6-St; Mon, 17 Jan 2022 08:00:46 -0500 In-Reply-To: <867daz1jo1.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 16 Jan 2022 22:59:20 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:224441 Archived-At: > From: Juri Linkov > Date: Sun, 16 Jan 2022 22:59:20 +0200 > Cc: Gregory Heytings , 51883@debbugs.gnu.org > > close 51883 29.0.50 > quit > > > I tried to use this, but undelete-frame-mode in the File menu > > makes no sense: when you mistakenly deleted a frame, you want > > to undelete it immediately, so you open the File menu, and > > see the message "No way, you can't undelete the deleted frame, > > because you were careless and not enabled a special mode". > > > > So the most useful case for this feature is to get the > > accidentally deleted frame back, and it fails to do this. > > > > Instead, it allows undeleting 16 frames in a special mode. > > Is there really a human that can delete 16 frames, and then > > remember what was on the 16th frame back? > > > > Rereading this thread indicates that the only concern about > > enabling this by default was the memory footprint for remembering > > 16 frames. OTOH, this feature is really useful for remembering > > 1 frame. So this is what should be enabled by default: > > It seems this is the right thing to do, so now pushed to master. I'm sorry, you cannot do that. We discussed this at some length and reached certain conclusions. Then you come and in effect say those considerations and discussions make no sense, and you know better? Let's please respect our discussions and decisions more than that. And if you want others to respect your opinions, please respect theirs, even if you disagree. The feature as installed allows you to customize it to have that mode turned on by default, so you could easily fix your problem by doing that. Specifically to your main argument: it is no different from deleting a file: unless the user took steps to configure the system to allow undeleting deleted files, deleted files are lost forever. Moreover, in the case of an Emacs frame, nothing of terrible importance is actually lost: the buffers displayed in that frame are still there, and restoring the deleted frame by hand shouldn't take more than a few moments. So I reverted this changeset. Please in the future don't make such changes unilaterally.