Re: [O] Should org-complete-tags-always-offer-all-agenda-tags be documented in the manual? [was: Tag completion does not work well with ...]

2018-05-19 Thread Nicolas Goaziou
Hello, alain.coch...@unistra.fr writes: > My reasoning was that, at section "6.2" and upon sequential reading, > the user does not really know what agenda files are yet. I was hoping > that the excerpt: > > ‘C-c a m (org-tags-view)’ >Create a global list of tag matches from all

Re: [O] Should org-complete-tags-always-offer-all-agenda-tags be documented in the manual? [was: Tag completion does not work well with ...]

2018-05-17 Thread Alain . Cochard
Nicolas Goaziou writes on Wed 16 May 2018 22:12: > > Consider this excerpt from section "6.2 Setting tags": > > > > Org supports tag insertion based on a _list of tags_. By > >default this list is constructed dynamically, containing all tags > >currently used in the buffer.

Re: [O] Should org-complete-tags-always-offer-all-agenda-tags be documented in the manual? [was: Tag completion does not work well with ...]

2018-05-16 Thread Nicolas Goaziou
Hello, alain.coch...@unistra.fr writes: > In general, though, I still feel it would make sense to document it, > especially considering that other ways than the default are already > documented. Consider this excerpt from section "6.2 Setting tags": > > Org supports tag insertion based on