From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: I wrote a mini manual for Emacs
Date: Mon, 16 Jun 2014 20:00:24 -0700 (PDT) [thread overview]
Message-ID: <00a2f060-2c73-452e-b330-a6f8c5fb8e6b@googlegroups.com> (raw)
In-Reply-To: <mailman.3803.1402972638.1147.help-gnu-emacs@gnu.org>
On Tuesday, June 17, 2014 8:07:12 AM UTC+5:30, Tu Do wrote:
> On Tue, Jun 17, 2014 at 1:11 AM, MBR wrote:
> > Good work!
> > I'd like to say something about the section ""I don't want a complicated
> > 'editor', I want something simple like Notepad(++)" in which you talk about
> > IDEs. When I started using Emacs (after about 10 years of using vi), I
> > immediately noticed that Emacs was very different from any other editor I'd
> > ever worked with. With all other editors, I'd use them for editing text
> > and do everything else from a shell prompt.
> Well, I did in the section "Why Emacs?" at the beginning, emphasized that
> Emacs is not a mere editor but a programming platform and has relation to
> Lisp Machine. However, someone said that is not good for beginners to put
> non-starter stuffs there. So I moved it to the appendix.
I think thats a good choice. In my 20+ years of using emacs and
convincing others (mostly unsuccessfully) to use it Ive found that
showing emacs' power is usually a put-off more than an attraction.
People say: «Look I ONLY want to do "..."! Why all this "..." »
रुसि [Just to make GG behave itself!]
next prev parent reply other threads:[~2014-06-17 3:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 5:24 I wrote a mini manual for Emacs Tu Do
2014-06-16 13:34 ` Tim Visher
2014-06-16 13:52 ` Tu Do
[not found] ` <mailman.3750.1402925697.1147.help-gnu-emacs@gnu.org>
2014-06-16 14:26 ` Rusi
2014-06-16 14:49 ` Tim Visher
2014-06-16 15:51 ` tuhdo1710
2014-06-16 15:14 ` Bastien
[not found] ` <mailman.3754.1402931683.1147.help-gnu-emacs@gnu.org>
2014-06-16 15:55 ` tuhdo1710
2014-06-16 22:08 ` Bastien
2014-06-17 2:33 ` Tu Do
[not found] ` <mailman.3786.1402956500.1147.help-gnu-emacs@gnu.org>
2014-06-17 5:55 ` Rusi
2014-06-17 7:02 ` solidius4747
2014-06-17 17:05 ` solidius4747
2014-06-16 18:11 ` MBR
2014-06-17 2:37 ` Tu Do
[not found] ` <mailman.3803.1402972638.1147.help-gnu-emacs@gnu.org>
2014-06-17 3:00 ` Rusi [this message]
2014-06-17 3:59 ` Yuri Khan
[not found] ` <mailman.3768.1402942300.1147.help-gnu-emacs@gnu.org>
2014-06-16 19:27 ` Barry Margolin
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=00a2f060-2c73-452e-b330-a6f8c5fb8e6b@googlegroups.com \
--to=rustompmody@gmail.com \
--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).