From: Yuri Khan <yuri.v.khan@gmail.com>
To: MBR <mbr@arlsoft.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
Tu Do <tuhdo1710@gmail.com>
Subject: Re: I wrote a mini manual for Emacs
Date: Tue, 17 Jun 2014 10:59:30 +0700 [thread overview]
Message-ID: <CAP_d_8XVHaY3LDrfCWzRnG_dTq-cQe6Mne_vd8LEgJicOqgdFw@mail.gmail.com> (raw)
In-Reply-To: <539F334B.7080006@arlsoft.com>
On Tue, Jun 17, 2014 at 1:11 AM, MBR <mbr@arlsoft.com> wrote:
> 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.
It’s more than that — it’s a software development environment
development environment, and sometimes even a software (development
environment)^3 :)
next prev parent reply other threads:[~2014-06-17 3:59 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
2014-06-17 3:59 ` Yuri Khan [this message]
[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=CAP_d_8XVHaY3LDrfCWzRnG_dTq-cQe6Mne_vd8LEgJicOqgdFw@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbr@arlsoft.com \
--cc=tuhdo1710@gmail.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.