|
From: | Dmitry Gutov |
Subject: | bug#2820: 23.0.91; ruby-mode binds keys it probably shouldn't |
Date: | Tue, 04 Sep 2012 23:10:17 +0400 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 |
On 04.09.2012 18:39, Stefan Monnier wrote:
Just setting forward-sexp-function value would break `up-list' and backward-up-list', for example.That's a problem, yes. We need a better story to extend forward-sexp-function to up-list (probably with something like the addition of an up-list-function).
That would be one way to solve it, I guess. In js2-mode-forward-sexp, I just decided to emulate the default behavior - signal scan-error with the right message and arguments when appropriate - because `up-list' expects the error with the right arguments, and autopair actually checks the error message for the word "prematurely".
There may be other third-party packages that rely on its behavior.
[Prev in Thread] | Current Thread | [Next in Thread] |