From: Madhu <enometh@meer.net>
To: eliz@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: ielm automatic saving of history -- bug 67000
Date: Thu, 31 Oct 2024 16:12:05 +0530 (IST) [thread overview]
Message-ID: <20241031.161205.384163890653085993.enometh@meer.net> (raw)
In-Reply-To: <86jze7q4io.fsf@gnu.org>
* 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.
BTW did you have a chance to consider the patch I mailed on
oct-17-2024? -- Regards, madhu
next prev parent reply other threads:[~2024-10-31 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 4:17 ielm automatic saving of history -- bug 67000 Madhu
2024-10-13 6:06 ` Eli Zaretskii
2024-10-13 9:49 ` Madhu
2024-10-14 6:23 ` Augusto Stoffel
2024-10-14 14:05 ` Eli Zaretskii
2024-10-15 4:46 ` Madhu
2024-10-15 12:18 ` Eli Zaretskii
2024-10-15 17:30 ` Madhu
2024-10-15 18:23 ` Eli Zaretskii
2024-10-16 4:25 ` Madhu
2024-10-16 6:04 ` Eli Zaretskii
2024-10-16 9:03 ` Madhu
2024-10-16 18:36 ` Eli Zaretskii
2024-10-31 10:42 ` Madhu [this message]
2024-10-31 11:13 ` Eli Zaretskii
2024-10-16 17:02 ` Simen Heggestøyl
2024-10-17 2:04 ` Madhu
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=20241031.161205.384163890653085993.enometh@meer.net \
--to=enometh@meer.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).