From: jmg3000@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: Mouse Scroll.
Date: 30 Mar 2007 07:17:04 -0700 [thread overview]
Message-ID: <1175264224.535035.157820@n76g2000hsh.googlegroups.com> (raw)
In-Reply-To: <1175194133.016299.4670@d57g2000hsg.googlegroups.com>
On Mar 29, 2:48 pm, "Robert Thorpe" <rtho...@realworldtech.com> wrote:
> On Mar 29, 1:57 am, "Daniel" <hanm...@gmail.com> wrote:
>
> > (BTW, why emacs is so hard to use? It is very less intuitive to use.)
>
> Sigh, It's a long story.
Just curious, what do you mean? Seems to me that, for a terminal-based
app, Emacs is pretty easy to use -- you just need to remember or else
look up a number of key-combos. The docs are good, the integrated help
is good. Haven't really tried elisp though.
next prev parent reply other threads:[~2007-03-30 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 0:57 Mouse Scroll Daniel
2007-03-29 18:48 ` Robert Thorpe
2007-03-30 2:42 ` Daniel
2007-03-30 14:17 ` jmg3000 [this message]
2007-04-02 9:55 ` Robert Thorpe
2007-03-30 7:00 ` Thien-Thi Nguyen
2007-04-01 16:20 ` Daniel
2007-03-31 18:40 ` Chris F.A. Johnson
2007-04-01 16:25 ` Daniel
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=1175264224.535035.157820@n76g2000hsh.googlegroups.com \
--to=jmg3000@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).