From: "Andreas Röhler" <andreas.roehler@online.de>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Beyond release
Date: Mon, 27 Jun 2016 11:58:01 +0200 [thread overview]
Message-ID: <5254d43b-39dd-7ac2-03d7-349e6d710a6b@online.de> (raw)
Hi Emacs,
while the release of Emacs 25 is pending and not everyone is involved
fixing remaining bugs, it might be time to reflect what to do afterward.
What about establishing a structured TODO - structured according to
importance and difficulty?
While Emacs is my editor of choice, it has some serious --and mostly
unnecessary-- flaws.
To make clear, that's not just a personal view, please consider the
withdraw of advanced and promising theorem prover Isabelle/HOL, which
doesn't longer support Emacs, while relying on it before. BTW that
withdraw was in time, before John took over and AFAIU caused by a
policy, which hopefully is abandoned now. "policy" means here: how to
design code and how to deal with bugs.
The most simple but far reaching bug IMO is the inconsistence of
beginning-of-defun introduced by open-paren-in-column-0-is-defun-start
and related. It not only makes Emacs Lisp editing somehow
non-professional, it also affects python.el and seems spread its
inconsistency beyond, making people believe such things are normal.
Cheers,
Andreas
next reply other threads:[~2016-06-27 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 9:58 Andreas Röhler [this message]
2016-06-27 14:18 ` Beyond release Clément Pit--Claudel
2016-06-27 15:33 ` Andreas Röhler
2016-06-27 15:52 ` Clément Pit--Claudel
2016-06-27 16:10 ` Dmitry Gutov
2016-06-27 16:25 ` Andreas Röhler
2016-06-27 16:55 ` Dmitry Gutov
2016-06-27 18:10 ` Andreas Röhler
2016-06-27 19:55 ` Dmitry Gutov
2016-06-28 6:14 ` Andreas Röhler
2016-06-28 11:13 ` Dmitry Gutov
2016-06-27 20:29 ` Alan Mackenzie
2016-06-28 8:39 ` Andreas Röhler
2016-06-27 16:21 ` Andreas Röhler
2016-06-27 16:40 ` Phillip Lord
2016-06-27 18:00 ` Clément Pit--Claudel
2016-06-27 18:05 ` Clément Pit--Claudel
2016-06-27 20:35 ` Phillip Lord
2016-06-27 15:53 ` Clément Pit--Claudel
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=5254d43b-39dd-7ac2-03d7-349e6d710a6b@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@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).