@atgeirr 
> While I don't immediately see why EclipseKeyword need to be made noncopyable

it does not hurt if it is (I haven't checked, maybe the compiler generates the copy/move constructors implicitly). I was more referring to the comment before this constructor...

@blattms 
> In my view (and the standard's) a class is move constructable already if it is copy constructable. Therfore I would normally expect that it also supports copying (an exception may be classes where this is _really_ expensive).

I suppose it will currently copy constructible in the "compiler won't complain" sense. But given the fact that the default copy constructor just copies an object's memory one-to-one, the destructor will be called twice for the same ERT handle which will probably lead to weird crashes. (haven't checked that either, though.)