From: Tu Do <tuhdo1710@gmail.com>
To: MBR <mbr@arlsoft.com>
Cc: emacs <help-gnu-emacs@gnu.org>
Subject: Re: I wrote a mini manual for Emacs
Date: Tue, 17 Jun 2014 09:37:12 +0700 [thread overview]
Message-ID: <CAOEd9jmvdaWYA3ksSwdHOgcbQD02v5o2z9HpwCrJfNrqivrkzA@mail.gmail.com> (raw)
In-Reply-To: <539F334B.7080006@arlsoft.com>
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.
On Tue, Jun 17, 2014 at 1:11 AM, MBR <mbr@arlsoft.com> 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.
>
> But once I started using Emacs I started telling people, "Emacs isn't an
> editor, it's a way of life!" What I meant by that was that I found I was
> starting up a single instance of Emacs in the morning, and virtually
> everything I did the rest of the day was done inside Emacs. If I needed to
> run a shell command, I'd do that inside an Emacs shell buffer because that
> way the command's output was automatically captured in the buffer and I
> could then use it like any other text - comparing it to other things with
> compare-window, searching for regular expressions in the output, saving
> some interesting portion of the output by simply copying it to a file,
> etc., etc.
>
> Besides being able to run a shell inside the "editor", you could run your
> compiler and linker straight from Emacs and have it parse and highlight any
> errors; you could debug your code inside Emacs with gdb and later gud, and
> have many added benefits over running gdb directly from the shell. One of
> those benefits is having it show you the source code, including a pointer
> showing what line of code you're about to execute.
>
> The bottom line is that Emacs actually is an IDE, not merely a text
> editor. It just happens to be an IDE that works on a dumb terminal. As
> a matter of fact, it's the original IDE! It existed before any of the
> GUI-style IDEs existed, and many features commonly found in IDEs were
> copied from Emacs.
>
> So, it wouldn't hurt to emphasize at the beginning of your Mini Manual
> that Emacs should not be thought of as an editor. It is a software
> development environment with powerful text editing capabilities. And it's
> much more than even that!
>
> Mark Rosenthal
>
> On 6/16/14 1:24 AM, Tu Do wrote:
>
> Hi everyone,
>
> I wrote an Emacs Mini Manual for complete beginners to be productive with
> Emacs common tools without having to look all over the manual. It provides
> a starting point before reading the full Emacs manual. Folow this link: Why
> This Guide? <http://tuhdo.github.io/emacs-tutor.html#sec-2> <http://tuhdo.github.io/emacs-tutor.html#sec-2> to read it
> fully.
>
> I hope it will be useful for new people switching to Ubuntu and want to
> have a nice development environment. If you find mistakes, please report it
> to me. If you think I'm missing commonly used tools or some idiomatic uses
> of Emacs, please tell me.
>
> Thanks
>
>
>
>
next prev parent reply other threads:[~2014-06-17 2:37 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 [this message]
[not found] ` <mailman.3803.1402972638.1147.help-gnu-emacs@gnu.org>
2014-06-17 3:00 ` Rusi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOEd9jmvdaWYA3ksSwdHOgcbQD02v5o2z9HpwCrJfNrqivrkzA@mail.gmail.com \
--to=tuhdo1710@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbr@arlsoft.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.