Why does (defun c:CTTEST ().... run when TEST is run on cmd line?
I don't think there's anything special about the CT -- it's just the fact of TEST1 being a part of that name, and AutoComplete taking over, so that if you hit Enter, it doesn't use just what you typed in, but what among the options offered it has highlighted. Try typing TEST [without the 1], for which I am offered CTTEST1, and WRITESTAT, and, because I have a Hatch pattern called TEST for experiments, to Hatch using that pattern. That latter is the one it had highlighted in the offerings, so that's what I got with TEST {Enter}, even though CTTEST1 was the top of the offerings list [I assume it's alphabetical with command names first and other things like Hatch pattern names after]. I would bet that if you also define a command called just TEST1, you won't get CTTEST1 when you type in TEST1, because the latter should be the primary offering.
Try turning off auto-completing of command names, an option under the -INPUTSEARCHOPTIONS command [which you will get if you type in AutoComplete directly].
Trust me folks, the autocomplete is not on.
I only turn that on when trying to find a command.
My current settings are:
Another interesting thing I found is it only happens for the first defun.
Try this:
(defun c:cttest ()(princ "\nWow"))
run Test, it says wow.
then run:
(defun c:ct-test ()(princ "\nWow"))
type Test, it says unknown function - like it should.
then run:
(defun c:cttest ()(princ "\nWow"))
and run Test, it says unknown function - like it should.
Ok, after I just wrote that, I tried on an OOTB acad profile and am not seeing this bug.
I don't expect you guys too so hold off while I narrow down more.
I did have some things loaded in my test profile like quilpik I should remove.
Ok, after lots of ripping apart company and default acad profiles, I think I got it down to what I consider a bug.
Indeed, the replies to check auto-correct/complete were also my first thought, and I faithfully posted the pic of them off.
But it seems they are not fully off. Note that the "Mid string search" option is greyed but on:
I thought those did not matter as autocomplete and autocorrect are clearly off.
But if I open the options, turn on autocomplete so I can access the mid-string search box, and turn it off as well as autocomplete, the TRAV command does nothing.
I can repeat that easily, and I expect everyone on 2019.1.2 can, and likely all acad versions since maybe 2017.
I don't think adesk considers that a bug, but I would most DEFINITELY call it a bug.
The odd thing is, it only seems to happen on functions the first time they are defined.
I have a .lsp names LinesCurves.lsp, with one function (DEFUN C:CT-TRAVERSE ( / )....
The first time I load that lisp, TRAV runs the function (with the mid string search on).
If I rename the function to (DEFUN C:CT-TRAVERSE1 ( / )....
and reload the lisp, TRAV does nothing now, says unknown command.
If I rename it back to (DEFUN C:CT-TRAVERSE ( / ).... and load, the TRAV does nothing now too.
So the mid string search bug only happens for functions defined in a lisp, the first time that lisp is loaded.
If the function names are the same, reloading it has no effect, the bug happens.
If you rename a function and reload a lisp, it seems to clear the search of functions from that file.
This implies the search knows where stuff came from.
The moral of the story is turn off mid-string search if you don't want it, as simply turning off autocomplete is not enough. thanks for watching, all.
btw, the help is wrong:
I don't doubt its unintentional, but what a process to get to the bottom of it.
