From: Zhu Zihao <all_but_last@163.com>
To: "Paul W. Rankin" <pwr@skeletons.cc>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal for an emacs-humanities mailing list
Date: Mon, 30 Nov 2020 11:53:43 +0800 [thread overview]
Message-ID: <86mtyzmreg.fsf@163.com> (raw)
In-Reply-To: <10e79eeb32b5d8f49453fe62f145172d@skeletons.cc>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
That sounds good, but an important question is: How can I search across
different lists?
There's already two lists: emacs-devel@gnu.org and bug-gnu-emacs@gnu.org.
There's also emacs-tagnent@gnu.org but rarely used. Searching answer for
a existing question in maillist will be very inefficient and may result
in duplicated discussion.
Paul W. Rankin via Emacs development discussions. writes:
> During EmacsConf 2020 it became clear that there is a sizeable number of people
> who use Emacs outside of a programming context, specifically in the Humanities,
> and there was support for a mailing list dedicated to this group.
>
> The benefit of such a list would allow those using Emacs within the Humanities a
> way to become more directly involved with the project without committing to the
> emacs-devel or help-gnu-emacs lists, which are much more programming-focused
> than the average Humanities user may be comfortable with or interested in.
>
> I would be happy to administer this list, and could surely bring on others of a
> similar background and interest. (I'm a member of the Savannah Emacs group.)
>
> Proposed address:
> emacs-humanities@gnu.org
>
> Proposed description:
> This list is for general discussion and help for using GNU Emacs in the
> Humanities. Participants are assumed to be non-programmers and respected
> as such.
--
Retrieve my PGP public key: https://meta.sr.ht/~citreu.pgp
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
next prev parent reply other threads:[~2020-11-30 3:53 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 6:57 Proposal for an emacs-humanities mailing list Paul W. Rankin via Emacs development discussions.
2020-11-30 1:24 ` Karl Fogel
2020-11-30 3:16 ` Bob Newell
2020-12-01 5:20 ` Richard Stallman
2020-12-01 10:59 ` 황병희
2020-11-30 3:31 ` Eli Zaretskii
2020-11-30 3:55 ` Paul W. Rankin via Emacs development discussions.
2020-11-30 4:40 ` Karl Fogel
2020-11-30 5:41 ` Eli Zaretskii
2020-11-30 6:03 ` Paul W. Rankin via Emacs development discussions.
2020-11-30 16:02 ` Eli Zaretskii
2020-12-02 14:54 ` Eli Zaretskii
2020-12-03 8:30 ` Paul W. Rankin via Emacs development discussions.
2020-12-03 9:15 ` Protesilaos Stavrou
2020-12-03 10:35 ` Paul W. Rankin via Emacs development discussions.
2020-12-12 12:38 ` Eli Zaretskii
2020-12-14 22:28 ` Karl Fogel
2020-12-03 9:43 ` Jean Louis
2020-12-03 10:34 ` Paul W. Rankin via Emacs development discussions.
2020-12-03 10:16 ` Joost Kremers
2020-12-04 5:55 ` Richard Stallman
2020-12-03 20:10 ` Arthur Miller
2020-12-03 20:48 ` Stefan Monnier
2020-12-03 21:07 ` Arthur Miller
2020-12-03 23:22 ` Stefan Monnier
2020-12-03 23:41 ` Arthur Miller
2020-11-30 13:39 ` Leo Vivier
2020-11-30 17:23 ` Eric Abrahamsen
2020-11-30 21:27 ` Karl Fogel
2020-11-30 23:17 ` Drew Adams
2020-11-30 23:29 ` Gregory Heytings via Emacs development discussions.
2020-11-30 23:31 ` Karl Fogel
2020-12-01 8:57 ` tomas
2020-12-01 11:43 ` Jean Louis
2020-12-01 16:46 ` Drew Adams
2020-12-01 20:55 ` tomas
2020-12-01 17:42 ` Eric Abrahamsen
2020-12-02 4:29 ` Richard Stallman
2020-12-02 6:41 ` Eric Abrahamsen
2020-12-01 9:17 ` tomas
2020-12-01 11:40 ` Jean Louis
2020-11-30 9:36 ` Michael Albinus
2020-11-30 16:12 ` Eli Zaretskii
2020-11-30 16:19 ` Corwin Brust
2020-11-30 19:33 ` Jean Louis
2020-11-30 3:53 ` Zhu Zihao [this message]
2020-11-30 4:46 ` Richard Stallman
2020-11-30 9:13 ` Lars Ingebrigtsen
2020-11-30 12:03 ` Gregory Heytings via Emacs development discussions.
2020-11-30 13:29 ` Pankaj Jangid
2020-11-30 16:33 ` Eli Zaretskii
2020-11-30 14:36 ` Jean Louis
2020-11-30 16:13 ` Corwin Brust
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=86mtyzmreg.fsf@163.com \
--to=all_but_last@163.com \
--cc=emacs-devel@gnu.org \
--cc=pwr@skeletons.cc \
/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).