From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Changing line widths in the Emacs source code Date: Sun, 13 Sep 2020 08:09:40 -0700 Message-ID: References: <87tuw1x016.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14831"; mail-complaints-to="usenet@ciao.gmane.io" To: =?UTF-8?Q?Daniel_Mart=C3=ADn?= , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Sep 13 17:12:25 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kHTg0-0003l2-WC for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Sep 2020 17:12:24 +0200 Original-Received: from localhost ([::1]:36452 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kHTg0-0000S3-0m for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Sep 2020 11:12:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45352) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kHTdR-0006YG-8r for emacs-devel@gnu.org; Sun, 13 Sep 2020 11:09:46 -0400 Original-Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]:35980) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kHTdO-0002es-Vi for emacs-devel@gnu.org; Sun, 13 Sep 2020 11:09:44 -0400 Original-Received: by mail-ej1-x633.google.com with SMTP id e23so19725120eja.3 for ; Sun, 13 Sep 2020 08:09:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :content-transfer-encoding; bh=uiKMdIeZzZ9JomInEAzFTtcV5ibDYJqk/f3nQQjKNwI=; b=SUcpIFljesNjqW9rCV+ipFbLsMwCL3QGwywPLx3hYe86pOzrxEUOFkqCThcZaTo2ND zHEizQ4VXL+ILWeubmdKwbwbA1Ch0/iGQ8WTfnUpv7wfexaJu0Ixpl8vzboe9kKkbunJ 2Ry0NcWcc9p/jAb3hBfqQ33ssovjXZ8qW892iEKkNv4Q59zObUtcmqSvPVppmm1MkgK1 2ms0OsIziGKDvBXEME/s3cUtM6mi2PP00BEgr+hk+3x7g5ol0jZ+e74wgst+0tiDpD0e kNfAlN2P4GPPoAHAmTP+YFEF8ty2Jrcjkc4CkrCWf4UrhyaGy6x66SAsL8h/8GnG3LTi NE+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:content-transfer-encoding; bh=uiKMdIeZzZ9JomInEAzFTtcV5ibDYJqk/f3nQQjKNwI=; b=L/Kf3pEFlEUuA6WMCR/4Mnb0jgFk5ZThA/FWGlKrIW3zdHLjTkYqx34HDR+n+RHn8g Y7wTeMkIPpMnwPyKv05YAQiouOzDhC1DxM6VHGsp90vf5W1WUxZKUQzUYh50vPcOsgej fidz6MP56hD0NtTe2Tl6VuaHq8tfd//f+6vlULnuz/2y6BdD0ps/RxUfxERvj6LfEU+H AYrqzbnaBUFANYC092fdzgiz9Pu2KzmPQbCavPp//GKxY5rXUKolQGcWb5wHOWKOtjY4 lCJiOafE3en6AiBvYsisAwJ+f19rtEbX1PM7J7iJCX95zvS1A1M+PaURhs7zdRRR6WW+ hORA== X-Gm-Message-State: AOAM5301RsFKF79z22dvsELS3wUPeUAwHzVbanuhdGjBrMv5F94mMQ+6 Sgm0J6joR4UIYZudP0Tj12iiv7huM1WV6NHGq6E= X-Google-Smtp-Source: ABdhPJzvclGr1Tt2kGVkXd9KWee5O2A9kg6Y9a8V0ItBTOoHDgW7RaswmsZXR3L7/Ny9ZL7cOLRcPjjWyGcVI+1zaXY= X-Received: by 2002:a17:906:b146:: with SMTP id bt6mr10421403ejb.287.1600009781297; Sun, 13 Sep 2020 08:09:41 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sun, 13 Sep 2020 08:09:40 -0700 In-Reply-To: Received-SPF: pass client-ip=2a00:1450:4864:20::633; envelope-from=stefankangas@gmail.com; helo=mail-ej1-x633.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:255503 Archived-At: Daniel Mart=C3=ADn writes: > If the existing code won't change, then we will have parts of the > codebase with a different style than others. The goal of having a code > style is not much about the individual decisions, but about > consistency. What you say seems to imply that we can never change a stylistic convention until someone produces a patch that fixes the entire source tree to use it. Maybe there is something in your argument that I don't understand. AFAIU, with a new convention code would slowly change over time. > Also, what would happen if you change code in an existing file? Would > you need to fit it in 80 columns, 100 columns? Our .clang-format file > would format the code using 100 columns, so it'll probably do the wrong > thing by default. You would apply the new convention judiciously, just like you would do today with the old one. It's not like the current convention is enforced strictly, and there are already examples when it's not being followed.