From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: rfc: (add-hook 'before-save-hook 'delete-trailing-whitespace)
Date: Sat, 23 Jan 2010 17:10:50 +0100 [thread overview]
Message-ID: <87iqasvm2d.fsf@gnu.org> (raw)
In-Reply-To: 87636tr6yh.fsf@ambire.localdomain
Hi,
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> Revised proposal: Let's decide one way or the other,
To me it’s clear: status quo, i.e., no ‘whitespace-cleanup’ or similar
all around, but encourage people not to leave trailing whitespace.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-01-23 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 9:06 rfc: (add-hook 'before-save-hook 'delete-trailing-whitespace) Thien-Thi Nguyen
2010-01-13 10:53 ` Ludovic Courtès
2010-01-13 14:22 ` Thien-Thi Nguyen
2010-01-21 20:31 ` Neil Jerram
2010-01-21 20:44 ` Ludovic Courtès
2010-01-13 20:02 ` Andy Wingo
2010-01-13 20:45 ` Thien-Thi Nguyen
2010-01-14 0:10 ` Ludovic Courtès
2010-01-21 20:46 ` Neil Jerram
2010-01-23 0:38 ` Thien-Thi Nguyen
2010-01-23 16:10 ` Ludovic Courtès [this message]
2010-02-09 13:30 ` Thien-Thi Nguyen
2010-02-14 14:20 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iqasvm2d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).