From: David Kastrup <dak@gnu.org>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Adding to ELPA?
Date: Sun, 11 Oct 2015 18:57:59 +0200 [thread overview]
Message-ID: <87fv1hcpgo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAdUY-+C2TH2-+P6nxLZcUQMZCZ3fUn1gfg7iP291wZXx-SnMQ@mail.gmail.com> (Artur Malabarba's message of "Sat, 10 Oct 2015 23:07:14 +0100")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
> On 10 Oct 2015 8:50 am, "David Kastrup" <dak@gnu.org> wrote:
>
>> The problem is more that I am fuzzy on what Emacs versions to require
>> here if any. Until rather recently, Emacs tended to lose events
>> placed into unread-command-events when they were arriving not
>> one-by-one. With many MIDI input applications (but not necessarily
>> all) that's going to end up a problem.
>
> I see. If this bug is bearable, I would require an emacs version as
> low as possible. If the bug is game breaking, I would depend on a
> version that fixed the bug. Ultimately it's up to you.
>
> If you choose the second option and there's no released version
> without the bug, then it would be polite to wait for the next release.
I'm now depending on (emacs "25") and I'm afraid that I'll be impolite
in order to be able to use this package as a dependency for some
additions to the separately distributed LilyPond-mode.
--
David Kastrup
next prev parent reply other threads:[~2015-10-11 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 15:28 Adding to ELPA? David Kastrup
2015-10-10 7:08 ` Artur Malabarba
2015-10-10 7:50 ` David Kastrup
2015-10-10 22:07 ` Artur Malabarba
2015-10-11 16:57 ` David Kastrup [this message]
2015-10-11 17:47 ` Artur Malabarba
2015-10-11 18:09 ` David Kastrup
2015-10-11 23:15 ` Artur Malabarba
2015-10-12 5:56 ` David Kastrup
2015-10-12 7:58 ` Artur Malabarba
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=87fv1hcpgo.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=bruce.connor.am@gmail.com \
--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 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.