unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Olivier Certner <ocert.dev@free.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63072@debbugs.gnu.org
Subject: bug#63072: 28.2; CC Mode: Fix "bsd" style and add "freebsd" and "openbsd" ones
Date: Tue, 25 Apr 2023 22:57:29 +0200	[thread overview]
Message-ID: <4964691.nKnxuYGXMN@ravel> (raw)
In-Reply-To: <83fs8nvnz6.fsf@gnu.org>

> ENOPATCH,

Yes. See end of initial message + was temporarily distracted.

> but in any case, I don't think we can change a style that
> was in use for such a long time.  So I suggest instead to create a new
> style, say bsd2 or somesuch.

That may be a problem, not so much for the ancient "bsd", but for the new 
ones.

After more reading, it seems that this "bsd" is in fact Allman's style, which 
indeed differs for the style used by BSD projects. So, I'm pondering with 
using "bsd-knf" instead (for Kernel Normal Form), which appears to be the 
dedicated term (and is even documented in Wikipedia).

What I intend to do with "freebsd" and "openbsd" is to have styles reflecting 
the current practice for these projects. Which means they can (in fact, most 
probably will) be changed in the future according to how they amend their 
style guidelines. If this policy of changes is documented, is that OK?

For those who want to use the current style for whatever project they have and 
don't want it to change afterwards, we could, e.g., make "freebsd" an alias of 
some "freebsd1" style (let's say, for version 1), and they would "freebsd1", 
i.e., a specific version that will not change. I'm not sure if this will be 
useful for some people, but at least it is cheap to do so we should probably 
do it even if in the end nobody would use it.

I think I need a little bit more reading and pondering (and your answers) 
before I can actually submit meaningful patches. (So the interruption might 
have been a blessing.)

Thanks.

-- 
Olivier Certner







  reply	other threads:[~2023-04-25 20:57 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 [this message]
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
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=4964691.nKnxuYGXMN@ravel \
    --to=ocert.dev@free.fr \
    --cc=63072@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).