From: Tassilo Horn <tsdh@gnu.org>
To: Steinar Bang <sb@dod.no>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Need assistance in figuring out what reformats my code on save
Date: Sun, 05 Sep 2021 20:43:43 +0200 [thread overview]
Message-ID: <87k0juc0y7.fsf@gnu.org> (raw)
In-Reply-To: <86wnnvl1kz.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
> Are there any other hooks that could be involved?
Maybe, although before-save-hook seems like a plausible candidate.
> Is there reformatting on save that don't use hooks?
You could use an advice but why would anyone do that given that there
are suitable hooks.
I'd try evaluating
(add-hook 'before-change-functions #'debug nil t)
in a buffer where that formatting before save happens and then save.
That should put you in the debugger and the backtrace will hopefully
show you who and from where the formatting is triggered.
HTH,
Tassilo
next prev parent reply other threads:[~2021-09-05 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 11:10 Need assistance in figuring out what reformats my code on save Steinar Bang
2021-09-05 18:43 ` Tassilo Horn [this message]
2021-09-06 14:26 ` Steinar Bang
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=87k0juc0y7.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=sb@dod.no \
/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.
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).