Hi, Having a semantic entry in the menus when they did not setup the embedding db might be confusing to users, and will cause errors when they try to use it.
Here is what I propose: I'll make the menu entries run-time dependent on the existence of the "sem_venv" parameter in the configuration (should have done this already). I'll also make the setup option default to true, so the next release will have the the semantic query C++ code enabled without impacting people who do not use the function. There will be no need for a rules file change. This will happen soon, in the next minor release, as all it does is include a small amount of GUI code on the C++ side. Also, I'd be very interested to know what you find this function useful for ? jf John Goerzen writes: > Source: recoll > Version: 1.43.12-1 > Severity: wishlist > > Hi, > > Over at https://www.recoll.org/pages/recoll-semantic.html, semantic search in > recoll is possible if -Dsemantic=true is added to the meson setup comment (as > others are in debian/rules). > > My read of the situation is that this causes no change for people that don't > explicitly use the semantic features. > > > > -- System Information: > Debian Release: 13.3 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, > 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.12.63+deb13-amd64 (SMP w/16 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled
