4!:3 list files loaded by 0!:x only. Cfg files may not be j scripts. Files loaded using 2!:x are not listed and not a bug. Qtide can load and parse cfg files without involving j engine.
On Jan 24, 2018 4:42 AM, "Eric Iverson" <[email protected]> wrote: > You are right and that is a good point. When 4!:3 was invented we didn't > use cfg files. This is perhaps a low level bug that should be investigated > and fixed one day. > > On Tue, Jan 23, 2018 at 1:42 PM, Raul Miller <[email protected]> > wrote: > > > I do not see the .cfg files listed when I use 4!:3'' > > > > -- > > Raul > > > > > > On Tue, Jan 23, 2018 at 1:33 PM, Eric Iverson <[email protected]> > > wrote: > > > 4!:3'' gives similar info more directly and portable. > > > > > > On Tue, Jan 23, 2018 at 1:29 PM, Raul Miller <[email protected]> > > wrote: > > > > > >> Ah, here's an osx approach (beware line wrap on all of this, of > course): > > >> > > >> $ :|2>/dev/null sudo dtrace -n 'syscall::open*:entry { > > >> printf("%s",copyinstr(arg0)); }' -c Applications/j64-806/bin/jconsole > > >> | awk '{print $4}' | egrep -v dylib | grep 'j.*\.' | uniq > > >> /Users/rauldmiller/Applications/j64-806/bin/profile.ijs > > >> /Users/rauldmiller/Applications/j64-806/bin/../system/util > > >> /Users/rauldmiller/Applications/j64-806/bin/profilex.ijs > > >> /Users/rauldmiller/Applications/j64-806/.jprofile.ijs > > >> /Users/rauldmiller/Applications/j64-806/system/util/boot.ijs > > >> /Users/rauldmiller/Applications/j64-806/system/main/stdlib.ijs > > >> /Users/rauldmiller/Applications/j64-806/system/util/scripts.ijs > > >> /Users/rauldmiller/Applications/j64-806/system/main/regex.ijs > > >> /Users/rauldmiller/Applications/j64-806/system/main/task.ijs > > >> /Users/rauldmiller/Applications/j64-806/system/util/configure.ijs > > >> /Users/rauldmiller/Applications/j64-806/system/config/base.cfg > > >> /Users/rauldmiller/Applications/j64-806/user/config/base.cfg > > >> /users/rauldmiller/applications/j64-806/user/config/folders.cfg > > >> /users/rauldmiller/applications/j64-806/system/config/folders.cfg > > >> /users/rauldmiller/applications/j64-806/user/config/recent.dat > > >> /users/rauldmiller/applications/j64-806/system/config/version.txt > > >> /users/rauldmiller/applications/j64-806/bin/installer.txt > > >> /users/rauldmiller/applications/j64-806/user/config/startup.ijs > > >> > > >> Thanks, > > >> > > >> -- > > >> Raul > > >> > > >> On Tue, Jan 23, 2018 at 12:59 PM, Alex Shroyer <[email protected]> > > wrote: > > >> > This was on MacOS 10.12.6; thanks for the advice. > > >> > > > >> > On Tue, Jan 23, 2018 at 12:13 PM, Raul Miller < > [email protected]> > > >> wrote: > > >> > > > >> >> Which OS are you working under? > > >> >> > > >> >> I threw a j install on a fresh ubuntu 16 machine and looked the > > >> >> startup files j was opening: > > >> >> > > >> >> $ :|strace -e trace=open /usr/bin/ijconsole 2>&1 | egrep -v > > >> >> 'DIRECTORY|\.so\.' | egrep '^open.".*j.*"' | cut -f2 -d'"' | uniq > > >> >> /etc/j/8.06/profile.ijs > > >> >> /etc/j/8.06/profilex.ijs > > >> >> /home/ubuntu/.jprofile.ijs > > >> >> /usr/share/j/8.06/system/util/boot.ijs > > >> >> /usr/share/j/8.06/system/main/stdlib.ijs > > >> >> /usr/bin/libjqt.so > > >> >> /usr/share/j/8.06/system/util/scripts.ijs > > >> >> /usr/share/j/8.06/system/main/regex.ijs > > >> >> /usr/share/j/8.06/system/main/task.ijs > > >> >> /usr/share/j/8.06/system/util/configure.ijs > > >> >> /usr/share/j/8.06/system/config/base.cfg > > >> >> /home/ubuntu/j64-806-user/config/base.cfg > > >> >> /home/ubuntu/j64-806-user/config/folders.cfg > > >> >> /usr/share/j/8.06/system/config/folders.cfg > > >> >> /home/ubuntu/j64-806-user/config/recent.dat > > >> >> /usr/share/j/8.06/system/config/version.txt > > >> >> /home/ubuntu/j64-806-user/config/startup.ijs > > >> >> /home/ubuntu/j64-806-user/break/7015.default > > >> >> > > >> >> If I were concerned with what .cfg files were relevant, on the > > >> >> machine, I think I'd start my investigation with something like > this. > > >> >> > > >> >> Good luck, > > >> >> > > >> >> -- > > >> >> Raul > > >> >> > > >> >> On Tue, Jan 23, 2018 at 11:25 AM, Alex Shroyer <[email protected] > > > > >> wrote: > > >> >> > Thanks Raul! That is exactly what I wanted. > > >> >> > > > >> >> > I played with this a bit and eventually realized that changes to > > >> >> > "~/j64-805/system/config/base.cfg" were having no effect. > > >> >> > Instead I made my changes inside "~/j64-805-user/config/base. > cfg". > > >> >> > > > >> >> > Cheers, > > >> >> > Alex > > >> >> > > > >> >> > > > >> >> > On Tue, Jan 23, 2018 at 11:13 AM, Raul Miller < > > [email protected]> > > >> >> wrote: > > >> >> > > > >> >> >> 9!:37 lets you set that width, it's documented on J's global > > settings > > >> >> >> foreign page: http://www.jsoftware.com/help/ > dictionary/dx009.htm > > >> >> >> > > >> >> >> But also keep in mind that jconsole is a rather minimal > > environment. > > >> >> >> If you want deeper OS bindings, that can be a bit of work. > > >> >> >> > > >> >> >> I hope this helps, > > >> >> >> > > >> >> >> -- > > >> >> >> Raul > > >> >> >> > > >> >> >> > > >> >> >> On Tue, Jan 23, 2018 at 11:09 AM, Alex Shroyer < > > [email protected]> > > >> >> wrote: > > >> >> >> > When the console is wider than some number of characters, the > J > > >> >> >> interpreter > > >> >> >> > writes "..." before printing the next line. > > >> >> >> > > > >> >> >> > But my terminal is narrower than this, so I end up with ugly > > line > > >> >> >> wrapping > > >> >> >> > in addition to the ellipses. > > >> >> >> > > > >> >> >> > Is there a way to adjust the width at which the J terminal > > prints > > >> the > > >> >> >> "..."? > > >> >> >> > It seems that if I was able to tell J to make its lines > shorter, > > >> then > > >> >> I > > >> >> >> > would be able to avoid the line wrapping problem. > > >> >> >> > > > >> >> >> > Thanks, > > >> >> >> > Alex > > >> >> >> > ------------------------------------------------------------ > > >> >> ---------- > > >> >> >> > 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 > > >> ------------------------------------------------------------ > ---------- > > >> 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
