From: Joost Kremers <joostkremers@fastmail.fm>
To: emacs-devel@gnu.org
Subject: Re: Proposal for an emacs-humanities mailing list
Date: Thu, 03 Dec 2020 11:16:02 +0100 [thread overview]
Message-ID: <87sg8njiu5.fsf@fastmail.fm> (raw)
In-Reply-To: <246e72aa3c49450ac7d382f599cd86f5@skeletons.cc>
On Thu, Dec 03 2020, Paul W. Rankin via Emacs development discussions. wrote:
> So, a more precise description:
>
> This list is for general discussion on using GNU Emacs in the Humanities
> and Emacs-related topics that are interesting to those who study or
> otherwise participate in the Humanities (also called Liberal Arts in N.
> America). Discussion here welcomes contributions from any GNU Emacs user
> (or potential user) involved in the disciplines of: anthropology,
> archaeology, classics, history, linguistics and languages, law and
> politics, literature, philosophy, religion, or the performing or visual
> arts.
Personally, I wouldn't formulate it as if the list of disciplines is fixed.
Perhaps something like the following would be better:
"Discussion here welcomes contributions from any GNU Emacs user
(or potential user) involved in disciplines such as anthropology, [...]"
And perhaps even add an "etc." at the end of the list.
> Participants are assumed not to have programming knowledge and respected
> as such.
This formulation might be understood to exclude participants that *do* have
programming knowledge, I think. (At least, that's how I read it...) I assume
that's not your intention, so I'd at least move the "not" forward (which also
requires "are" to be inserted before "respected"):
"Participants are not assumed to have programming knowledge and are respected as
such."
(Honestly, I'm not a fan of the phrase "and are respected as such". It sounds as
if not having programming knowledge is somehow a defect...)
> Support that requires any writing of code should be directed to
> help-gnu-emacs@gnu.org.
This, too, sounds too restrictive IMHO. Adding a few lines to one's init file
can also be considered "writing code"...
My proposal for the second paragraph:
Participants are not assumed to have programming knowledge. Questions and
discussions regarding programming Emacs should generally be directed at
help-gnu-emacs@gnu.org.
Just my €0.02, of course.
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2020-12-03 10:16 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 [this message]
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
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=87sg8njiu5.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--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).