From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Changing line widths in the Emacs source code
Date: Sun, 13 Sep 2020 17:01:02 +0200 [thread overview]
Message-ID: <877dsxlo0h.fsf@gnus.org> (raw)
In-Reply-To: <m1bli9d8yl.fsf@yahoo.es> ("Daniel Martín"'s message of "Sun, 13 Sep 2020 16:53:22 +0200")
Daniel Martín <mardani29@yahoo.es> writes:
> I don't agree with this suggestion, at least as it is written. 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.
Nope -- in the Emacs tree, we're all about not making needless stylistic
changes, really. That's why we don't make white space changes, and we
don't change one-form `if' statements into `when' across the board.
We just live with it, and write the new code using whatever standard
we've settled on.
> Also, what would happen if you change code in an existing file? Would
> you need to fit it in 80 columns, 100 columns?
I'm not sure I understand what you're asking -- we never change the
formatting of anything (unless we rewrite the code), so nothing changes.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-13 15:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 13:45 Changing line widths in the Emacs source code Lars Ingebrigtsen
2020-09-13 13:58 ` Stefan Kangas
2020-09-13 14:09 ` Lars Ingebrigtsen
2020-09-13 15:53 ` Stefan Kangas
2020-09-13 16:21 ` Lars Ingebrigtsen
2020-09-13 16:51 ` Yuan Fu
2020-09-13 16:58 ` Lars Ingebrigtsen
2020-09-13 17:55 ` Stephen Leake
2020-09-13 18:04 ` arthur miller
2020-09-13 17:34 ` Eric Abrahamsen
2020-09-13 17:54 ` Stephen Leake
2020-09-13 14:22 ` Alan Mackenzie
2020-09-13 18:38 ` Vladimir Sedach
2020-09-13 20:13 ` Göktuğ Kayaalp
2020-09-13 20:52 ` Stefan Monnier
2020-09-13 21:23 ` Göktuğ Kayaalp
2020-09-14 0:08 ` Tim Cross
2020-09-13 23:45 ` Óscar Fuentes
2020-09-14 2:23 ` Stefan Monnier
2020-09-14 2:28 ` T.V Raman
2020-09-14 7:42 ` tomas
2020-09-14 9:59 ` Alan Third
2020-09-15 7:25 ` Stefan Kangas
2020-09-13 14:53 ` Daniel Martín
2020-09-13 15:01 ` Lars Ingebrigtsen [this message]
2020-09-13 17:23 ` Andy Moreton
2020-09-13 17:29 ` Lars Ingebrigtsen
2020-09-13 18:07 ` Göktuğ Kayaalp
2020-09-13 15:09 ` Stefan Kangas
2020-09-13 14:54 ` Eli Zaretskii
2020-09-13 14:57 ` Lars Ingebrigtsen
2020-09-13 15:13 ` Eli Zaretskii
2020-09-13 17:15 ` Lars Ingebrigtsen
2020-09-13 15:27 ` Stefan Monnier
2020-09-13 17:31 ` Dmitry Gutov
2020-09-13 17:34 ` Andrea Corallo via Emacs development discussions.
2020-09-16 6:42 ` jeremyb
2020-09-13 15:28 ` Göktuğ Kayaalp
2020-09-13 15:43 ` Óscar Fuentes
2020-09-13 17:07 ` Amin Bandali
2020-09-13 18:01 ` Stephen Leake
2020-09-13 18:17 ` Göktuğ Kayaalp
2020-09-14 3:50 ` Richard Stallman
2020-09-14 19:25 ` David Koppelman
2020-09-15 8:53 ` Lars Brinkhoff
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=877dsxlo0h.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
/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).