[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] emacs-25 b6d6304: Comment on last change to define-der

From: John Wiegley
Subject: Re: [Emacs-diffs] emacs-25 b6d6304: Comment on last change to define-derived-mode
Date: Mon, 07 Mar 2016 07:44:50 -0800
User-agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.0.92 (darwin)

>>>>> Oleh Krehel <address@hidden> writes:

> Like I said, it's up to you to decide what to do. You've already shown favor
> to the testing and bug-squashing directions for the Emacs development.
> In my opinion, the coding style could be another useful direction.

I do think coding style can be of value, but I'd rate it at far lower
importance than testing and bug-squashing. The reason being that improving
tests and reducing bugs benefits all of our users, while coding styles mostly
benefit the people on this list.

> - Removing the ambiguity about `indent-tabs-mode'.

What is the ambiguity?

> - Working on something like `pretty-print-buffer': a command to
> automatically eliminate hanging parens, consecutive spaces, multi-variable
> `setq'; and re-indent everything.

This could be quite nice!

> - Extending the checkdoc to find more warnings in the code style, like
> unresolved declarations etc.


> - Formalizing the C code style, tutorials, contribution guidelines etc.
> Maybe we could have a linter for C.


> I think it would be great if at some moment we could stop thinking how a
> code looks, and only think about what it does. And ignoring how it looks
> isn't really a great solution - it may work for some, doesn't work for me at
> the moment.

Personally I'd love that too. I'd just rather see the bugs under much better
control before putting too much energy in this direction, as its likely to
generate a lot of debate.

John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

reply via email to

[Prev in Thread] Current Thread [Next in Thread]