unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: philipk@posteo.net,  emacs-devel@gnu.org
Subject: Re: [ELPA] new single file package: mpdired.el
Date: Mon, 11 Mar 2024 09:44:47 +0100	[thread overview]
Message-ID: <87plw188e8.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <86r0ghvqjs.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Mar 2024 21:24:07 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
>> Date: Sun, 10 Mar 2024 19:03:56 +0100
>> From:  Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
>> > I have tried to do so but for whatever reason this completely messes up
>> > the way I'm saving state in buffer local variables.  FWIW, I have tried
>> > with parent as nil and special-mode with the same result.
>> 
>> It seems to be because `define-derived-mode' calls
>> `kill-all-local-variables' (line 254 of derived.el).  Maybe this could
>> be optional.  WDYT?
>
> How can we NOT kill all local variables when we are turning on a major
> mode?

Yes.  Thinking about it, it seems that my usage of a major mode is wrong
here.  I thing it should be activated in only *one* place whatever I do
with the buffer content afterward.  Thanks.
-- 
Manuel Giraud



      reply	other threads:[~2024-03-11  8:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  9:26 [ELPA] new single file package: mpdired.el Manuel Giraud via Emacs development discussions.
2024-03-08 10:25 ` Philip Kaludercic
2024-03-08 11:17   ` Manuel Giraud via Emacs development discussions.
2024-03-08 11:26     ` Philip Kaludercic
2024-03-08 12:22       ` Manuel Giraud via Emacs development discussions.
2024-03-08 13:18         ` Philip Kaludercic
2024-03-08 16:25           ` Manuel Giraud via Emacs development discussions.
2024-03-08 16:34             ` Philip Kaludercic
2024-03-08 17:06               ` Manuel Giraud via Emacs development discussions.
2024-03-08 17:29                 ` Philip Kaludercic
2024-03-09 13:18                   ` Manuel Giraud via Emacs development discussions.
2024-03-09 13:36                     ` Philip Kaludercic
2024-03-10 16:00                       ` Manuel Giraud via Emacs development discussions.
2024-03-10 17:03                         ` Philip Kaludercic
2024-03-10 17:43                           ` Manuel Giraud via Emacs development discussions.
2024-03-10 17:49   ` Manuel Giraud via Emacs development discussions.
2024-03-10 18:03     ` Manuel Giraud via Emacs development discussions.
2024-03-10 18:15       ` Philip Kaludercic
2024-03-10 19:24       ` Eli Zaretskii
2024-03-11  8:44         ` Manuel Giraud via Emacs development discussions. [this message]

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=87plw188e8.fsf@ledu-giraud.fr \
    --to=emacs-devel@gnu.org \
    --cc=eliz@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=philipk@posteo.net \
    /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).