From: Drew Adams <drew.adams@oracle.com>
To: Sacha Chua <sacha@sachachua.com>, help-gnu-emacs@gnu.org
Subject: RE: what I should do, and the "Emacs News Ezine"
Date: Fri, 29 Mar 2019 07:44:35 -0700 (PDT) [thread overview]
Message-ID: <3ad1c088-577c-43bb-b724-1b493f55071f@default> (raw)
In-Reply-To: <CAJGZZeJzi=UAnsJhEFaeCK+fKqVuEXqEDUxEbi2zEFgEtOwMeA@mail.gmail.com>
Wrt posting information, tutorials, articles, ~blog content, snippets, code,... whatever about Emacs and Lisp:
Emacs Wiki is yet another Emacs-community space.
Anyone can post such stuff on Emacs Wiki (duh, it's a wiki). And anyone can update or otherwise modify info that's there.
Editing content there doesn't use Markdown, but the markup is pretty simple and well documented.
next prev parent reply other threads:[~2019-03-29 14:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 5:12 todo-did.el complete rewrite Emanuel Berg
2019-03-25 6:57 ` Van L
2019-03-25 18:25 ` license and where to safely store all code (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-25 18:50 ` [OFF TOPIC] " Emanuel Berg
2019-03-25 20:04 ` todo-did.el complete rewrite Ralph Seichter
2019-03-26 0:07 ` where to put files (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-26 0:53 ` where to put files Ralph Seichter
2019-03-26 2:48 ` Emanuel Berg
2019-03-26 17:15 ` Robert Thorpe
2019-03-26 8:36 ` Van L
2019-03-25 20:45 ` todo-did.el complete rewrite Stefan Monnier
2019-03-25 23:41 ` Emanuel Berg
2019-03-26 17:35 ` Stefan Monnier
2019-03-27 0:37 ` Emanuel Berg
2019-03-27 1:42 ` Amin Bandali
2019-03-27 13:12 ` what I should do, and the "Emacs News Ezine" (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-27 13:40 ` what I should do, and the "Emacs News Ezine" Michael Albinus
2019-03-29 9:16 ` Marcin Borkowski
2019-03-29 12:49 ` Óscar Fuentes
2019-04-01 22:07 ` Emanuel Berg
2019-03-27 14:40 ` Amin Bandali
2019-03-28 0:05 ` Van L
2019-03-29 1:38 ` Amin Bandali
2019-03-29 6:27 ` Emanuel Berg
2019-04-27 14:58 ` Van L
2019-04-27 21:09 ` Emanuel Berg
2019-03-29 5:27 ` Sacha Chua
2019-03-29 14:44 ` Drew Adams [this message]
2019-04-01 22:11 ` Emanuel Berg
2019-04-26 7:04 ` Van L
2019-04-26 7:39 ` Emanuel Berg
2019-04-27 13:07 ` Van L
2019-04-27 21:07 ` Emanuel Berg
2019-04-26 7:47 ` tomas
2019-04-27 21:10 ` Emanuel Berg
2019-04-29 3:32 ` Van L
2019-04-04 4:18 ` Xavier Maillard
2019-04-04 3:31 ` Emanuel Berg
2019-04-17 0:39 ` Sacha Chua
2019-04-17 1:53 ` Emanuel Berg
2019-04-17 11:02 ` Van L
2019-04-17 19:07 ` Emanuel Berg
2019-04-01 13:07 ` 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=3ad1c088-577c-43bb-b724-1b493f55071f@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sacha@sachachua.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).