unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: Omar Polo <op@omarpolo.com>,  emacs-devel@gnu.org
Subject: Re: a mode for algol 68
Date: Thu, 30 Nov 2023 13:01:39 +0000	[thread overview]
Message-ID: <875y1j8kek.fsf@posteo.net> (raw)
In-Reply-To: <87r0k7a31e.fsf@gnu.org> (Jose E. Marchesi's message of "Thu, 30 Nov 2023 12:33:49 +0100")

"Jose E. Marchesi" <jemarch@gnu.org> writes:

>> On 2023/11/30 07:10:20 +0000, Philip Kaludercic <philipk@posteo.net> wrote:
>>> Omar Polo <op@omarpolo.com> writes:
>>> 
>>> > (please Cc: me since I'm not subscribed to this list)
>>> >
>>> > Two years ago I started hacking on Jose E. Marchesi' algol-mode (that
>>> > I've renamed a68-mode) while I was playing with the algol68g compiler.
>>> > Truth to be told, I think I've spent more time hacking on the emacs mode
>>> > that with the language itself, but anyway...
>>> >
>>> > I haven't touched the mode any more for the last two years, and I doubt
>>> > I'll hack again on it in the future.  Although it's almost finished,
>>> > there remains issues with the indentation and font-locking in some
>>> > cases.
>>> >
>>> > My hope would be that some friendly hacker would take interest in
>>> > maintaining it and maybe even distribute it in ELPA / NonGNU Elpa.
>>> 
>>> I think it would be very nice to have this added to GNU ELPA.  If the
>>> code works (and I see it isn't too much), it shouldn't be too much of a
>>> maintenance burden, so I'd be fine with helping out.
>>> 
>>> > On the copyright side, I don't know Jose E. Marchesi and I copied
>>> > initial the code from some random github repository.  Not great, I know,
>>> > but it was the only major mode for algol68.  However, I *do* have an FSF
>>> > copyright assignment and I ended up rewriting almost all of the code in
>>> > the end.  I paied attention to do the 'initial import' with the original
>>> > code as-is and do my changes on top.  It's 53 commits in total.
>>> 
>>> I cannot evaluate this myself, do you a link to the original GitHub
>>> repository?
>>
>> I took the code from
>> https://github.com/lachrymology/me/blob/master/.emacs.d/extras/algol-mode.el
>> but upon a closer look it seems to originate from here:
>> https://www.jemarch.net/algol68.html
>>
>> I'm cc'ing Jose E. Marchesi using the mail found on (presumibly) their
>> website.  Having a @gnu.org account makes me think that there shouldn't
>> be copyright issues :-)
>
> I have papers in place for Emacs, and I am totally willing to transfer
> the copyright for a68-mode.el's original code (whatever of it survives
> in latest algol-mode.el) to the FSF.

OK, in that case everything should be given to add the package to GNU
ELPA.  The only matter left discussing is if you want to continue to
host the repository yourself and have the ELPA server mirror the
repository regularly.

>> I apologize for not searching better initially, I should have contacted
>> Marchesi in the first place.  I somehow have completely missed their
>> website.
>>
>>> > The code is available here for browsing here:
>>> > <https://git.omarpolo.com/?action=summary&path=a68-mode.git>
>>> > and can be cloned with git via anonymous SSH via
>>> > <ssh://anon@omarpolo.com/a68-mode.git> or with HTTPS via
>>> > <https://git.omarpolo.com/a68-mode.git>.
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > Omar Polo



  reply	other threads:[~2023-11-30 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 12:16 a mode for algol 68 Omar Polo
2023-11-29 12:57 ` Emanuel Berg
2023-11-30  7:10 ` Philip Kaludercic
2023-11-30 10:19   ` Omar Polo
2023-11-30 11:33     ` Jose E. Marchesi
2023-11-30 13:01       ` Philip Kaludercic [this message]
2023-11-30 13:14         ` Jose E. Marchesi

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=875y1j8kek.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=jemarch@gnu.org \
    --cc=op@omarpolo.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).