unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: JD Smith <jdtsmith@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 39992@debbugs.gnu.org
Subject: bug#39992: Merge external idlwave development efforts into GNU Emacs?
Date: Sun, 19 Sep 2021 12:41:12 -0400	[thread overview]
Message-ID: <6B65AE1C-0D47-490D-BEF3-385BC6FCEE7E@gmail.com> (raw)
In-Reply-To: <CADwFkmmDH6VuxmrZV=pjqFJUveX=dk_2q-gJP+jDNTQYnfSZVA@mail.gmail.com>


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.  

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).

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. 

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. 

Best,
JDS

> On Sep 19, 2021, at 12:05 PM, Stefan Kangas <stefan@marxist.se> wrote:
> 
> Stefan Kangas <stefan@marxist.se> writes:
> 
>> 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?
> 
> The above email bounced, so I have now copied in the email address used
> in the GitHub repository.






  reply	other threads:[~2021-09-19 16:41 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 [this message]
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=6B65AE1C-0D47-490D-BEF3-385BC6FCEE7E@gmail.com \
    --to=jdtsmith@gmail.com \
    --cc=39992@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).