I'll think about it, but am not too sympathetic. Compare it with a change that was made recently. One feature I use all the time in J is the Input Log dialog. I know I typed something like what I want some time back, and want to recall it rather than retype from scratch. However, one problem with the log was that it was sometimes hard to find the sentence I was looking for, and I often wished for some search capability. It took an hour or so to add that, and now I find the Input Log far easier. It is a noticeable and very satisfying improvement.
However, the config is completely different. For me it is just set and forget. I cannot remember the last time I changed my config, but it must have been at least several months ago. In fact the only times I ever look at the config is in response to a question about it. Moreover, the change to ensure config is reloaded correctly would take several hours work, and would be hard to get right. Essentially, you are asking for this to accomplish something that for me would be of zero benefit. While you say that you would benefit, surely this would be very minor. You are not likely to change the config that often, and I find it hard to credit that you cannot just load another copy of J to check that the changes you have made are successful. In sum, the time/benefit ratio for this change is just not compelling. On 17 August 2015 at 19:14, 'Pascal Jasmin' via Beta <[email protected]> wrote: > restarting is a big deal when you have several files loaded, or even > definitions you did not put in files yet. User keys are awesome, but > especially so for helping me/user do something right now with the > files/definitions loaded right now. The restart step is a bit like > compiling C code to do it, instead of iterating quickly. > > There's also the issue that conflicting key assignments and other "simple" > mistakes in the config file are easy to make, and reloading your "stack" > each time makes a simple utility useful right now if it could be loaded > right now, too tedious to experiment with. > > reloading the entire config, especially if easier, would be fine too. > Trying all the format options for instance is a lot more convenient that > way. > > On another note, I never understood the ctrl-shift up/down modifiers > instead of just ctrl. > > > ----- Original Message ----- > From: chris burke <[email protected]> > To: Beta forum <[email protected]> > Cc: > Sent: Monday, August 17, 2015 9:39 PM > Subject: Re: [Jbeta] new beta > > > To repeat a feature request, > > a way to reload config (even by calling a verb) would be a big help for > using/testing config options. Especially user keys. > > Yes, but as before, I am not too keen on this. I am not at all sure that we > can easily reload all the config, and I don't want to reload only part of > it. > > I am a little surprised at this request. J loads almost instantaneously, so > why not open a config file in a text editor, and load J after making any > change? > > On 17 August 2015 at 16:46, 'Pascal Jasmin' via Beta <[email protected]> > wrote: > > > > You can recall entries by either > > pressing the Ctrl up-arrow and Ctrl down-arrow keys to cycle backwards > and > > forwards through the log > > > > This will double my productivity as soon as I get used to it. > > > > > when saving a new script to a new name, it is added to the recent files > > list > > > > thank you for this. > > > > To repeat a feature request, > > > > a way to reload config (even by calling a verb) would be a big help for > > using/testing config options. Especially user keys. > > > > > > ----- Original Message ----- > > From: chris burke <[email protected]> > > To: Beta forum <[email protected]> > > Cc: > > Sent: Monday, August 17, 2015 7:33 PM > > Subject: [Jbeta] new beta > > > > A new J804 beta is available for Windows, Linux and OSX 64 10.7 and > later. > > Install from www.jsoftware.com/download/j804/install. > > > > This should fix problems reported earlier, and includes an All-In-One > > installer for OSX. We still have a few weeks before making a final > release, > > so feel free to send in any more issues. > > > > For a list of changes, see > > www.jsoftware.com/jwiki/System/ReleaseNotes/J804. > > > > We'd appreciate feedback, either to the beta forum or if specifically on > > Qt, to the qt mailbox group. > > ---------------------------------------------------------------------- > > 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 > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
