unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Immanuel Litzroth <immanuel.litzroth@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Is emacs module acceptable in ELPA?
Date: Mon, 19 Oct 2020 10:57:39 +0300	[thread overview]
Message-ID: <20201019075739.GL5209@protected.rcdrun.com> (raw)
In-Reply-To: <CAM1nAcybW0SXJYnzO5OEQyVGZct3KRKHSzUcEujXZJdzNBkf3A@mail.gmail.com>

* Immanuel Litzroth <immanuel.litzroth@gmail.com> [2020-10-19 10:27]:
> Is there way to make a package that is then using `make' and creating
> > module?
> There are some packages in Melpa that do this. They will compile the binary
> when the functionality is loaded in Emacs.
> https://github.com/akermu/emacs-libvterm
> https://github.com/politza/pdf-tools
> I think the package repos just have support for byte compiling .el files.
> Immanuel

Thank you.

By the way I do use emacs-libvterm as that is handling mutt mail
client in best manner. Emacs is missing maildir support, mutt is
handling maildir blazing fast, so I cannot without it. Since I started
using libvterm, term or ansi-term also improved, there were just few
bugs and it was improved, so I will switch back to ansi-term, I hope
it will work.

I did look into code of emacs-libvterm and I can see it tries to
compile the module, it does not succeed really, but it does say that
it was successful erroneously. Though concept inside seem to be good.

Would such module creation be accepted in GNU ELPA if authors agree?
They use cmake, and other build tools?




  reply	other threads:[~2020-10-19  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  7:14 Is emacs module acceptable in ELPA? Jean Louis
2020-10-19  7:26 ` Immanuel Litzroth
2020-10-19  7:57   ` Jean Louis [this message]
2020-10-19 14:11 ` Stefan Monnier

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=20201019075739.GL5209@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=emacs-devel@gnu.org \
    --cc=immanuel.litzroth@gmail.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).