unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: 39992@debbugs.gnu.org
Cc: jd smith <jdsmith@rain.mhr.utoledo.edu>
Subject: bug#39992: Merge external idlwave development efforts into GNU Emacs?
Date: Sun, 19 Sep 2021 08:49:47 -0700	[thread overview]
Message-ID: <CADwFkmkHmb-YU-bPVBVFjxSa3M6Mf45agi72rqMWzNvKz54R5A@mail.gmail.com> (raw)
In-Reply-To: <875zfe49a2.fsf@stefankangas.se> (Stefan Kangas's message of "Mon, 09 Mar 2020 02:16:53 +0100")

Stefan Kangas <stefan@marxist.se> writes:

> I don't use it myself, but I noticed that there is ongoing development
> of idlwave.el here:
>
>     https://github.com/jdtsmith/idlwave
>
> As far as I can tell from the git log, the last change to idlwave by
> JD Smith was on Fri Apr 27 19:34:22 2007 +0000.
>
> Would it be possible to merge this effort into the version distributed
> with GNU Emacs itself?  That way more users could benefit from the
> improvements.

I note that on the GitHub page, there has since been added a note:

    Note: IDLWAVE is currently not maintained. In current form it
    supports IDL v8.6, and is still in daily use by some users.

    If you are interested in taking over IDLWAVE maintenance, please
    post an issue. See the DEVELOP file for information on the file
    structure layout.

I'm not sure what this means for the idlwave we ship with Emacs.

JD Smith, do you mind if someone else tries to on merge your external
development efforts into Emacs itself?





  reply	other threads:[~2021-09-19 15:49 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 [this message]
2021-09-19 16:05   ` Stefan Kangas
2021-09-19 16:41     ` JD Smith
2021-09-19 17:23       ` Stefan Kangas
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=CADwFkmkHmb-YU-bPVBVFjxSa3M6Mf45agi72rqMWzNvKz54R5A@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=39992@debbugs.gnu.org \
    --cc=jdsmith@rain.mhr.utoledo.edu \
    /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).