From: Lele Gaifax <lele@metapensiero.it>
To: help-gnu-emacs@gnu.org
Subject: Re: Temporarily disable a write hook?
Date: Fri, 14 Jul 2017 18:13:24 +0200 [thread overview]
Message-ID: <871spjuhcr.fsf@metapensiero.it> (raw)
In-Reply-To: CANc-5UwwJAF6iRQ7b_Hw3F8Ko7cA_HgFrv+zuNPeegw5KNpx8w@mail.gmail.com
I use https://github.com/purcell/whitespace-cleanup-mode, that mostly does the
right thing for me: it saves the trouble when I have to edit a source authored
by some less-picky-than-me on whitespace issues. When I really want to get rid
of trailing spaces, I do that explicitly, save and reload the buffer: from
then on, the mode above will keep it clean.
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
next prev parent reply other threads:[~2017-07-14 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 15:03 Temporarily disable a write hook? Skip Montanaro
2017-07-14 15:11 ` Yuri Khan
2017-07-14 15:43 ` Skip Montanaro
2017-07-14 16:13 ` Lele Gaifax [this message]
2017-07-14 17:29 ` Skip Montanaro
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=871spjuhcr.fsf@metapensiero.it \
--to=lele@metapensiero.it \
--cc=help-gnu-emacs@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.
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).