On 2026-01-16 22:46, noa wrote: > For me, this is /not/ too good to give up; i prefer to use > org-timestamp for timestamp manipulation, and i frequently run into > the issue of trying to shift-select over a timestamp. This led me to > unbind the keys and write about it, which led to Ihor suggesting i > bring this up here. > > However, i think that the third option should not be called 'always > if it does not actually mean that shift-select is always supported. > A better name might be something like 'except-timestamps.
I also find this annoying/inconsistent, and would definitely switch to a version without the timestamp behaviour if it existed. > Assuming 'always cannot be changed for backward compatibility, i > think a new option 'always-always (open to better names) should be > allowed, which does not allow timestamps special privileges. IMHO the breakage is only minor if it keeps 'except-timestamps as an option (and is better than symbols like 'always-for-real-this-time). Best, -- Jacob S. Gordon [email protected] Please don’t send me HTML emails or MS Office/Apple iWork documents. https://useplaintext.email/#etiquette https://www.fsf.org/campaigns/opendocument
