From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikita Karetnikov Subject: Re: [PATCH 0/2] Add tools for sysadmins: htop and dfc. Date: Sat, 31 Aug 2013 01:52:39 +0400 Message-ID: <87sixqluc8.fsf@karetnikov.org> References: <1377893316-5136-1-git-send-email-tipecaml@gmail.com> <877gf2nbej.fsf@karetnikov.org> <52210294.5060202@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33820) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFWY9-0002Hr-F9 for guix-devel@gnu.org; Fri, 30 Aug 2013 17:48:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VFWY5-000671-Sg for guix-devel@gnu.org; Fri, 30 Aug 2013 17:48:13 -0400 Received: from [2a01:7e00::f03c:91ff:fedf:181] (port=50767 helo=cooksoni.karetnikov.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFWY5-00066h-M5 for guix-devel@gnu.org; Fri, 30 Aug 2013 17:48:09 -0400 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Cyril Roelandt Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > Yes. I never know what to do in such cases. Is there a document that > contains these coding-style rules, such as the PEP8 for Python ? The pretty-printing rule is described in SICP. Search for =E2=80=9CThere i= s no limit=E2=80=9D [1]. However, that paragraph doesn=E2=80=99t say what to do= when the line is too long. I=E2=80=99m trying to keep lines under 79 characters (as suggested in PEP8)= . It allows =E2=80=9Cto have several files open side-by-side, and works well when using code review tools that present the two versions in adjacent columns=E2=80=9D [2]. I also find that short lines are easier to read. I believe it=E2=80=99s OK to write (proc very-very-very-very-very-very-long-argument a b c) instead of (proc very-very-very-very-very-very-long-argument a b c) because this allows to display more lines on the screen. Also, it may be a good idea to write (very-long-procedure1 argument1 (very-long-procedure2 argument2 (very-long-procedure3 argument3 (...)))) instead of (very-long-procedure1 argument1 (very-long-procedure2 argument2 (very-long-procedure3 argument3 (...)))) That said, you have to break the rules sometimes. Should we mention this in the =E2=80=9Cpackaging rules=E2=80=9D section? [1] https://mitpress.mit.edu/sicp/full-text/book/book-Z-H-10.html#%_sec_1.1= .1 [2] http://www.python.org/dev/peps/pep-0008/#maximum-line-length --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJSIRQqAAoJEM+IQzI9IQ38UjcP+wQYnhyJEgAi4Dh4eU8azU1N aiocteKOSB1xH9294M+ZBOwJpsyOlewKS6gJFjqcQzA4GE/yNesgjh9ooDFNtczT T/S+rQw+y41PFTK47+ORGcJKomHqyek5HVxamD9yoSrnyPKklWA83RiwJ5bgLFfw 8XxEWQnzfWx+slOBoB4XT6qZR2MHoD1sT1CIZR782tidqkCf9RnICXjnQXzu02wU G32nwczgQxSzqKh8wFW+Pv2tsghiSK1iCaVLTMLtcj0qB/zCxjOm3jq5BcJhX7Ov 83W+so8PaAnI9DiZIPM+F0SyrRJOhXmNCfIcndkzm67Ktb08EO1lupWp57ALkAqZ MRc9bu4s2J6Nolr3yDuFQonltGUOcp8fShkNKJ6ELcp7IoyGC68om35CihCZql/Q 75oo0hWhQ79bflG0D8ovQ2nW1rkK2y395NnoSC7mJogrAwHaWTrepEjE6i/IEXk7 VHyuCuODdqifRSMo/uxYtSo8ektTLl10UT8pYCLbjwQFzipJMqCBPBK0vWarEQ6P k9gj27yqB6XPjH1hfVN/O5UMNya9Rt95Y9ODGKSx/3TVmR3+R5BjxP7c9DKdvqIk ybyTuyVNsERf1bvACDuQR9fUR/FzfQ3hf+z9Qpni/0tgt7IhkUZrTyW7NphrmihA 3Xq1umesqCnAEndOTHVv =E6iM -----END PGP SIGNATURE----- --=-=-=--