From: "Phillip Lord" <phillip.lord@russet.org.uk>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Reformat all of src/
Date: Wed, 28 Dec 2016 17:35:15 -0000 [thread overview]
Message-ID: <c490170b1bc6413e907a294c4f42f722.squirrel@cloud103.planethippo.com> (raw)
In-Reply-To: <jwvzijg3rcz.fsf-monnier+gmane.emacs.devel@gnu.org>
On Wed, December 28, 2016 5:19 pm, Stefan Monnier wrote:
>> I notice whether indentation is made from tabs, spaces or a mix because
>> I
>> use whitespace.el to highlight them (and some other whitespace
>
> That's one example of "something wrong".
>
>
> There might be cases where the difference is important and it's hence
> valuable to use whitespace.el to help you avoid problems, but your life
> will be more pleasant when you stop worrying about those details when
> they don't matter.
Probably true. I switched whitespace on, because I noticed in my own
projects that my whitespace handling was very messy and this caused
diffing issues. I just never got around to fiddling with my whitespace.el
configuration to switch it off for Emacs. Probably never will, now;
wouldn't recognize Emacs source without the occasional fluorescent yellow
tab, which is the colour I use.
It doesn't both me overly, although to stop worrying about details which
are not important, you have to know which ones are important. You've
corrected my patches for indentation several times (which I've always been
grateful for). Some projects are extremely picky on whitespace.
Hence, my conclusion: if tooling support could be added to incrementally
approach convergence, that would not be a bad thing. But it's not worth
worrying about excessively.
I will leave it there!
Phil
next prev parent reply other threads:[~2016-12-28 17:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 0:59 Reformat all of src/ Chris Gregory
2016-12-28 3:43 ` Stefan Monnier
2016-12-28 4:45 ` John Wiegley
2016-12-28 4:52 ` Chris Gregory
2016-12-28 5:01 ` Chris Gregory
2016-12-28 12:58 ` Phillip Lord
2016-12-28 15:35 ` John Yates
2016-12-28 15:39 ` Lars Ingebrigtsen
2016-12-28 16:01 ` John Yates
2016-12-28 16:27 ` Lars Ingebrigtsen
2016-12-28 16:17 ` Phillip Lord
2016-12-28 17:19 ` Stefan Monnier
2016-12-28 17:35 ` Phillip Lord [this message]
2016-12-28 17:52 ` Stefan Monnier
2016-12-28 17:59 ` Eli Zaretskii
2016-12-28 16:32 ` Yuri Khan
2016-12-28 16:37 ` Lars Ingebrigtsen
2016-12-28 16:56 ` Yuri Khan
2016-12-28 16:59 ` John Wiegley
2016-12-28 17:12 ` Yuri Khan
2016-12-28 17:20 ` Phillip Lord
2016-12-28 18:38 ` Paul Eggert
2016-12-29 1:10 ` Dmitry Gutov
2016-12-29 5:53 ` Paul Eggert
2016-12-29 11:28 ` Dmitry Gutov
2016-12-30 1:07 ` Paul Eggert
2016-12-30 10:34 ` Phillip Lord
2017-01-01 1:14 ` Dmitry Gutov
2016-12-29 13:18 ` Phillip Lord
2016-12-29 16:17 ` Eli Zaretskii
2016-12-29 17:18 ` John Covici
2016-12-29 17:19 ` John Covici
2016-12-30 10:30 ` Phillip Lord
2016-12-28 17:23 ` John Yates
2016-12-31 10:23 ` Philippe Vaucher
2016-12-29 1:36 ` Richard Stallman
2016-12-29 3:41 ` Eli Zaretskii
2016-12-29 12:04 ` Tino Calancha
2016-12-29 16:15 ` Eli Zaretskii
2016-12-30 0:09 ` Richard Stallman
2016-12-30 8:21 ` Eli Zaretskii
2016-12-29 14:39 ` Stefan Monnier
2016-12-28 10:27 ` hector
-- strict thread matches above, loose matches on Subject: below --
2016-12-29 2:08 Chris Gregory
2016-12-29 3:38 ` Eli Zaretskii
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=c490170b1bc6413e907a294c4f42f722.squirrel@cloud103.planethippo.com \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.