From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: buc.el ready
Date: Tue, 8 Jun 2021 17:28:53 +0300 [thread overview]
Message-ID: <YL9+pRQYqrrKdDOv@protected.localdomain> (raw)
In-Reply-To: <878s3kyduz.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-06-08 11:13]:
> Jean, or anyone else, take a look. Is the pack ready? [code
> also yanked last in mail]
>
> https://dataswamp.org/~incal/emacs-init/buc.el
>
> I went thru it and it is actually a very good an simple idea,
> I don't know why I suddenly didn't understand it's purpose and
> thought it complicated...
;;; buc.el --- move between buffers based on category -*- lexical-binding: t
;;;
;;; Commentary:
;;;
;;; Author: Emanuel Berg (incal) <moasenwood@zoho.eu>
;;; Created: 2021-05-23
;;; Keywords: docs, files
;;; License: GPL3+
;;; Package-Requires: ((cl-lib "1.0"))
;;; URL: https://dataswamp.org/~incal/emacs-init/buc.el
;;; Version: 2.0.0
Your "Commentary" comes too early there.
Why not read: (info "(elisp) Simple Packages")
Additionally you have not provided a license. "GPL3+" is some kind of
a tag, it is not a license and does not comply to GPL3 licensing
requirements. Use C-h C-c to find out "How to apply"
> I'm unsure tho if the documentation probably doesn't make anything
> clearer to a lot of people, right?
I was never reading documentation inside of package before some
years. I was reading description lines from M-x package-list-packages
and information about the package. Why should a user go into the
source, unless it is some programming library.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2021-06-08 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 8:12 Jean: buc.el ready (actually, now when I understand it again, it isn't a bad idea at all!) Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-08 14:28 ` Jean Louis [this message]
2021-07-06 9:39 ` buc.el ready Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 15:53 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-07-06 16:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=YL9+pRQYqrrKdDOv@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).