unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Olivier Certner <ocert.dev@free.fr>
Cc: 63072@debbugs.gnu.org
Subject: bug#63072: 28.2; CC Mode: Fix "bsd" style and add "freebsd" and "openbsd" ones
Date: Wed, 26 Apr 2023 13:31:56 +0300	[thread overview]
Message-ID: <83ttx3szmr.fsf@gnu.org> (raw)
In-Reply-To: <2661733.poxlI1A5LX@ravel> (message from Olivier Certner on Wed,  26 Apr 2023 11:31:28 +0200)

> From: Olivier Certner <ocert.dev@free.fr>
> Cc: 63072@debbugs.gnu.org
> Date: Wed, 26 Apr 2023 11:31:28 +0200
> 
> > > Additionally, these changes will be exceedingly rare, and styles will just
> > > be updated on a best-effort basis.
> > 
> > The "best-effort" part is what bothers me.  We introduce these new
> > styles because the relevant projects change the styles, and then we
> > basically tell users: don't expect these styles to actually follow
> > those projects, except by luck?  Does that make sense?
> 
> By luck? The last changes in these styles with a practical consequence for CC 
> mode were done more than 20 years ago. Had the changes proposed here been done 
> at that time, users would have been able to use the right style since then.
> 
> Truth is, users not having the right style would be extremely unlucky, given 
> the rate of changes (practically zero). These styles are *intended* to follow 
> these projects' practice. And they will so more than 99% of the time. Of 
> course, if a style changes and requires a CC style modification, then someone 
> will have to submit it and in the meantime users will have to live with the 
> discrepancy. Is that what really bothers you? That's what best effort means. 
> Again, this will be useful to the relevant users more than 99% of the time.

If the styles don't change in practice, then I'm okay with adding
them.  But then I wonder why you bothered to mention the fact that
they do change.





  reply	other threads:[~2023-04-26 10:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 17:49 bug#63072: 28.2; CC Mode: Fix "bsd" style and add "freebsd" and "openbsd" ones Olivier Certner
2023-04-25 18:03 ` Eli Zaretskii
2023-04-25 20:57   ` Olivier Certner
2023-04-26  5:50     ` Eli Zaretskii
2023-04-26  7:28       ` Olivier Certner
2023-04-26  9:13         ` Eli Zaretskii
2023-04-26  9:31           ` Olivier Certner
2023-04-26 10:31             ` Eli Zaretskii [this message]
2023-04-26 13:09               ` Olivier Certner
2023-04-26 13:32                 ` Eli Zaretskii
2023-04-26 13:53                   ` Olivier Certner
2023-04-26 16:07                     ` Eli Zaretskii
2023-09-05 16:01                       ` Stefan Kangas
2023-09-15 12:41                       ` Stefan Kangas
2023-09-19 16:15                         ` Olivier Certner
2023-09-21 15:22                           ` Stefan Kangas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ttx3szmr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63072@debbugs.gnu.org \
    --cc=ocert.dev@free.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).