unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Sacha Chua <sacha@sachachua.com>
Cc: Tom Davey <tom@tomdavey.com>, Emanuel Berg <incal@dataswamp.org>,
	emacs-tangents@gnu.org
Subject: Re: 2022-06-06 Emacs news
Date: Tue, 7 Jun 2022 23:32:58 +0300	[thread overview]
Message-ID: <Yp+1+lZswtmQR2Em@protected.localdomain> (raw)
In-Reply-To: <CAJGZZeJZYUUUjU5ibuL+XinexD+pAdXB_==jOaT_a9fzvbGo8g@mail.gmail.com>

* Sacha Chua <sacha@sachachua.com> [2022-06-07 19:26]:
> If people would like to volunteer to do even more, it might be fun to add
> some of the particularly useful links into, say, the EmacsWiki. Org
> workflows, programming configs, neat demos, Dired or eshell tricks...
> People could take charge of their favourite interests and add stuff as they
> come across neat links in news. Could be fun?

Emacs News is basically collection of links. 

My suggestion is that you setup a database with title, description and
URL, and then let people add to it on a website, as the database will
make sure that links are unique. Then you will know what is new and
what not.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2022-06-07 20:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  4:49 2022-06-06 Emacs news Sacha Chua
2022-06-07  4:55 ` Emanuel Berg
2022-06-07 11:13   ` Jean Louis
2022-06-07 13:20     ` Emanuel Berg
2022-06-07 13:47       ` How to send links for Emacs News " Sacha Chua
2022-06-07 14:58         ` Emanuel Berg
2022-06-07 15:29       ` Jean Louis
2022-06-07 15:48         ` Tom Davey
2022-06-07 16:04           ` Sunil Patel
2022-06-07 16:21           ` Emanuel Berg
2022-06-07 16:25           ` Sacha Chua
2022-06-07 16:36             ` Emanuel Berg
2022-06-07 20:32             ` Jean Louis [this message]
2022-06-07 23:55               ` Emanuel Berg
2022-06-08  4:40                 ` Jean Louis
2022-06-08  5:30                   ` Emanuel Berg
2022-06-08  3:37               ` Sacha Chua
2022-06-08  4:00                 ` Emanuel Berg
2022-06-08 16:03           ` Marcin Borkowski
2022-06-08 19:19             ` Jean Louis
2022-06-09  0:57               ` Emanuel Berg
2022-06-09  5:06               ` Marcin Borkowski
2022-06-09  5:22                 ` Emanuel Berg
2022-06-09  7:21                 ` Jean Louis
2022-06-09  8:01                   ` Emanuel Berg
2022-06-09  0:55             ` Emanuel Berg
2022-06-07 16:44         ` Emanuel Berg

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=Yp+1+lZswtmQR2Em@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=incal@dataswamp.org \
    --cc=sacha@sachachua.com \
    --cc=tom@tomdavey.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.
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).