unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Distopico <distopico@riseup.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: flymake-guile
Date: Thu, 31 Aug 2023 11:03:48 -0500	[thread overview]
Message-ID: <875y4vi4c2.fsf@riseup.net> (raw)
In-Reply-To: <CADwFkmk8DuHf+jOLPf2hYMgwuUJ=BHnoUdpENg=Ke-py3wHuAw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]


On 2023-08-31, Stefan Kangas <stefankangas@gmail.com> wrote:

> Hi!
>
> Distopico <distopico@riseup.net> writes:
>
>> Hi all!
>>
>> I'm the author of a new package `flymake-guile` and I
>> would like to include it in Nongnu ELPA.
>>
>> Here the repo: https://framagit.org/flymake-backends/flymake-guile
>
> Thanks.
>
> Since you're the only author, how would you feel about adding it to
> GNU ELPA instead?
>
> One important difference between GNU ELPA and NonGNU ELPA is that any
> significant contribution (typically more than 15 lines) would need its
> copyright assigned to the FSF.  See:
> https://www.gnu.org/licenses/why-assign.html
>
> On the other hand, GNU ELPA is more tightly integrated with the rest of Emacs.
>

Thank you for your feedback, for now I'm fine having it in NonGNU ELPA


>> --8<---------------cut here---------------start------------->8---
>> ;;; Commentary:
>>
>> ;; Flymake backend for GNU Guile using `guild' compile.
>> ;;
>> ;; Usage:
>> ;;   (require 'flymake-guile)
>
> I don't think there is any need to require it, as the `flymake-guile'
> function is autoloaded.  So the `require' will just slow down starting
> Emacs, if a user adds it to their init file.
>
>> ;;   (add-hook 'scheme-mode-hook 'flymake-guile)
>
> You could also consider including this form:
>
> (use-package flymake-guile
>    :ensure t
>    :hook (scheme-mode-hook . flymake-guile))
I apply that recommendation, not you can see the change in the repo

thank you.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]

  reply	other threads:[~2023-08-31 16:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  2:23 [NonGNU ELPA] New package: flymake-guile Distopico
2023-08-31  6:31 ` Stefan Kangas
2023-08-31 16:03   ` Distopico [this message]
2023-08-31  6:52 ` Philip Kaludercic
2023-08-31 16:08   ` Distopico
2023-08-31 18:02     ` Philip Kaludercic
2023-08-31 19:22       ` Distopico
2023-09-01 13:09         ` Philip Kaludercic
2023-09-01 13:45           ` Dr. Arne Babenhauserheide
2023-09-01 13:52             ` Philip Kaludercic
2023-09-01 13:58           ` Distopico
2023-09-01 14:23             ` Philip Kaludercic
2023-09-05  2:23               ` Distopico
2023-09-05  7:08                 ` Philip Kaludercic
2023-09-05 15:09                   ` Distopico
2023-09-05 16:01                     ` Philip Kaludercic
2023-09-05 16:03                       ` Distopico
2023-08-31 11:03 ` Mauro Aranda
2023-08-31 16:13   ` Distopico
2023-08-31 16:15 ` Distopico

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=875y4vi4c2.fsf@riseup.net \
    --to=distopico@riseup.net \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@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).