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.devel Subject: Re: ielm automatic saving of history -- bug 67000 Date: Thu, 31 Oct 2024 13:13:45 +0200 Message-ID: <86h68s34pi.fsf@gnu.org> References: <865xpsr3b0.fsf@gnu.org> <20241016.143359.2067752235306528118.enometh@meer.net> <86jze7q4io.fsf@gnu.org> <20241031.161205.384163890653085993.enometh@meer.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19567"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Madhu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 31 12:14:38 2024 Return-path: Envelope-to: ged-emacs-devel@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 1t6T8Q-0004wT-H2 for ged-emacs-devel@m.gmane-mx.org; Thu, 31 Oct 2024 12:14:38 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t6T7f-0006bv-Dx; Thu, 31 Oct 2024 07:13:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t6T7d-0006bc-Bk for emacs-devel@gnu.org; Thu, 31 Oct 2024 07:13:49 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t6T7d-0003td-0T; Thu, 31 Oct 2024 07:13:49 -0400 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=UIXO3+X+UPrQEYKELUYqVYlY6UVJC1yER9mOSos0VZ8=; b=ATCdDlnYPRzN NYMPrMh+hOf/X0OAqv9i41UHE9H5g8St4vbhuJ4cDYwc7pocmYN2kaqCJR44v7BUtdAVzaXT2Fz2j zM4w5yFwFX3viHpnDxwjhvWPk7XSuonqsrTCWi9l/hdODPk+2dcm0nsU7mB/sjL/p2M93iOXp3G9a 4NKoGIbK6Vg2EkqGqwRGW2s8B9+vyHpS+eujEDMrzZYG9JFiXvg0vZqtl7CU9QlNt2tgHkeC3uTsN ghYUSggW840U9Yx2WgxqbargOSAuRo/lfCLsqaR5Og7NmXaCQqBtLqVP8Dr2cZO0IVCK6uB5U20Uv r4jk4z/ZuChDHAT264I+ow==; In-Reply-To: <20241031.161205.384163890653085993.enometh@meer.net> (message from Madhu on Thu, 31 Oct 2024 16:12:05 +0530 (IST)) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:324964 Archived-At: > Date: Thu, 31 Oct 2024 16:12:05 +0530 (IST) > Cc: emacs-devel@gnu.org > From: Madhu > > * Eli Zaretskii <86jze7q4io.fsf@gnu.org> > Wrote on Wed, 16 Oct 2024 21:36:15 +0300 > >> the ielm-history file from which the comint-input-ring is initalized > > > > That's not what bothers me. What bothers me is the way we save the > > history of the ielm command the first time, when they are not taken > > from a file, but from the user input. > > > >> Here I am prompted with the coding system warning . If i go ahead > >> and qchoose utf-8-unix, it goes ahead and saves it. I can compare > >> 2.txt.binary and 2.txt.out to see that utf-8-unix has not resulted > >> in any data loss. Hence all the claims in my previous message. > > > > The data loss I had in mind is not in this case. > > I still think there is some fishy behaviour when raw-text-unix is used > by as the initial (unspecified) encoding. The message which the > prompt presents (that utf-8-unix cannot be used to save etc.) is > surely incorrect, since it goes ahead and saves it anyway as > utf-8-unix. The explanation presented when Emacs requests a safe encoding was worded in a way that could be interpreted to mean the text cannot possibly be encoded bu utf-8. The reality is subtly different: utf-8 cannot encode that _safely_, but it can encode it with some data loss if forced to do so. I have modified the wording to say "safely encode", to make that part more explicit. > BTW did you have a chance to consider the patch I mailed on > oct-17-2024? -- Regards, madhu No, I hoped Simen will get to that at some point.