I never do this, but this is exceptional.
I have come across a lot of IDE's and development tools in my 20 years of development but this one takes the biscuit. This product couldn't be farther from production ready. It is just so fundamentally broken from the top down, inside out, every which way. This post will hopefully save some other poor developer from the same time loss I just incurred.
1) The debugger systematically times out. I changed xserver over to exceed having heard that mentioned by somebody as a solution. No improvement. Debugger unusable.
2) The editor just cannot handle it. The most basic changes in the source causes the indexer to go nuts under the covers. It ultimately hangs, giving up, starting again, giving up, restarting. The IDE is blocked most of the time and I'm sitting there like a tulip waiting for control to be given back to me. Editor unusable when refactoring/moving code/changing code.
3) Even the shortcut keys to find in file mess up when you type too fast... the word/string you're looking for gets inserted into the source file. Editor flaky.
4) The console window is just so unbelievably slow it should be shut down/removed immediately. console window flaky.
5) Unless I have read wrong, the output of build has to go into a Clion "Debug" directory, which doesn't suit me at all. I ended up having a clion build and a "real" build side by side. Thats just wrong. Build possibly flaky.
The marketing is brilliant. The video/demo is brilliant. The svn integration is excellent. The rest.... bin it! Why not put it back into serious development and release a "working" version in 6 months. You have a wonderful opportunity to get into the market where eclipse/kdevelop even xcode and visual studio (though try beat their debugger and I WILL pay money) have a very strong foothold. You are blowing it. It simply isn't production ready. If it did what was advertised it could be awesome.
There is no way in earth I would ever every conceive of paying money for this "tool". Make it do what it says on the tin and I would consider re-evaluating it. For info, I have ALWAYS coded in an IDE (including codeblocks where eclipse wasn't available on Linux). I always had a bit of teething problems but always managed to get the IDE's debugger (gdb ultimately) working. It cost me a day or two fiddling but it always worked. I've wasted more than a week on this and its time down the toilet. I have spent the last two days using gdb with -tui option, installing and running vim over ctags with a few svn scripts from colleagues.... I'm up and running. I don't think I'll go back to an IDE (well maybe xcode on mac or visual studio on windows as they are really good products).
Sorry to rant like this but its not frustrating, its vexing. There are surely a team of gifted java developers working behind the scenes on that product but something, somewhere (someone!) along the Clion development food chain needs to take a look at how they are doing their job and consider the extensive negative feedback you can find on Clion via google. The marketing team can keep their jobs BTW, they are excellent :)
Anyways, sorry to be so negative but its an honest opinion from somebody thats been around more than a year or two and wanted the IDE to work.
An no, I'm not opening support tickets :)