unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Tom Davey <tom@tomdavey.com>
To: Jean Louis <bugs@gnu.support>, Emanuel Berg <incal@dataswamp.org>,
	"emacs-tangents@gnu.org" <emacs-tangents@gnu.org>
Subject: RE: 2022-06-06 Emacs news
Date: Tue, 7 Jun 2022 15:48:20 +0000	[thread overview]
Message-ID: <DM5PR08MB348242403332C15413234ECEDAA59@DM5PR08MB3482.namprd08.prod.outlook.com> (raw)
In-Reply-To: <0A407E62-54E2-44BB-942C-9279D490C849@gnu.support>

The regular listing of the threads in progress on the Emacs developer list is, by itself, invaluable. How Sacha is able to discover and write about so much else is beyond my comprehension. For us, the readers, Emacs News makes visible the vigorously beating heart of today's Emacs, increasingly from around the world. 

Tuesday morning would be bleak indeed were not Emacs News waiting for me in my Inbox. I can count at least 338 issues, beginning in October 2015. It is a stupendous amount work, produced week after week.

Sacha, thank you.  

--
Tom Davey
tom@tomdavey.com
New York NY USA

-----Original Message-----
From: Emacs-tangents <emacs-tangents-bounces+tom=tomdavey.com@gnu.org> On Behalf Of Jean Louis
Sent: Tuesday, June 7, 2022 11:29 AM
To: Emanuel Berg <incal@dataswamp.org>; emacs-tangents@gnu.org
Subject: Re: 2022-06-06 Emacs news

Now is time, send it to Sacha, I guess she may be reading it here, alert her. Send her links with titles.


On June 7, 2022 1:20:04 PM UTC, Emanuel Berg <incal@dataswamp.org> wrote:
>Jean Louis wrote:
>
>> News is what Sacha sends, and it can be anything about Emacs, new 
>> features, development discussion, me packages, demonstrations, 
>> anything that people write about it.
>
>But not a single thing I ever wrote about it the last
>10~15 years :(
>
>https://www.youtube.com/watch?v=VuDKPak3HQw


Jean


  reply	other threads:[~2022-06-07 15:48 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 [this message]
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
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=DM5PR08MB348242403332C15413234ECEDAA59@DM5PR08MB3482.namprd08.prod.outlook.com \
    --to=tom@tomdavey.com \
    --cc=bugs@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=incal@dataswamp.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).