From: Bozhidar Batsov <bozhidar@batsov.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] * lisp/progmodes/ruby-mode.el: Use `setq-local' where appropriate.
Date: Thu, 31 Oct 2013 21:44:50 +0200 [thread overview]
Message-ID: <CAM9Zgm0B=N2L3SfjOX-xjqEkN=T6PV1xh6VFPTLN2O-5YSxv9Q@mail.gmail.com> (raw)
In-Reply-To: <jwv61sdtjju.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
I think that we don't need to worry about compatibility with the other
version of the ruby-mode in Ruby's SVN repo, since just about nobody uses
it (except maybe some Emacs 23 users?).
ruby-mode suffers from a lot of legacy in it (compared to other built-in
modes) and would definitely benefit from a clean up. After all, simpler
code is always easier to improve, extend and debug.
On 31 October 2013 19:55, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > The attached patch simply replaces (set (make-local-variable …)…) with
> > setq-local’ where appropriate in ruby-mode.el.
>
> Is it OK to use such bleeding-edge constructs in ruby-mode.el, or is
> there still some external version with which we should try to preserve
> compatibility?
>
> I meant, the code still tests (functionp 'syntax-ppss), so if we can
> drop backward compatibility, there are probably more cleanups ahead.
>
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 1396 bytes --]
next prev parent reply other threads:[~2013-10-31 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 12:40 [PATCH] * lisp/progmodes/ruby-mode.el: Use `setq-local' where appropriate Bozhidar Batsov
2013-10-31 17:55 ` Stefan Monnier
2013-10-31 19:44 ` Bozhidar Batsov [this message]
2013-11-01 3:43 ` Dmitry Gutov
2013-11-01 12:26 ` Stefan Monnier
2013-11-02 0:23 ` Dmitry Gutov
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='CAM9Zgm0B=N2L3SfjOX-xjqEkN=T6PV1xh6VFPTLN2O-5YSxv9Q@mail.gmail.com' \
--to=bozhidar@batsov.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.