[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input h
From: |
Stefan Kangas |
Subject: |
bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history |
Date: |
Fri, 5 Jan 2024 12:17:28 -0800 |
Simen Heggestøyl <simenheg@runbox.com> writes:
>>> +(defvar ielm--history-file-name
>>> + (locate-user-emacs-file "ielm-history.el")
>>
>> Shouldn't that be .eld?
>
> Hm, the file will contain actual Lisp expressions, so I'd think that .el
> is fitting?
I'm not so sure. We don't really intend for users to use it the way
you'd expect from an .el file, like byte-compiling or loading it.
So while these are, hopefully, valid Lisp expressions (barring typos,
which frequently happens at a REPL), it's not really a file containing
meaningful code either.
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history, Simen Heggestøyl, 2024/01/04
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history,
Stefan Kangas <=
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history, Simen Heggestøyl, 2024/01/08
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history, Stefan Kangas, 2024/01/08
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history, Simen Heggestøyl, 2024/01/12
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history, Stefan Kangas, 2024/01/13
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history, Simen Heggestøyl, 2024/01/19
- bug#67000: 30.0.50; [PATCH] Add support for reading/writing IELM input history, Stefan Kangas, 2024/01/28