My recent experiment with ubeta for Mac seems to
belie the statement below by Chris ... That is, I
find that startup.ijs, while it works neatly in the
IDE, doesn't get loaded during a jconsole start.

I too have had a modified profile.ijs for years as
Henry says below - for many releases, the distributed
profile.ijs file was unchanged. The ubeta was/is
different, so I would really like to move the the
more convenient/approved "startup.ijs" approach.

I tried my experiment in my previous message by not
remembering exactly what Chris said below - which is
that I have to have TWO startup files to replace my
profile.ijs modification - one for jw and another
for jconsole. I have a belief that when you have two
files, they are almost inevitably different... But
happily I could use a symbolic link to solve that.

On the other hand, a true "clean install" as I have
been nattering about in my other messages blows away
the config directory in any case. Largely removing
the convenience of avoiding adding the one line (to
load my own profile additions) near the end of the
distributed profile.ijs ... I think I'll just keep
doing it the way I have in the past. (sigh)

- joey

At 16:10  +0800 2006/08/09, Chris Burke wrote:
Joey K Tuttle wrote:
At 23:01  -0700 2006/07/26, Oleg Kobchenko wrote:

I was trying to say that "startup.ijs" should be called
for console too. And that would make the standard
method too hookup custom code.

In your method, you need to modify profile.ijs or
copy two files. At the same time, startup.ijs is
not installed, thus preserved with new installation.
So no editing or moving is required, or at least
copying of just one file.


I agree - that would be nicer. I would be happy to
call my toolkit "startup.ijs" and set my locale in
it. It is a small nuisence to have to either edit
or check that profile.ijs is unchanged in a new
release. Maybe jsoftware can make this minor change
that would make life easier for jconsole users.

This is done for the next beta.

The normal config file is not read by jconsole, so in this case, the startup script name is hard coded to startup_console.ijs. Put this in your usual config directory, e.g. .../j601/user/config/startup_console.ijs.

The usual name of startup.ijs is not used to avoid conflict with a script that assumes jwd.



At 16:49  -0500 2006/08/23, Kip Murray wrote:
Thanks, Henry!  KM

On Wed, 23 Aug 2006, Henry Rich wrote:

| For years my profile.ijs has contained
|
| buildpublic_j_  0 : 0
| langexten    d:\path\langexten
| utils        d:\trade\utils
| klutils      d:\trade\klutils
| )
|
| and then
|
| load 'utils'
|
| etc. work.  Still seems to work in 6.01.
|
|
| Henry Rich
|
|
| > -----Original Message-----
| > From: [EMAIL PROTECTED]
| > [mailto:[EMAIL PROTECTED] On Behalf Of Kip Murray
| > Sent: Wednesday, August 23, 2006 5:32 PM
| > To: Beta forum
| > Subject: Re: [Jbeta] j601ubeta_linux.tar.gz
| >
| > Every time I download a new version, I edit
| > /system/extras/config/scripts.ijs to include short names for
| > my favorite
| > scripts.
| >
| > Do I have to do it that way?  Is there something I could put in my
| > startup.ijs or a separate file I could put in my user folder
| > to get the
| > same result?
| >
| >    JVERSION
| > Binary: j601binubeta_linux32
| > Library: j601libubeta
| > Help: j601hlpubeta
| > Engine: j601/beta/2006-08-16/22:30
| >
| >
| > Kip Murray
| > Math, UofHouston
| >
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to