all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Filipp Gunbin <fgunbin@fastmail.fm>
To: John Yates <john@yates-sheets.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Casting as wide a net as possible
Date: Mon, 14 Dec 2015 17:41:11 +0300	[thread overview]
Message-ID: <m237v55bzs.fsf@fastmail.fm> (raw)
In-Reply-To: <CAJnXXogJywM4xRM9OEF1RKEwOib_G_JJvj=YThhsUwFn6gHviQ@mail.gmail.com> (John Yates's message of "Thu, 10 Dec 2015 11:46:42 -0500")

On 10/12/2015 11:46 -0500, John Yates wrote:

> I would hope that our site would be not just a self-indulgent
> love fest, a litany of all the things we - the advanced, deeply
> committed users - love about Emacs.  Instead I imagine our site
> as the place where a newbie becomes seduced by Emacs' clearly
> wonderful and unique functionality, available "out of the box".

When I started using Emacs, it attracted me with the ease of working
with codings.  I've tried some editors at that time, of course
(including well-known IDEs, for years), but never before it was so easy
to just open a file in a given coding, or re-open it in another.  We,
non-English-natives, still have problems with different encodings (yes,
KOI8-R, CP-1251 and CP-866 for Russian are still here) and Emacs helped
me to learn more clearly what the encoding is.

Another thing that impressed was set of advanced general text-editing
capabilities (someone mentioned transpose-* functions here) and their
infrastructure, including syntax tables.

These and other things made me sure that, although the my work language
(Java) support is lacking many things IDEs have, Emacs will be my editor
of choice.

Maybe it makes sense to underline this versatility and good accessible
infrastructure in addition to features most users expect to see in an
"ad" for a text editor.

Filipp



  parent reply	other threads:[~2015-12-14 14:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 16:46 Casting as wide a net as possible (was: First draft of the Emacs website) John Yates
2015-12-10 17:31 ` Eli Zaretskii
2015-12-10 18:56 ` Drew Adams
2015-12-10 19:02   ` Casting as wide a net as possible John Wiegley
2015-12-10 19:07     ` Eli Zaretskii
2015-12-10 19:48     ` David Kastrup
2015-12-10 20:01       ` Eli Zaretskii
2015-12-10 20:17         ` David Kastrup
2015-12-10 20:19           ` John Wiegley
2015-12-10 20:50             ` David Kastrup
2015-12-11  7:09       ` Richard Stallman
2015-12-10 19:54     ` covici
2015-12-10 21:21     ` Marcin Borkowski
2015-12-14 13:05     ` Adrian.B.Robert
2015-12-14 16:21       ` raman
2015-12-14 18:21         ` John Wiegley
2015-12-11  7:08 ` Casting as wide a net as possible (was: First draft of the Emacs website) Richard Stallman
2015-12-11 16:14   ` Casting as wide a net as possible raman
2015-12-14 14:41 ` Filipp Gunbin [this message]
2015-12-14 15:01   ` Yuri Khan
2015-12-14 17:20     ` Filipp Gunbin
2015-12-14 17:59       ` Random832
2015-12-14 18:19         ` Yuri Khan
2015-12-15 18:12           ` Filipp Gunbin
2015-12-15 18:54             ` Random832
2015-12-15 19:03               ` Random832
     [not found] <<CAJnXXogJywM4xRM9OEF1RKEwOib_G_JJvj=YThhsUwFn6gHviQ@mail.gmail.com>
     [not found] ` <<fa45f69a-b8df-46f8-8fda-4735dc34e4dc@default>
     [not found]   ` <<m2d1uenn4h.fsf@newartisans.com>
     [not found]     ` <<83a8pi9l6o.fsf@gnu.org>
2015-12-10 19:15       ` Drew Adams

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=m237v55bzs.fsf@fastmail.fm \
    --to=fgunbin@fastmail.fm \
    --cc=emacs-devel@gnu.org \
    --cc=john@yates-sheets.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.
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.