unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: RE: emacs stackexchange beta site
Date: Fri, 19 Sep 2014 12:58:51 -0700 (PDT)	[thread overview]
Message-ID: <3370d086-c9d5-49b4-a7d7-5a04f17ceb74@default> (raw)
In-Reply-To: <87mw9vbezf.fsf@debian.uxu>

> >> Adding an emacs SX site just adds one more site to
> >> monitor, because I guess it won't be forbiden to ask
> >> an emacs question on superuser or tex in the future.
> >
> > That was exactly my point.
> 
> That's the strangest point ever. How can an
> Emacs-specific site make it more difficult to monitor?
> It will be *easier* to monitor because all Emacs stuff
> will be at one place!

What makes you think that will be the case?

> > And I don't see any great "PR" advantage, personally.
> > Is it so hard for users of SE sites to learn about
> > tags and filters?
> 
> Again, the tags will be much more elaborate and
> Emacs-specific on the Emacs site.

Nothing prevents you from creating Emacs-specific tags
today.  Make them as elaborate as you like.  Nothing
is more elaborate than elaborate-as-you-like.

> > Especially Emacs users and potential users?
> > If Emacs really needs PR that reaches past an
> > individual's ability to learn how to search for Emacs
> > questions and answers and throws "!! EMACS !!"
> > directly in their face so they'll notice it better,
> > then it's a sad day for Emacs and Emacs users
> > generally (IMHO).
> 
> Emacs shouldn't be a holy grale at the end of the
> rainbow. I have no problems with kids and morons
> starting to use Emacs at any stage of their age/degree
> of moronity. It won't make anyone more stupid and some
> will learn tremendously from it. Some will contribute
> themselves, one day. We have schools and we force the
> kids to go there. We don't expect the kids to be
> alright and eventually figure out how to write, read,
> count, and behave, left all alone. We obviously can't
> force anyone to use the software we believe in but we
> can give it maximum exposure so that at least a
> fraction of the computer people of tomorrow will know
> of other software than the MS and Apple IDEs.

Blah.  But I do support the idea of anyone, "at any stage",
including kids and the supposedly mentally challenged,
starting to use Emacs.  Welcome!



  reply	other threads:[~2014-09-19 19:58 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.9059.1410993440.1147.help-gnu-emacs@gnu.org>
2014-09-17 23:26 ` emacs stackexchange beta site Emanuel Berg
2014-09-18  2:06   ` Drew Adams
     [not found]   ` <mailman.9072.1411006041.1147.help-gnu-emacs@gnu.org>
2014-09-18 21:03     ` Emanuel Berg
2014-09-18 23:47       ` Stefan Monnier
2014-09-19 13:34         ` Tom
2014-09-19 14:53           ` Drew Adams
     [not found]           ` <mailman.9197.1411138427.1147.help-gnu-emacs@gnu.org>
2014-09-19 19:13             ` Emanuel Berg
2014-09-19 19:58               ` Drew Adams [this message]
     [not found]               ` <mailman.9231.1411156757.1147.help-gnu-emacs@gnu.org>
2014-09-19 20:24                 ` Emanuel Berg
2014-09-19 20:44                   ` Drew Adams
     [not found]                   ` <mailman.9235.1411159521.1147.help-gnu-emacs@gnu.org>
2014-09-19 21:01                     ` Emanuel Berg
     [not found]         ` <mailman.9194.1411136428.1147.help-gnu-emacs@gnu.org>
2014-09-19 19:06           ` Emanuel Berg
2014-09-19 19:55             ` Drew Adams
     [not found]             ` <mailman.9230.1411156541.1147.help-gnu-emacs@gnu.org>
2014-09-19 20:12               ` Emanuel Berg
2014-09-19  6:13       ` Udyant Wig
2014-09-19 17:57         ` Pascal J. Bourguignon
2014-09-19 18:54         ` Emanuel Berg
2014-09-20  6:58           ` Udyant Wig
2014-09-20 15:02             ` Emanuel Berg
2014-09-21 10:04               ` Udyant Wig
2014-09-21 15:49                 ` Emanuel Berg
2014-09-22  5:10                   ` Udyant Wig
2014-09-22 22:44                     ` Emanuel Berg
     [not found]         ` <mailman.9215.1411149649.1147.help-gnu-emacs@gnu.org>
2014-09-19 18:53           ` Udyant Wig
2014-09-19 19:18             ` Emanuel Berg
2014-09-19 19:22             ` Emanuel Berg
2014-09-19 23:46             ` Pascal J. Bourguignon
2014-09-20  1:24             ` Stefan Monnier
     [not found]             ` <mailman.9241.1411170621.1147.help-gnu-emacs@gnu.org>
2014-09-20  6:14               ` Udyant Wig
2014-09-20 14:47                 ` Emanuel Berg
2014-09-21 10:09                   ` Udyant Wig
2014-09-21 15:52                     ` Emanuel Berg
     [not found]             ` <mailman.9244.1411176300.1147.help-gnu-emacs@gnu.org>
2014-09-20  6:17               ` Udyant Wig
2014-09-19 18:58           ` Emanuel Berg
     [not found]       ` <mailman.9168.1411115739.1147.help-gnu-emacs@gnu.org>
2014-09-19 19:01         ` Emanuel Berg
2014-09-17 22:36 Ian Kelling
2014-10-11 13:33 ` Bastien
     [not found] ` <mailman.10973.1413034461.1147.help-gnu-emacs@gnu.org>
2014-10-17  0:04   ` Emanuel Berg
2014-10-17  0:16     ` Emanuel Berg
2014-10-17 21:37       ` Artur Malabarba
     [not found]       ` <mailman.11408.1413582659.1147.help-gnu-emacs@gnu.org>
2014-10-17 22:35         ` Emanuel Berg
2014-10-18 14:33           ` Rainer M Krug
2014-10-18 17:06           ` Artur Malabarba

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=3370d086-c9d5-49b4-a7d7-5a04f17ceb74@default \
    --to=drew.adams@oracle.com \
    --cc=embe8573@student.uu.se \
    --cc=help-gnu-emacs@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.
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).