From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Help for eclipse
Date: Wed, 11 Jun 2014 16:16:42 +0200 [thread overview]
Message-ID: <871tuvttth.fsf@debian.uxu> (raw)
In-Reply-To: 2cfe5201-407a-4f80-a6de-6ff3dc7d4382@googlegroups.com
adrians <nmanole@gmail.com> writes:
> Emanuel, so based on your extensive experience with
> Eclipse it's a total pain?
I don't need extensive experience with Eclipse to know
it sucks. I have very specific and well-defined
parameters for what makes for good software. I can use
just about any application and instantly know if it is
software that "is me" or not.
> Right. I can tell you from having used if for a heck
> of a lot longer than you used it for that, configured
> with the proper settings, it can be significantly
> snappier than Emacs - at least under Windows.
Snappy on Windows - isn't that a contradiction in
terms?
> In fact the general clunkiness of Emacs' scrolling
> still bothers the heck out of me.
(setq scroll-conservatively 10000)
(setq auto-window-vscroll nil)
Emacs is programmable - more on scrolling (one line at
a time or in panes; left-to-right; etc.): [1]
> As for which of these two environments is easier to
> get accustomed to for someone new to them, please
> don't suggest that it's Emacs.
I don't care for new users that are negativistic about
it. I was a new user once as well and while I read two
books I used Emacs simultaneously and every day made
improvements - to Emacs (as I saw it), and to my own
understanding of it (and those two qualities are not
easily separable after a while) - and never did I
feel it was unpleasant or burdensome - the only thing I
regret was being a bit too public about it, so people
got expedition fever, and I didn't understand that, and
got into some flame wars. Well, hell. Other than that,
configuring/programming Emacs and learning Lisp was a
wonderful experience, and I'm happy every day that I
have a system which is to 95% exactly what I want.
> For years now, Eclipse has had straightforward UI
> discoverability through the use of Ctrl-3 which
> allows you to search through all commands, views,
> menus, etc., from one spot.
Menus! - why don't you go use Finder if you like menus
so much? (But there are GUI menus in the X version of
Emacs, so that shouldn't be a problem for you if you
really want them.) As for online help that's very
elaborate in Emacs with the the dynamic docstring system
that lets you add documentation at the same place as
the code, and where documentation becomes instantly
available at the moment that code is made available.
> Just to be clear, I'm not contesting Emacs' greater
> extensibility and power overall, just your statement
> that Eclipse is "a pain" and, by implication, that
> Emacs is not, from a noob's perspective.
Emacs is much better in every aspect than Eclipse but I
don't think there is any implication at work.
[1] http://user.it.uu.se/~embe8573/conf/emacs-init/scroll.el
--
underground experts united:
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2014-06-11 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 21:20 Help for eclipse edu500ac
2014-06-10 23:55 ` Emanuel Berg
2014-06-11 2:55 ` adrians
2014-06-11 14:16 ` Emanuel Berg [this message]
2014-06-13 2:12 ` Rusi
2014-06-13 2:57 ` adrians
2014-06-13 3:02 ` Rusi
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=871tuvttth.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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).