From: Edward Dodge <someone@somewhere.org>
To: help-gnu-emacs@gnu.org
Subject: Re: OT -- An extremely dumb curiosity question?
Date: Tue, 13 Feb 2007 23:49:15 -0700 [thread overview]
Message-ID: <m27iul44k4.fsf@Mac-Mini.local> (raw)
In-Reply-To: mailman.4182.1170951157.2155.help-gnu-emacs@gnu.org
> Hi;
>
> What are all you people doing with emacs ?
Virtually everything. Here are my favorites:
1) USENET (Gnus)
2) e-mail (Gnus)
3) file management (dired)
4) LISP development (SLIME)
5) Notes & Journals (text/flyspell-mode)
6) General scripting and markup in Perl/sh/html/LaTeX
7) & Sometimes IRC (ERC)
<snip>
> the point of my question is i use emacs to write an occasional bash
> script or a small c program. i screw around with beginners level
> lisp and watch things not work. but as i read the posts on the
> mailing list it is obvious emacs is being used for much much more.
There are four key things to remember about Emacs:
1) EMACS IS A CLASSIC. It has withstood the test of time. It has been
here for years and it will be here for years hence. What you learn
today will help you in the future.
2) EMACS IS FREE. You aren't on somebody else's $$$-upgrade treadmill
with Emacs. And because of the GNU liscence this versatile editor
is one of the most ubiquitous computer tools out there.
3) EMACS RUNS ON EVERYTHING. I first learned to use it in 1998 at
work, when I was on an old RS6000. Since then I've used it on a
Sun, an HP, a PC with Linux, a PC with Windows, "Classic" Mac OS,
and now I use it on a Mac with OSX.
4) EMACS IS AN INGENIOUS TOOL. You are only limited by your
imagination and your desire. Sure the learning curve is steep,
but reasons 1), 2), & 3) make sure you aren't always aiming at a
moving target.
> Sometimes it seems it has replaced the Gnome or KDE desktop.
> Outside of programming, I am having trouble imagining why people
> would use it. Do you use it full screen all the time; only in a
> terminal or a virtual terminal? Is it the only program you have
> running at start up with everything else being done by command line?
I learned the Emacs text-editing commands and their associated
bind-keys well, including a few bindkeys for dired. And I keep Emacs
open all the time in its own window, not in the terminal. In fact,
using Emacs on OSX keeps me out of the terminal for all but the most
complicated command-line sequences.
> I ask here because none of my friends have any idea what I am
> talking about.
Welcome to the club! ;)
> This is a casual chatty question not to be taken too seriously, but
> if some of you are taking a break from your real work, I would be
> really interested in knowing just what people really do with it.
> Emacs I mean.
Good question. Hope you got some good ideas here in gnu.emacs.help.
--
Edward Dodge
next prev parent reply other threads:[~2007-02-14 6:49 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4182.1170951157.2155.help-gnu-emacs@gnu.org>
2007-02-08 16:56 ` OT -- An extremely dumb curiosity question? Tyler Smith
2007-02-08 17:27 ` Pascal Bourguignon
2007-02-08 23:47 ` thorne
2007-02-08 23:30 ` Joost Kremers
2007-02-08 23:48 ` Pascal Bourguignon
2007-02-08 23:56 ` Joost Kremers
2007-02-11 12:02 ` Tim X
2007-02-11 15:20 ` William Case
2007-02-11 15:55 ` William Case
[not found] ` <mailman.4346.1171209373.2155.help-gnu-emacs@gnu.org>
2007-02-11 21:23 ` Tim X
2007-02-11 11:53 ` Tim X
2007-02-08 17:33 ` Hadron
2007-02-08 21:28 ` Robert D. Crawford
2007-02-09 3:50 ` Rjjd
2007-02-09 17:26 ` Robert Thorpe
2007-02-10 9:53 ` Eli Zaretskii
[not found] ` <mailman.4289.1171101235.2155.help-gnu-emacs@gnu.org>
2007-02-10 17:00 ` Galen Boyer
2007-02-11 12:13 ` Tim X
2007-02-12 8:29 ` Robert Thorpe
2007-02-11 11:34 ` Tim X
2007-02-14 6:49 ` Edward Dodge [this message]
2007-02-08 15:45 William Case
2007-02-08 16:24 ` Leo
2007-02-08 16:51 ` CHENG Gao
2007-02-08 17:00 ` ken
2007-02-08 17:33 ` CHENG Gao
2007-02-12 0:51 ` Matthew Flaschen
2007-02-08 22:41 ` Lennart Borgman (gmail)
2007-02-09 15:59 ` Eli Zaretskii
2007-02-09 16:19 ` Juanma Barranquero
2007-02-09 16:32 ` Eli Zaretskii
2007-02-09 16:40 ` Juanma Barranquero
2007-02-10 9:44 ` Eli Zaretskii
2007-02-09 16:26 ` CHENG Gao
[not found] ` <mailman.4238.1171037993.2155.help-gnu-emacs@gnu.org>
2007-02-09 18:25 ` Pascal Bourguignon
2007-02-10 1:28 ` Juanma Barranquero
[not found] ` <mailman.4266.1171070942.2155.help-gnu-emacs@gnu.org>
2007-02-10 11:46 ` Pascal Bourguignon
2007-02-10 15:07 ` Juanma Barranquero
2007-02-10 16:47 ` Tassilo Horn
2007-02-10 19:55 ` Juanma Barranquero
[not found] ` <mailman.4314.1171137338.2155.help-gnu-emacs@gnu.org>
2007-02-10 23:53 ` Tassilo Horn
2007-02-11 0:54 ` Juanma Barranquero
[not found] ` <mailman.4328.1171155290.2155.help-gnu-emacs@gnu.org>
2007-02-11 7:04 ` Hadron
2007-02-11 14:29 ` Juanma Barranquero
[not found] ` <mailman.4234.1171036785.2155.help-gnu-emacs@gnu.org>
2007-02-09 17:58 ` Mathias Dahl
[not found] ` <mailman.4193.1170953922.2155.help-gnu-emacs@gnu.org>
2007-02-09 17:54 ` Mathias Dahl
2007-02-11 9:07 ` CHENG Gao
[not found] ` <mailman.4331.1171184841.2155.help-gnu-emacs@gnu.org>
2007-02-12 7:00 ` Mathias Dahl
2007-02-12 9:14 ` CHENG Gao
[not found] ` <mailman.4376.1171271700.2155.help-gnu-emacs@gnu.org>
2007-02-12 13:41 ` Mathias Dahl
2007-02-10 2:37 ` mkeller
2007-02-10 8:28 ` Tom Rauchenwald
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=m27iul44k4.fsf@Mac-Mini.local \
--to=someone@somewhere.org \
--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).