I've done some searching but have not found anything like the problem I am experiencing.

first some facts: Draftsight 2018 SP1, intel x64 processor, Dell 7710. windows 10 pro, version 1709, OS Build 16299.125

This problem existed in 2018 sp0 as well, but i have upgraded to make sure there hadn't been a fix. I have 2018 sp0 on another machine and it is not exhibiting this problem.

I have trouble with entering typed commands. using just the built in shortcuts with no customization, I have a problem where I enter a command but the previous command executes instead. it may do that 2 or 3 times before the entered command runs. most often happens after I type E and a spacebar for Delete. it lets me delete, but if I try to say draw a line using L and spacebar, I get Delete again. worse when it happens that I delete something and then want to undo. it keeps trying to delete. I can't keep track of what was undone and what wasn't.

2017 didn't act this way, no free version that I ever used before worked this way, but now that I have a paid version and have updated it, the problem has arisen.

I have turned off auto completion, i've changed the delay time

I saw a post somewhere about some commands need an extra enter at the end, but that isn't really the case with the problems I have the most. Even when I esc. twice before trying to draw a line, I still get the previous delete command. the problem is not restricted to just the command examples I have given. I have problems with just about any command entered. working from the toolbars or ribbon work fine.

Now, for a good natured heads-up: i'm a very old cad dog here. been using Autocad since Release 11 (not 2011. release 11). not as old as some, but its a respectable run. command line is life. if i'm in cad, i'm using a command line. when I use Solidworks, I don't have the problem with toolbars or ribbon. 2d CAD is wrong without the command line. lets not entertain the idea that switching to toolbars or ribbon is an *acceptable* solution in this case. ;)

I want to think this started after a recent Windows Update, but I am not sure because I had just resigned myself to wrestling with it.

I have changed keyboards, but it has not solved the problem.

Thanks.