Martin,

One last note about qjide.

I try and support as many J front ends as I can with JOD. The only change
is how the (ed) verb works.  (ed) generates a script and then opens the
appropriate
editor for the front end. I don't know how, or even if it is possible, to
do this
in qjide.

How would you issue a command in the console window that opens one of your
edit windows?

In other ide's

For jqt (ed) places a script in an edit window.
For jhs a link is written to the page that upon clicking opens the JHS
editor

For qjide I get the expected cannot find the file error that (ed) returns
when it cannot handle the case: for example cutting and pasting from  qjide
session.

[J console]

   load 'general/jod'

   od ;:'play utils'
+-+-----------------+----+-----+
|1|opened (rw/ro) ->|play|utils|
+-+-----------------+----+-----+

   dnl 'bone'
+-+----------+
|1|bonebridge|
+-+----------+

   ed 'bonebridge'
+-+-------------------------------------------------+
|0|!JOD error: unable to open TEMP/*.ijs for editing|
+-+-------------------------------------------------+


Thanks John Baker


On Wed, Feb 24, 2016 at 2:02 PM, Herr Martin Saurer <
[email protected]> wrote:

> Dear J’ers
>
> There are updated repositories for qjide and jkernel:
>
> https://github.com/martin-saurer/qjide <
> https://github.com/martin-saurer/qjide>
> https://github.com/martin-saurer/jkernel <
> https://github.com/martin-saurer/jkernel>
>
> What’s new in qjide:
>
> - Bugfix for Win64 (J 64-bit, Python 64-bit)
>   qjide should work now in 64-bit environments (please report if not)
>
> What’s new in jkernel:
>
> - J User Folder does no longer have to be a sub-directory of the J
> installation folder
>
> Cheers
>
> Martin
>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>



-- 
John D. Baker
[email protected]
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to