From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: New package for Sweden: package-header.el - was Re: Interacting with minibuffer
Date: Sun, 23 May 2021 00:34:22 +0200 [thread overview]
Message-ID: <8735ue4cup.fsf@zoho.eu> (raw)
In-Reply-To: YKmDyG2qUuHHGQeN@protected.localdomain
Jean Louis wrote:
>> You mean this kind of stuff?
>>
>> ;;; Author: Emanuel Berg (incal) <moasenwood@zoho.eu>
>> ;;; Created: 2020-09-06
>> ;;; Keywords: bib, tex
>> ;;; License: GPL3+
>> ;;; Package-Requires: ((cl-lib "1.0"))
>> ;;; URL: https://dataswamp.org/~incal/emacs-init/issn-verify.el
>> ;;; Version: 1.0.0
>
> Yes, however, I don't think that conforms to licensing
> requirement, placing just a label of some license is not
> a license. Don't assume that recipient will know where to
> find the license. Use C-h C-c
Uhm, example, please?
More for you to "clean up!"
https://dataswamp.org/~incal/emacs-packs/
Well, this is great!
Except for the check thing, either a bug or something wrong
with my use:
(require 'checkdoc)
(setq checkdoc-permit-comma-termination-flag t)
(defun check-package-style ()
(interactive)
(let ((msg "Style check..."))
(message msg)
(checkdoc-current-buffer t) ; TAKE-NOTES
(message "%sdone" msg) ))
(defalias 'check-style #'check-package-style)
Looks simple/unrelated enough...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-05-22 22:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 18:45 Interacting with minibuffer Sébastien Le Callonnec
2021-05-22 20:21 ` Jean Louis
2021-05-22 20:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 21:55 ` New package for Sweden: package-header.el - was " Jean Louis
2021-05-22 22:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:08 ` Jean Louis
2021-05-22 22:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:28 ` Jean Louis
2021-05-22 22:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:56 ` Jean Louis
2021-05-22 23:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:44 ` Jean Louis
2021-05-22 22:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:20 ` Jean Louis
2021-05-22 22:34 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-05-22 22:51 ` Jean Louis
2021-05-22 22:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 23:10 ` Jean Louis
2021-05-23 0:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-23 0:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-23 1:13 ` Jean Louis
2021-05-23 1:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-23 1:42 ` Jean Louis
2021-05-23 1:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-23 1:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 21:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-23 6:38 ` Eli Zaretskii
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=8735ue4cup.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).