unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christian <cnngimenez@disroot.org>
To: emacs-devel@gnu.org
Subject: [ELPA] New package: SachaC-news
Date: Sun, 12 Nov 2023 16:32:17 -0300	[thread overview]
Message-ID: <87o7fyix8e.wl-cnngimenez@disroot.org> (raw)

Hi!

I want to propose SachaC-news (or sachac-news.el if you like)
package to be included in ELPA. Its objective is to check for
Sacha Chua's news repository periodically, and to show the Org
file if there is a new commit with a new post in it. It has
some customizations too, such as folding specific sections
automatically, and desktop notifications via "notify-send". The
requirement is the git program to be installed on your system.
This information and its usage is at the README.org file at the
package repository:

          https://github.com/cnngimenez/sachac-news

The code has been checked with byte-compile-file, and
flycheck configured with checkdoc and flycheck-package [1].
They do not display any warnings up to commit d00e629, but tell
me if you find something to fix or any suggestions.

According to http://elpa.gnu.org/, and the README.org [2] file
linked there, it says to notify to this mail address as
first step. Also, it mentions other steps regarding pushing the
code and adding an entry on elpa-packages file. But, there is a
marker above indicating "OUTDATED" [3].

Please, could you tell me if these steps are needed?
If they are not, how should I proceed?

Cheers!
Christian Gimenez

[1] https://github.com/purcell/flycheck-package
[2] https://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/README
[3] The section states: "Text below this marker is OUTDATED and
still needs to be reviewed/rewritten!!"



             reply	other threads:[~2023-11-12 19:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 19:32 Christian [this message]
2023-11-14  2:56 ` [ELPA] New package: SachaC-news Richard Stallman
2023-11-15 23:56   ` Björn Bidar
2023-11-14  2:56 ` Richard Stallman
2023-11-18 20:26   ` Christian
2023-11-21 16:07     ` Sacha Chua
2023-11-25 22:40       ` Christian
2023-12-31  3:13     ` Richard Stallman
2023-12-31 18:13       ` Adam Porter
2023-12-31 19:32         ` Eli Zaretskii
2023-12-31 21:36           ` Adam Porter
2023-12-31 22:33             ` Christopher Dimech
2023-12-31 22:57             ` Emanuel Berg
2024-01-01 12:01             ` Eli Zaretskii
2024-01-02  3:19         ` Richard Stallman
2024-01-02  5:08           ` Emanuel Berg
2024-01-04  4:01             ` Richard Stallman
2024-01-02 18:05         ` Christian
2024-01-02  0:04       ` Stefan Kangas
2024-01-05  4:23         ` Richard Stallman
2024-01-02 17:40       ` Christian Gimenez
2023-11-17  7:28 ` Philip Kaludercic
2023-11-18 20:30   ` Christian
2023-11-18 21:10     ` Philip Kaludercic
2023-11-25 22:07       ` Christian
2023-11-25 22:50         ` Philip Kaludercic

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=87o7fyix8e.wl-cnngimenez@disroot.org \
    --to=cnngimenez@disroot.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).