From: Omar Polo <op@omarpolo.com>
To: emacs-devel@gnu.org
Subject: a mode for algol 68
Date: Wed, 29 Nov 2023 13:16:21 +0100 [thread overview]
Message-ID: <3R4QN2M2RR03N.2G0ADM6I6F823@venera> (raw)
(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.
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.
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
next reply other threads:[~2023-11-29 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 12:16 Omar Polo [this message]
2023-11-29 12:57 ` a mode for algol 68 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
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=3R4QN2M2RR03N.2G0ADM6I6F823@venera \
--to=op@omarpolo.com \
--cc=emacs-devel@gnu.org \
/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).