If a project .cmake-build.el has a single run config defined, then cmake-build-run will still refuse to run it without going throughcmake-build-set-config first (which would present two options: "nil" and that sole defined config). IMHO it would follow the principle of least surprise to simply default to that config instead, saving a command invocation.
If a project
.cmake-build.elhas a single run config defined, thencmake-build-runwill still refuse to run it without going throughcmake-build-set-configfirst (which would present two options: "nil" and that sole defined config). IMHO it would follow the principle of least surprise to simply default to that config instead, saving a command invocation.