From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: removing white space highlight
Date: Fri, 26 Feb 2016 04:29:59 +0100 [thread overview]
Message-ID: <87ziuokv2g.fsf@debian.uxu> (raw)
In-Reply-To: 87io1cuqhx.fsf@robertthorpeconsulting.com
Robert Thorpe <rt@robertthorpeconsulting.com> writes:
>> I'll be like that once for every file.
>
> Yes, for decades.
Are there so really so many files that are left
untouched for so long?
Why can't you do it once for all files?
Or, by all means, do it as it goes along. It should
only happen when a file is edited or added. If it is,
all the better: it is forever fixed. If it isn't
edited this isn't an issue as nothing will
happen anyway.
> That's far too high a price to pay for being
> perfectionist about whitespace.
Being a perfectionist in the negative sense is
spending too much time on stuff that doesn't mean
anything, really, and/or being neurotic about it.
This discussion for example is perhaps closing in on
that :)
However not wanting to have trailing whitespace and
having it automatized in four lines of Elisp and then
have the desired behavior forever seems like rather
good craftmanship to me...
> I don't think you understand how useful blaming is
> to people who do maintenance programing.
If this is automatized like I've described the issue
should forever be removed from the realm of humans.
Only the machines will know about it before long...
But I'm fine ending the discussion. I'm not
maintaining any cooperative software anyway and
I don't plan to, ever. I'm a solo climber. When there
is one person, he knows where the rope is. When there
is twenty everyone subconsciously relax and suddenly
at the attack camp there is a bottleneck and the guy
first in line says: "Where is the gear? Where is
the equipment?" Uh-oh!
I know where my rope is - here:
;; (setq before-save-hook nil)
(defun before-save-hook-f ()
(delete-trailing-whitespace) )
(setq before-save-hook #'before-save-hook-f)
:)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2016-02-26 3:29 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 10:06 removing white space highlight Luca Ferrari
2016-02-18 10:19 ` Gian Uberto Lauri
2016-02-18 10:54 ` Luca Ferrari
2016-02-18 10:30 ` tomas
2016-02-18 13:34 ` Luca Ferrari
2016-02-18 13:17 ` tomas
2016-02-18 14:37 ` Luca Ferrari
2016-02-18 14:15 ` tomas
2016-02-18 16:08 ` Luca Ferrari
2016-02-19 0:23 ` Emanuel Berg
2016-02-19 1:05 ` Drew Adams
2016-02-19 16:02 ` Marcin Borkowski
2016-02-19 20:43 ` Emanuel Berg
2016-02-19 20:50 ` Marcin Borkowski
2016-02-20 0:30 ` Emanuel Berg
2016-02-20 19:08 ` Bob Proulx
2016-02-21 0:32 ` Emanuel Berg
2016-02-21 1:34 ` Bob Proulx
2016-02-21 1:48 ` Emanuel Berg
2016-02-21 3:27 ` Robert Thorpe
2016-02-21 3:31 ` Emanuel Berg
2016-02-21 5:00 ` Marcin Borkowski
2016-02-21 6:10 ` Emanuel Berg
2016-02-21 11:48 ` tomas
2016-02-21 17:13 ` Emanuel Berg
2016-02-23 0:33 ` Robert Thorpe
2016-02-23 0:41 ` Emanuel Berg
2016-02-24 0:44 ` Robert Thorpe
2016-02-24 1:41 ` Emanuel Berg
2016-02-24 20:38 ` Robert Thorpe
2016-02-25 0:10 ` Emanuel Berg
2016-02-25 8:47 ` Luca Ferrari
2016-02-25 9:29 ` Christian Kruse
2016-02-25 19:58 ` Robert Thorpe
2016-02-25 20:10 ` vc-region-history promotion (was: removing white space highlight) Stefan Monnier
2016-02-25 22:15 ` removing white space highlight Emanuel Berg
2016-02-25 22:41 ` Robert Thorpe
2016-02-26 0:02 ` Emanuel Berg
2016-02-26 2:58 ` Robert Thorpe
2016-02-26 3:29 ` Emanuel Berg [this message]
2016-02-26 6:08 ` Bob Proulx
2016-02-26 19:48 ` Emanuel Berg
2016-02-27 20:54 ` Robert Thorpe
2016-02-28 2:43 ` Emanuel Berg
2016-02-28 18:09 ` Robert Thorpe
2016-02-29 0:52 ` Emanuel Berg
2016-02-29 2:43 ` Robert Thorpe
2016-02-22 14:05 ` Luca Ferrari
2016-02-23 0:13 ` Emanuel Berg
2016-02-23 0:34 ` Robert Thorpe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ziuokv2g.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.