From: Jason Earl <jearl@notengoamigos.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Open Hypspec with w3m
Date: Mon, 31 Jan 2011 21:15:21 -0700 [thread overview]
Message-ID: <87aaiggzl2.fsf@notengoamigos.org> (raw)
In-Reply-To: 87ei7ubx1k.fsf@puma.rapttech.com.au
Thank you (again) very much for responding.
On Sun, Jan 30 2011, Tim X wrote:
[...]
> It never does any harm to ask for pointers and suggestion in this
> group. There are a number of regulars in this group, like Stefan, who
> are active contributors/maintainers of emacs. They have both a wealth
> of information and are aware of current development/improvements in
> emacs.
I really do appreciate the pointers.
[...]
> Note that emacs also has a cl compatibility package (require 'cl). It is
> not a 100% cl compatibility layer, but does bring in some of the useful
> cl functions that are not part of standard elisp. This can be very
> handy. However, you do need to be careful as there are significant
> differences between elisp and cl (I use to constantly get confused!).
>
> Practicle common lisp is a good text. I also found Paradigms of
> Artificial Intelligence really good (don't be put off by the reference
> to AI, it has a lot of really good lisp stuff). ANSI Common Lisp is
> also quite good and while it took a couple of goes, On Lisp is really
> good once you get to the point where you want to start getting to
> grips with macros in a serious manner. Although somewhat criticised, I
> also found Let Over Lambda an interesting read.
Thanks for the advice. It certainly does help to know what to study
next.
[...]
>> I hate to admit it, but I basically use Emacs because it was basically
>> the only tool around when I first started using Linux. I got used to
>> it, and even for pure end users it is a pretty impressive tool. Now
>> that I am beginning to see it as a learning tool/development environment
>> I am a little surprised it is not more popular ;).
>>
>
> Yes. A similar situation. I came from vi to emacs (I started with old
> Unix systems long before Linux). However, due to some bad luck, I lost
> my sight and at the time (mid 90s) the only good interface on Linux
> for blind users was emacs and an extension package called emacspeak,
> which uses defadvice a lot to add speech support. The learning curve
> was very steep at first and emacs seemed very alien compared to the
> vi. However now I am very much at home with it. Last year, after over
> 15 years, I was lucky enough to get a considerable amount of sigh
> back, but even though I could go back to using vi, I've been totally
> sucked in by the power and flexibility of emacs.
I am glad that you got (most of) your sight back. I want to use phrases
like eye-opening or enlightening, but I do not want you to think that I
am making the obvious bad pun.
> There are frequent arguments/debates in this group regarding emacs'
> failure as an IDE. I think the critics are possibly missing the main
> point. While other IDEs, like eclipse or visual studio etc, may offer
> lots of great features and do so pretty much out of the box, you still
> need to very much structure your workflow to fit the tool. For me,
> emacs has the advantage of allowing me to structure the tool to fit
> with my preferred workflow, plus I can do most of my development
> related tasks which are not strictly speaking coding, with it as
> well. I find the combination of org-mode, the various development
> modes, vcs, w3m and mail all being within one tool, emacs, incredibly
> useful. I have built up a toolbox of handy and useful bits of elisp
> and collected even more from posts to this and other groups. I really
> like the fact that all my important stuff is in plain text format and
> managed under version control. For the last year or so, I've been
> making increasing use of org-mode. It has revolutionised how I work
> . A mode I cannot recommend highly enough for any emacs user.
I have high hopes that with the inclusion of CEDET that Emacs can start
making progress on the IDE front. I basically feel the same way about
Emacs as you do. I've used Eclipse and Netbeans, and I did not like
them, even for Java development. Sure, there were some things that they
did *much* better than Emacs, but mostly they just seemed to get in the
way.
I've played a bit with CEDET's EDE, however, and it was definitely cool
to build Autoconf projects from Emacs. Eventually I really would like
to be able to help move things forward.
Jason
next prev parent reply other threads:[~2011-02-01 4:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 19:29 Open Hypspec with w3m Jason Earl
2011-01-28 23:00 ` Tim X
2011-01-28 23:33 ` Jason Earl
2011-01-28 23:58 ` [SOLUTION] " Jason Earl
2011-01-29 2:36 ` Stefan Monnier
2011-01-29 17:04 ` Jason Earl
2011-01-28 23:05 ` Stefan Monnier
2011-01-29 0:29 ` Jason Earl
2011-01-29 2:37 ` Stefan Monnier
2011-01-29 17:06 ` Jason Earl
2011-01-29 22:53 ` Tim X
2011-01-30 4:05 ` rusi
2011-01-30 14:47 ` Perry Smith
[not found] ` <mailman.10.1296398854.11759.help-gnu-emacs@gnu.org>
2011-01-30 15:11 ` Krzysztof Bieniasz
2011-01-30 15:45 ` Open Hypspec with w3m (morphed into keyboards, etc) Perry Smith
[not found] ` <mailman.15.1296402359.11759.help-gnu-emacs@gnu.org>
2011-01-30 16:34 ` Krzysztof Bieniasz
2011-01-30 16:35 ` Krzysztof Bieniasz
2011-01-30 16:38 ` Krzysztof Bieniasz
2011-01-30 5:06 ` Open Hypspec with w3m Jason Earl
2011-01-30 8:44 ` Tim X
2011-02-01 4:15 ` Jason Earl [this message]
2011-02-01 12:33 ` rusi
2011-02-01 21:15 ` Tim X
2011-02-01 22:44 ` Current Emacs Development (was: Open Hypspec with w3m) Jason Earl
2011-02-02 4:25 ` Current Emacs Development Stefan Monnier
2011-02-02 5:58 ` Jason Earl
2011-02-04 23:33 ` Open Hypspec with w3m Andy Moreton
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=87aaiggzl2.fsf@notengoamigos.org \
--to=jearl@notengoamigos.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.
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.