From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 22884@debbugs.gnu.org
Subject: bug#22884: 25.0.92; C/l mode editing takes waaaayy too long
Date: Sun, 13 Mar 2016 10:03:54 +0000 [thread overview]
Message-ID: <20160313100354.GA1871@acm.fritz.box> (raw)
In-Reply-To: <20160304210818.GC2117@acm.fritz.box>
Hello, Paul.
On Fri, Mar 04, 2016 at 09:08:18PM +0000, Alan Mackenzie wrote:
> On Fri, Mar 04, 2016 at 12:32:06PM -0800, Paul Eggert wrote:
> > Alan Mackenzie wrote:
> > > I have had an idea for fixing Emacs so that we don't have this problem
> > > with parens in column 0. That is only to scan comments in the forward
> > > direction, and to mark them with text properties. `back_comment' will
> > > then be little more than checking these text properties are up to date,
> > > and then doing a backward text property search.
> > Would this mean we no longer need to put \( into Elisp doc strings too? It has
> > always been annoying that we have to do that.
> It would mean this, yes. open-paren-in-column-0-is-defun-start would
> become obsolete.
Apologies, but I was mistaken on this point. Being able to put "(" at
column 0 in Elisp strings would entail some further work, though that
work would not be difficult or disruptive.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-03-13 10:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 18:08 bug#22884: 25.0.92; C/l mode editing takes waaaayy too long Paul Eggert
2016-03-03 12:49 ` Alan Mackenzie
2016-03-03 17:54 ` Paul Eggert
2016-03-03 19:23 ` Alan Mackenzie
2016-03-03 20:38 ` Eli Zaretskii
2016-03-03 21:57 ` Paul Eggert
2016-03-03 22:59 ` Alan Mackenzie
2016-03-03 20:51 ` Eli Zaretskii
2016-03-03 23:44 ` Paul Eggert
2016-03-04 14:47 ` Alan Mackenzie
2016-03-04 20:32 ` Paul Eggert
2016-03-04 21:08 ` Alan Mackenzie
2016-03-13 10:03 ` Alan Mackenzie [this message]
2016-03-08 14:02 ` Alan Mackenzie
2016-03-09 8:25 ` Paul Eggert
2016-03-09 9:28 ` John Wiegley
2016-03-09 9:37 ` Paul Eggert
2016-03-09 21:30 ` John Wiegley
2016-03-09 10:56 ` Alan Mackenzie
2016-03-09 14:44 ` Drew Adams
2016-03-09 17:04 ` Alan Mackenzie
2016-03-09 17:14 ` Drew Adams
2016-03-03 20:40 ` Eli Zaretskii
2016-03-03 22:27 ` Alan Mackenzie
2016-03-03 23:18 ` Alan Mackenzie
2016-03-04 8:32 ` Eli Zaretskii
2016-03-04 9:37 ` Alan Mackenzie
2016-03-15 3:07 ` Stefan Monnier
2016-05-08 23:10 ` Dmitry Gutov
2016-05-13 19:35 ` Paul Eggert
2016-05-13 20:37 ` Glenn Morris
2016-05-13 21:09 ` Paul Eggert
2022-04-28 11:22 ` Lars Ingebrigtsen
2022-04-28 19:35 ` Paul Eggert
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=20160313100354.GA1871@acm.fritz.box \
--to=acm@muc.de \
--cc=22884@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).