unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: "Paul W. Rankin" <pwr@skeletons.cc>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Protesilaos Stavrou <info@protesilaos.com>,
	emacs-devel@gnu.org
Subject: Re: Proposal for an emacs-humanities mailing list
Date: Thu, 3 Dec 2020 12:43:32 +0300	[thread overview]
Message-ID: <X8izROtUGM3XyypY@protected.rcdrun.com> (raw)
In-Reply-To: <246e72aa3c49450ac7d382f599cd86f5@skeletons.cc>

* Paul W. Rankin" via "Emacs development discussions. <emacs-devel@gnu.org> [2020-12-03 11:31]:
> Hi Eli,
> 
> Sorry for the delayed response.
> 
> Upon consulting Wikipedia, it seems that in the US the term "Humanities" has
> a narrower definition, i.e. as distinct from the arts and social sciences.
> For emacs-deval readers in the US, emacs-humanities would cover the Liberal
> Arts.
> 
> 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.

That sounds fine to me, partially.

You said people are welcome who are potential users of GNU Emacs. I
hope that also people will be welcome who are potentially interested
users in the discussion that is going on even if they are not involved
directly in some of those disciplines. There is anyway no method of
verification who is involved in some of those disciplines.

> Participants are assumed not to have programming knowledge and
> respected as such. Support that requires any writing of code should
> be directed to help-gnu-emacs@gnu.org.

I cannot see than how is the mailing list related to Emacs. Then maybe
you just wish to call it "humanities"?

When there is even setting with init file involved it is already so
that user is participating in the programming and that shall be
encouraged.

Then to tell such users to go to other mailing list is rather counter
productive, as let us say student of the law suddenly wish to write a
report in Org mode, should we then just bounce users from one to other
mailing lists, that does not seem useful.

Overall I am generally supporting any kind of communication between
people. People involved in humanities are already there. 

> I'm happy to moderate, although I think the ideal would be to have
> at least one additional moderator because sometimes I go stretches
> without attending to email. (I was sure I saw someone else in this
> thread put their hand up but upon reading back I think perhaps I
> misread.) I am painfully fickle when it comes to email addresses, so
> to be safe it probably should be hello@paulwrankin.com.

I hope it will not be moderated to exclude people for expressing their
opinions as the description above tells me it leads there. Maybe in
the next revision it will look so much better.






  parent reply	other threads:[~2020-12-03  9:43 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 [this message]
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
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=X8izROtUGM3XyypY@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.com \
    --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).