Erlang Development Environment

[Sean Hinde]

Peter,

> An improvement
> would perhaps be the possibility to save the retrieved data 
> (from an update) to
> file so that you don't have to collect the info from scratch 
> every time you
> start the program. I suppose using e.g. dets, it would be 
> quite a quick thing to
> implement?

I agree - it is on the TODO list in the source. The easiest way would be to
just save the list of functions as a term to a file.
 
> While we're on the subject of easy access to documentation... 
> I've sometimes
> found it useful to be able to view Erlang man pages from the 
> Erlang shell. I
> wrote a very simple program the other day that either prints 
> a page to stdout or
> lets you perform some string searching within a page. If 
> anyone's interested
> I'll post it.

That sounds useful. It would also be easy to add a button to get the man
page for the currently selected module in the code_finder (maybe even to
jump to the right function - Hm, that'd be neat).

- Sean



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.