all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: googleartist@yahoo.com (Artist)
Subject: Re: An idea, Emacsmonks
Date: 20 Mar 2003 19:29:24 -0800	[thread overview]
Message-ID: <de3ad953.0303201929.3a232c0c@posting.google.com> (raw)
In-Reply-To: 87adfrm5le.fsf@gnu.org

Alex Schroeder <alex@gnu.org> wrote in message news:<87adfrm5le.fsf@gnu.org>...
> googleartist@yahoo.com (Artist) writes:
> 
> >  I know about http://emacswiki.wikiwikiweb.de/cgi-bin/wiki.pl but
> > somehow I like to format for perlmonks better.  Can we start
> > something like that..?  or I like to hear pro and cons for the same.
> 
> Hm.  I could of course write an elaborate style sheet for
> http://www.emacswiki.org/ -- and I could add frames and tables and
> other stuff -- but all that would not improve the fundamental core
> idea: Have pages editable by all on the web.  The information just
> keeps getting better and better.  No threads.  No outdated
> information.  No login.  No locking.  No spam.
> 
> So you'd have to describe what perlmonks does better -- what kind of
> "format" do you refer to?
> 
> Alex.

Thanks Alex,
 Here are my points:

1. Webbased Interface (Universal)
2. Question/Answers
3. Knowledge repository
4. Regular user base
5. Chat, Messages, Helping Hands
6. All in one place
7. More thinkable application
8. Faster Learning Curve
9. Faster Idea Exchange
10. Archive Search
11.(My familiar interface :-).


Artist.

  parent reply	other threads:[~2003-03-21  3:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19  3:54 An idea, Emacsmonks Artist
2003-03-19 21:03 ` Alex Schroeder
2003-03-19 21:54   ` David Masterson
2003-03-20  6:21   ` Ramakrishnan Muthukrishnan
2003-03-21  3:29   ` Artist [this message]
2003-03-21 23:23     ` Alex Schroeder
2003-03-26 11:40   ` Colin Marquardt

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=de3ad953.0303201929.3a232c0c@posting.google.com \
    --to=googleartist@yahoo.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.