I can't really see anyone disagreeing with this... Apart from Henry's item 0, it's how prettyprint behaves (Edit > Format Script) and I see Henry's Syntax Check as analogous.
In fact I trawled through jijs.ijs making my recommendations, and subsequently discovered they were exactly how prettyprint works. On Wed, Sep 5, 2012 at 1:50 AM, Henry Rich <[email protected]> wrote: > OK, I changed the menu to make the Ctrl-1 key available (will not be > available for a little while, whenever Chris rebuilds the base). > > The lint menu becomes available for any window created AFTER you load lint. > So if you do > > load 'debug/lint' > > you'll have it for scripts opened thereafter. But I assumed that any lint > user would load it during startup, as you ended up doing. > > Yes, it's a shy facility! I was reluctant to make a change that would > surprise anybody. But I like your idea, which I will repeat as > > 0. Make the menu line visible if ~addons/debug/lint/lint.ijs is found > 1. Make the menu line enabled for IJS > 2. If the menu line is selected, require 'debug/lint' before running lint > > > I'm willing to do this, but not without general agreement. Does this sound > OK, guys? > > Henry Rich > > > > > On 9/4/2012 8:32 PM, Ian Clark wrote: >> >> Very nice, Henry. >> >> May I offer some suggestions to gild the lily? Sorry if there's too >> much detail here. It's meant to clarify my meaning, rather than try to >> tell you what you'll know even better than I do. >> >> I'm running on a Macintosh, so what I say may not be quite the >> behavior under Windows, but here goes... >> >> This is a very "shy" facility, and IMO it will be easily overlooked by >> a casual user. I had to read the code in ~system/extras/util/jijs.ijs >> to find out how to make the said menu item appear. >> >> I was only able to do so by inserting the line: >> >> load 'debug/lint' >> >> in my startup.ijs. It didn't work to enter the above line in the session >> window. >> >> Even then, I could only see the new menu item: Run > Window and Syntax >> Check (Ctrl+1) when a script was opened in an IJS window and the >> window was uppermost (=selected). >> >> AFAICS the script jijs.ijs sets a flag "nolint" by detecting the >> presence of the verb: lint_lint_ . >> I suggest instead setting "nolint" by detecting the presence of the >> script: ~addons/debug/lint/lint.ijs . >> If the script is present, configure the Run menu to show "Window and >> Syntax Check" all the time, but grayed out unless an IJS window is >> open and selected. >> ...In fact, more like the behavior of menu item "editlint": Edit > >> Format Script ⌘L >> >> If the menu item: Run > Window and Syntax Check is selected, only then >> load lint.ijs, so the _lint_ locale is only present if required. I >> guess this can be done by having the verb: "runlint" execute: >> require 'debug/lint' >> just before the "runimmx1" sentence. >> ...Again, much as is done in verb: "lint" -the prettyprinter which >> runs when "editlint" is selected. >> >> And BTW the "runlint" entry in noun: JIJSMAC needs to be: >> menu runlint "Window and Syntax &Check" "Ctrl+1" "" ""; >> instead of: >> menu runlint "Window and Syntax &Check (Ctrl+1)" "" "" ""; >> This then shows correctly in the Run menu on the Mac as: >> Window and Syntax Check ⌘1 >> and the shortcut ⌘1 (=Maccy name for hotkey) then works okay (at least >> it does for me). >> >> Ian >> >> >> >> On Thu, Aug 30, 2012 at 11:57 PM, Henry Rich <[email protected]> wrote: >>> >>> In the latest J602 base library, if you have lint installed, you will get >>> a >>> Run menu option to run lint on the current window. Ctrl-1 is the >>> shortcut >>> for this action. >>> >>> Henry Rich >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
