unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: JD Smith <jdtsmith@gmail.com>
Cc: 39992@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#39992: Merge external idlwave development efforts into GNU Emacs?
Date: Sun, 19 Sep 2021 10:23:02 -0700	[thread overview]
Message-ID: <CADwFkmkgLnMkPJogRygmcYRiFYndC97Zht6yrrf8kR+jRPQ1yg@mail.gmail.com> (raw)
In-Reply-To: <6B65AE1C-0D47-490D-BEF3-385BC6FCEE7E@gmail.com>

JD Smith <jdtsmith@gmail.com> writes:

> I’m happy for anyone to work on merging the latest IDLWAVE into Emacs,
> and I can assist with this process as time allows.  This might require
> some moderate effort, since I believe I refactored and simplified the
> code layout (in an attempt to attract a new maintainer) after my last
> push into emacs core.  This refactoring occurred around 20015/16. My
> last commit on GitHub was actually in 2018.

Thank you for your efforts in maintaining this package.  I don't
actually use it myself, so I only have a few observations on the
maintenance aspects below.

> I’ve also discussed with several of the emacs devels over the years
> moving IDLWAVE to a package on Elpa.  I think that’s a more
> appropriate home, since there are not terribly many users (as judged
> by the number of email queries I get now vs. a decade ago).

That makes sense to me.  I'm copying in Stefan Monnier, who is in charge
of GNU ELPA, in case he has anything to add.

> I still use IDLWAVE, but far more rarely than before.  There is
> currently a bug related to routine info scanning that I need to look
> into.  I’m happy to do this in the context of a merged core/elpa
> package if someone is able to lead that effort.  There were numerous
> changes on the emacs side based on obsoleted functions, etc. that I
> never found the time to bring over.

If we could get those changes merged into your version, perhaps we could
just replace the one in Emacs with yours?

It would of course be excellent if you could eventually find the time to
do that, and a priori it sounds like much less works than going the
other way around.

> And needless to say, if you know of any users of IDLWAVE who are
> interested in taking over maintenance and overseeing its re-folding
> back into the emacs core/elpa, I’d be delighted to speak with them.

I currently don't, unfortunately.  I suppose we shall have to wait and
see if there is someone interested.

Thanks again for getting back to us about this.





  reply	other threads:[~2021-09-19 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09  1:16 bug#39992: Merge external idlwave development efforts into GNU Emacs? Stefan Kangas
2021-09-19 15:49 ` Stefan Kangas
2021-09-19 16:05   ` Stefan Kangas
2021-09-19 16:41     ` JD Smith
2021-09-19 17:23       ` Stefan Kangas [this message]
2021-09-19 17:40         ` Eli Zaretskii

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=CADwFkmkgLnMkPJogRygmcYRiFYndC97Zht6yrrf8kR+jRPQ1yg@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=39992@debbugs.gnu.org \
    --cc=jdtsmith@gmail.com \
    --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 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).