unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuchen Pei <id@ypei.org>
To: Emacs Devel mailing list <emacs-devel@gnu.org>
Subject: [ELPA] New package: hcel
Date: Sun, 11 Sep 2022 01:01:35 +1000	[thread overview]
Message-ID: <87pmg346k0.fsf@ypei.org> (raw)

Hello,

I'd like to submit my little package called hcel[1] to ELPA.

It is a Haskell codebase explorer, using the server program provided by
haskell-code-explorer[2], which I ported to recent GHC version[3] and
I named my port / fork hcel.

[1] https://g.ypei.me/hcel.git/tree/lisp
[2] https://github.com/alexwl/haskell-code-explorer
[3] https://g.ypei.me/hcel.git/about/

I'm not sure whether it is unusual to submit a package that relies on a
self-hosted free software server program, but I am also not aware of
packages doing anything similar.  There are packages offering related
functionalities, like eglot, which can work with
haskell-language-server.  However, haskell-language-server requires more
ram and cpu, and does not support cross-package find-definition and
references.

Basically, this is an emacs version of the web client that is included
in the original haskell-code-explorer.  In general, I think emacs as an
alternative client to the web browser is a way to avoid nonfree
javascript, similar to alternative web frontends (e.g. invidious,
teddit, haketilo), but better (because emacs).  Ideally there should be
an "emacs app store" offering (GPL covered) clients to all sorts of web
services, which could be a subset of ELPA packages, to advance the user
freedom of at least emacs users.  But I digress.

The server and client programs are currently in the same repo, and I
hold the copyright of the emacs package, but not the server.  I can
assign the copyright of the emacs package and separate it out into its
own git repo of course, and I can also ask the original authors for
copyright assignment if needed.

I have been using this package for a week or two, and expect to use it
as aid for writing Haskell programs.  So as long as I write Haskell and
the package has not been superceded by other tools like
haskell-language-server, I am motivated to make sure it works well.

What do you think?

Best,
Yuchen

-- 
PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
          <https://ypei.org/assets/ypei-pubkey.txt>



             reply	other threads:[~2022-09-10 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10 15:01 Yuchen Pei [this message]
2022-09-17  0:40 ` [ELPA] New package: hcel Yuchen Pei
2022-09-19  0:15   ` How Do I submit a package to ELPA? (was Re: [ELPA] New package: hcel) Yuchen Pei
2022-09-20 21:26 ` [ELPA] New package: hcel Stefan Monnier
2022-09-21  6:18   ` Yuchen Pei
2022-09-21 12:03     ` Stefan Monnier
2022-09-20 21:42 ` Stefan Monnier
2022-09-21  5:58   ` Yuchen Pei
2022-09-21  6:21     ` Stefan Kangas
2022-09-21  7:19     ` Michael Heerdegen
2022-09-21  7:44       ` Emanuel Berg

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=87pmg346k0.fsf@ypei.org \
    --to=id@ypei.org \
    --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).