unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Robert Thorpe" <rthorpe@realworldtech.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Mouse Scroll.
Date: 2 Apr 2007 02:55:11 -0700	[thread overview]
Message-ID: <1175507711.528055.215570@n76g2000hsh.googlegroups.com> (raw)
In-Reply-To: <1175264224.535035.157820@n76g2000hsh.googlegroups.com>

On Mar 30, 3:17 pm, jmg3...@gmail.com wrote:
> 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.

If you want to use it as it comes out of the box then it's very easy
to use, it works like the editors that come with common operating
systems.  It's just much more powerful and has slightly different
keys.  Writing elisp and adding support for new features isn't even
that hard either, if you're OK with learning another language.

There are problems though.  Keymaps currently present a small problem,
since the only way to modify them is through elisp.  This isn't hard
in simple cases but often the exact specifics of how they should be
used are difficult.

Most users I think act like myself when they get a new program, they
use the keys that it uses, another small group of users immediately
start rearranging the keys.  I think the OP is one of this second
group who end up wondering why everything is so hard.  Loads of the
enquiries from newbies on this newsgroup are from trying to rearrange
keys.

All that said, I can't complain, if I was really bothered I'd write
some code to make it simpler.

  reply	other threads:[~2007-04-02  9:55 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
2007-04-02  9:55     ` Robert Thorpe [this message]
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=1175507711.528055.215570@n76g2000hsh.googlegroups.com \
    --to=rthorpe@realworldtech.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).