From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: cyd@gnu.org, 11354@debbugs.gnu.org
Subject: bug#11354: 24.1.50; long lines (214 chars!) in files.el
Date: Thu, 26 Apr 2012 11:11:48 -0700 [thread overview]
Message-ID: <6E85BC44392D46329A8B001686F5265D@us.oracle.com> (raw)
In-Reply-To: <83aa1yidyc.fsf@gnu.org>
> Yes, frivolous "bugs". Coding style is not a bug.
1. Debatable. Emacs is about source code, not just executable behavior. Emacs
users deserve clean, readable code. The source code is part of Emacs and the
experience of using Emacs. A big part. Not to recognize and respect that is to
do a disservice to users.
2. `report-emacs-bug' is not only for bugs, in any case. It is for improvements
generally, including bugs and enhancement requests. A suggestion to improve
usability is as valid as a report about a critical security bug, even if the fix
is not as important.
There is no reason for such stubborn resistance to such a reasonable suggestion,
which is after all in line with the GNU policy. It is trivial to fix this -
takes far less time and effort than your resistance/obstruction. Is your desire
to improve Emacs or to fight some silly battle?
By declaring this "won't fix" you are effectively deciding that it is _better_
to have such long lines in the code than it is to respect the longstanding
policy of limiting line length.
How so?
a. Because the fix is so trivial.
b. Because leaving such extremely long lines here and there does not discourage
their use elsewhere: it sets a bad example.
next prev parent reply other threads:[~2012-04-26 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 16:22 bug#11354: 24.1.50; long lines (214 chars!) in files.el Drew Adams
2012-04-26 17:09 ` Chong Yidong
2012-04-26 17:32 ` Drew Adams
2012-04-26 17:46 ` Eli Zaretskii
2012-04-26 18:11 ` Drew Adams [this message]
2012-04-26 18:30 ` Stefan Monnier
2012-04-26 18:49 ` Drew Adams
2012-04-26 20:59 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6E85BC44392D46329A8B001686F5265D@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=11354@debbugs.gnu.org \
--cc=cyd@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.