[plt-scheme] Some PLT environment issues
In "guide/More_Libraries.html", there is a reference to a unknown function
"plt-help":
"Run plt-help to find documentation for libraries that are installed on your
system and specific to your user account."
Was it implemented then removed?
Laurent
On Wed, Oct 28, 2009 at 10:06, Laurent <laurent.orseau at gmail.com> wrote:
> I tend to think that everything should be accessible with commands/function
> calls.
> In this way, everything can be automatized and easily reused in different
> situations.
>
> A "help" function/macro as mentioned earlier would be very convenient (at
> least to me).
> For example:
> (help arg) -> (requires header quick-description)
>
> > (help remove-pkg)
> (planet/util)
> (remove-pkg owner pkg maj min)
> "Removes the package from the local repository"
>
> Contracts could be given too probably.
>
> The F1 help could/should also be coded with such function (doesn't it exist
> yet somewhere?):
> (help-open remove-pkg)
> opens the browser to the remove-pkg page. An "I'm feeling lucky" option
> should also be set by default.
>
> Side note: quote-require from cce/scheme returns the definition symbols
> provided by a given package,
> which can probably be useful in such context.
>
> Laurent
>
> On Wed, Oct 28, 2009 at 00:30, Scott McLoughlin <scott at adrenaline.com>wrote:
>
>> Most importantly, on "frob"
>>
>> "The term *Frob* has typically been used to refer to any small device or
>> object
>> (usually hand-sized) which can be manipulated, or *frobbed*. It was
>> adopted by
>> the community of computer programmers which grew out of the MIT<http://en.wikipedia.org/wiki/MIT> Tech
>> <http://en.wikipedia.org/wiki/Tech_Model_Railroad_Club>
>> Model Railroad Club<http://en.wikipedia.org/wiki/Tech_Model_Railroad_Club>in the 1950s.
>> *Frob* is among the oldest existing words in
>> hacker <http://en.wikipedia.org/wiki/Hacker_%28computing%29> jargon, as
>> reported in the Jargon File <http://en.wikipedia.org/wiki/Jargon_File>."
>>
>>
>> Second, regarding adding a "Project" entity to PLT that can be managed, it
>> just
>> seems logical/prudent to me to completely defer secondary UI issues.
>> Instead,
>> all the logic an functionality could be worked out for mzscheme via a
>> relatively
>> simple command line utility (or even a little scheme repl - whatever).
>>
>> The utility could just run emacs or vi or whatever when needed (preferably
>> an
>> editor that can scripts on startup, highlight lines on demand, etc.), run
>> Lynx
>> or Firefox or whatever when needed to view docs, run the subversion
>> command line
>> utility and so on and so forth.
>>
>> This allows for actually building the data structures, organizing them on
>> disk,
>> analyzing the project information and keeping track of *that* and so on
>> and
>> so forth.
>>
>> Any thoughts? Sound like a reasonable first step?
>>
>> Scott
>>
>>
>> Stephen De Gabrielle wrote:
>>
>> Hi,
>>
>> If you feel like making *any* change to the spec, small or large, please
>> feel free.
>> - http://code.google.com/p/projects-project/ (I've added you as a user)
>>
>> (the offer is open to anyone who is interested in adding any project
>> features to DrScheme)
>>
>> Cheers,
>>
>> Stephen
>>
>> PS What is 'frobbing' ?
>>
>>
>>
>> _________________________________________________
>> For list-related administrative tasks:
>> http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20091028/a5580c20/attachment.html>