Paul Bryan <[email protected]> writes: > I get the same behaviour still today. There didn't seem to be a consensus as > to whether this needed to be changed or not. The suggested changed amounts to > something like changing > > `(let ((crm-separator "[ \t]*:[ \t]*"))...)' > > to > > `(let ((crm-separator "[ \t]*[,:][ \t]*"))...)' > > allowing for separators of either : or , when adding tags to a capture. See > the thread for more details, including a patch with the suggested changes. > > There was some discussion about allowing customisation or not, and it seemed > customisation was not favoured. Bastien suggested hard coding the > `crm-separator', presumably similarly as I did above. > > A quick check confirms that the fix works okay. So, is this something that is > wanted? If so, I can submit a patch. If not, I'll cancel the report.
I think we can make separator a variable (not a custom option). This way, if someone absolutely wants to change it, they could. Currently, typing foo,bar in tag setting dialogue will anyway end up being :foo:bar:, so the change is not even breaking. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
