unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: ded-law@ddoherty.net, 13200@debbugs.gnu.org
Subject: bug#13200: 24.1.50; Ruby Mode Indentation after Here Docs
Date: Sun, 23 Dec 2012 19:49:20 -0500	[thread overview]
Message-ID: <jwvlicogtx7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <50D72C0A.2070508@yandex.ru> (Dmitry Gutov's message of "Sun, 23 Dec 2012 20:06:34 +0400")

>>>> package.el should be able to ignore your "out of date" elpa version if
>>>> the bundled version is more recent, so it should work even if you don't
>>>> uninstall the elpa version.
>>> By ignore, do you mean it won't show up in the list of packages
>>> available to install?
>> No, I mean it should not be added to load-path during startup.
> That may add to the confusion in this case. "I installed ruby-mode 1.1, but
> it didn't do anything!", or something.

No, because package.el wouldn't let you install 1.1 when you have 1.2
bundled (at least, not without warning you).

So this would only cause the downloaded package to be suddenly
superseded by the bundled package when you upgrade Emacs, which is The
Right Thing To Do.

>>> Do you think we should bump it to 1.2?
>> Depends.  Is it a fork?
> I meant, bump the version of the bundled ruby-mode.

I understand this.  But the question still stands: is the bundled
version really a more up-to-date version, or do we have a fork and there
are good reasons why someone would want to use the ELPA version over the
built-in one?

> The "ruby-mode 1.1" doesn't contain any substantial changes, AFAICT, so
> there's nothing to merge. But it is present in both Marmalade and the
> original ELPA.

Sounds like it's not a fork.  So we should bump our version accordingly.

> I opened an issue at the repo of the Marmalade uploader
> (https://github.com/resure/ruby-mode/issues/1), and if that doesn't result
> in anything, I'll escalate to the current Marmalade maintainer.

I'm not sure that there's a problem on their side.  They also cater to
older Emacsen.


        Stefan





  reply	other threads:[~2012-12-24  0:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16 11:04 bug#13200: 24.1.50; Ruby Mode Indentation after Here Docs Daniel Doherty
2012-12-16 20:24 ` Glenn Morris
     [not found]   ` <87a9t6kyho.wl%ded-law@ddoherty.net>
2012-12-22 18:42     ` Glenn Morris
2012-12-23 13:50       ` Stefan Monnier
2012-12-23 14:47         ` Dmitry Gutov
2012-12-23 15:41           ` Stefan Monnier
2012-12-23 16:06             ` Dmitry Gutov
2012-12-24  0:49               ` Stefan Monnier [this message]
2012-12-24  2:12                 ` Dmitry Gutov
2012-12-24  5:11                   ` Stefan Monnier
2012-12-16 20:30 ` 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

  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=jwvlicogtx7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=13200@debbugs.gnu.org \
    --cc=ded-law@ddoherty.net \
    --cc=dgutov@yandex.ru \
    /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).