Got to apply these to your own circumstances.
The < > are just to highlight what is expected so it <Filename> might be replaced be "11"
The second option should work if you replace the details with your specific LISP file name instead of a.lsp. You might need to use double \\ instead of single in the file path
Another alternative is create load of small LISPs in a single file, where the LISP name is what you want, and take away the "c:" prefix from the actual LISP to use - should be fairly fool proof if not the most elegant. Load this file at start-up
(defun c:testthis ( / )
(load "....filepath....\\a.lsp" "a.lsp Failed to Load") ;;Using full path and not variable
(testthis)
)
I think:
(autoload "<fileName>" '("<LISP Name 1>" "<LISPName 2>")) ; where <LISPName x> are LISPs contained in <filename>
The file should be saved in your trusted locations, no need to include the extension '.LSP' I think, might be wrong
(autoload "COPY0" '("COPY0"))
(autoload "COPYCOMMAND" '("ZZZ"))
(autoload "COVER" '("COVER"))
(autoload "DIMFLIP" '("DIMFLIP"))
(autoload "DRAWXFALL" '("DRAWXFALL"))
(autoload "DRAWPIPE" '("DRAWPIPE"))
(autoload "EDITRL" '("EDITRL"))
Load on demand is easy just put in a startup lisp that is automatically loaded.
Thinking some more though easier to put in a menu as an option. Load a lisp with all the defuns in it.
I would make something like type A30 on command line and it runs a lisp that splits the A & 30. Look at attached code it does circles, fillet, offset etc F123 C345. Again load as required, if only every now and then.
fillet reactor.lsp
For Nikon you can not use "." in the value you need to use "-" so F123-45 will work. The "." is a valid character in the input and gets treated different to a decimal point.
So A30 would set the snapang to 30, then ask for pt1 pt2. If you get stuck just ask, can have 26 functions A-Z, C, O & F used.