unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Madhu <enometh@meer.net>
To: eliz@gnu.org
Cc: simenheg@runbox.com, emacs-devel@gnu.org
Subject: Re: ielm automatic saving of history -- bug 67000
Date: Sun, 13 Oct 2024 15:19:28 +0530 (IST)	[thread overview]
Message-ID: <20241013.151928.1926966009878393680.enometh@meer.net> (raw)
In-Reply-To: <86v7xwtu3i.fsf@gnu.org>

Hello,

*  Eli Zaretskii <eliz@gnu.org> <86v7xwtu3i.fsf@gnu.org>
Wrote on Sun, 13 Oct 2024 09:06:25 +0300
>> 2. The way to opt out of this is to set ielm-history-file-name to nil in
>> user customization.  In that case this code path should be avoided
>> altogether.
>
> If you do that, comint-write-input-ring is supposed to do nothing and
> return immediately.  Does that not happen?

It still interferes with any user customization, (e.g. the
my-ielm-mode-hook in the file attached upthread)

>> The "worst" problem happens when ielm buffer exits without running
>> kill-buffer-hook
>
> How can this happen? can you show a recipe for this?

(let (kill-buffer-hook (executing-kbd-macro 'kludge) buffer-file-name kill-buffer-query-functions) (kill-buffer "*ielm*")) -- used as outlined in the quoted portion below, to opt out of saving history for "this" particular ielm session.

I agree it is outside the design-scope of the current implementation,
but it does still hurt, -- Regards, Madhu

> ( -- historically I've used this pattern to avoid
>> saving history for a particular buffer, this is the way to opt out of
>> saving the history) but in this case it runs from the kill-emacs-hook,
>> and that forces me to choose a coding system to save the buffer. There
>> is no option to opt out.



  reply	other threads:[~2024-10-13  9:49 UTC|newest]

Thread overview: 15+ 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 [this message]
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-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=20241013.151928.1926966009878393680.enometh@meer.net \
    --to=enometh@meer.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=simenheg@runbox.com \
    /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).