From: Dmitry Gutov <dmitry@gutov.dev>
To: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
Cc: Andrey Listopadov <andreyorst@gmail.com>, 67246@debbugs.gnu.org
Subject: bug#67246: 30.0.50; elixir-ts-mode uses faces inconsistently
Date: Fri, 24 Nov 2023 21:30:16 +0200 [thread overview]
Message-ID: <cef11c60-03b1-3a67-2f9d-40839eb132be@gutov.dev> (raw)
In-Reply-To: <CAOS0-34JrbfFxpfAwzryh7qpcaVTtAcZqtCynia4ovhY8DqsAQ@mail.gmail.com>
On 24/11/2023 21:23, Wilhelm Kirschbaum wrote:
>
> On Fri, Nov 24, 2023 at 9:06 PM Dmitry Gutov <dmitry@gutov.dev
> <mailto:dmitry@gutov.dev>> wrote:
>
> On 24/11/2023 20:56, Wilhelm Kirschbaum wrote:
> > On Mon, Nov 20, 2023 at 12:00 PM Andrey Listopadov
> <andreyorst@gmail.com <mailto:andreyorst@gmail.com>
> > <mailto:andreyorst@gmail.com <mailto:andreyorst@gmail.com>>> wrote:
> >
> > Nov 20, 2023 04:50:27 Dmitry Gutov <dmitry@gutov.dev
> <mailto:dmitry@gutov.dev>
> > <mailto:dmitry@gutov.dev <mailto:dmitry@gutov.dev>>>:
> >
> > > I guess I expected that if the mode has been added to the core
> > then the
> > > development is led here too. And modes maintained
> externally live
> > more
> > > easily in ELPA. Anyway, we are where we are.
> >
> >
> > I agree, but not sure how to deal with the users already using it on
> > emacs 29.1 with the MELPA package.
> > When I wanted to submit the package, I remember there being an email
> > saying we should not add packages to ELPA yet, so now I am stuck
> with
> > the github repository and MELPA.
> > Once 30 drops it should be easier to redirect conversations here,
> not
> > sure how this works. The packages are slightly different and I
> regret
> > my earlier decisions.
>
> OTOH, once Emacs 30 drops, there will be no good way to undo the
> inclusion, if you became so inclined.
>
>
> Which might be an option currently, since elixir-ts-mode hasn't been in
> an Emacs release yet.
>
>
> I am not sure what you mean? Which option? I meant I regret pushing it
> to MELPA first.
Ah. If you want it to stay in Emacs core (and not in ELPA), then it
should be easy enough to pull it from MELPA at any later point. Simply
asking should suffice.
next prev parent reply other threads:[~2023-11-24 19:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 19:50 bug#67246: 30.0.50; elixir-ts-mode uses faces inconsistently Andrey Listopadov
2023-11-18 1:36 ` Dmitry Gutov
2023-11-18 7:50 ` Wilhelm Kirschbaum
2023-11-20 1:50 ` Dmitry Gutov
2023-11-20 10:00 ` Andrey Listopadov
2023-11-24 18:56 ` Wilhelm Kirschbaum
2023-11-24 19:05 ` Dmitry Gutov
2023-11-24 19:23 ` Wilhelm Kirschbaum
2023-11-24 19:30 ` Dmitry Gutov [this message]
2023-11-24 19:47 ` Wilhelm Kirschbaum
2023-11-25 0:21 ` Dmitry Gutov
2023-11-25 8:33 ` Andrey Listopadov
2023-11-25 23:26 ` Dmitry Gutov
2023-11-27 17:59 ` Wilhelm Kirschbaum
2023-11-29 3:24 ` Dmitry Gutov
2023-12-03 10:41 ` Andrey Listopadov
2023-12-04 17:50 ` Wilhelm Kirschbaum
2023-12-04 17:46 ` Wilhelm Kirschbaum
2024-01-10 17:47 ` Stefan Kangas
2024-01-13 8:50 ` Wilhelm Kirschbaum
2024-01-29 4:08 ` Dmitry Gutov
2024-01-30 1:59 ` Dmitry Gutov
2024-02-05 17:05 ` Wilhelm Kirschbaum
2024-02-05 17:34 ` Wilhelm Kirschbaum
2024-02-05 17:42 ` Dmitry Gutov
2024-02-05 17:47 ` Wilhelm Kirschbaum
2024-02-05 20:51 ` Dmitry Gutov
2024-02-07 2:21 ` Dmitry Gutov
2024-02-23 15:05 ` Wilhelm Kirschbaum
2024-02-07 2:21 ` 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=cef11c60-03b1-3a67-2f9d-40839eb132be@gutov.dev \
--to=dmitry@gutov.dev \
--cc=67246@debbugs.gnu.org \
--cc=andreyorst@gmail.com \
--cc=wkirschbaum@gmail.com \
/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).