Bug: doc string incorrect in org-icalendar-exclude-tags [8.3.2 (release_8.3.2-1-g115c4b @ /home/james/src/org-mode/lisp/)]

Bug: doc string incorrect in org-icalendar-exclude-tags [8.3.2 (release_8.3.2-1-g115c4b @ /home/james/src/org-mode/lisp/)]

[james]

I've been trying to sort out the icalendar export bits. I've noticed the
docstring of (org-icalendar-exclude-tags) states that the tag can be set
with the ICAL_EXCLUDE_TAGS keyword. (it doesn't work). However in the
code of (org-export-define-derived-backend), the :exclude-tags of
:options-alist uses "ICALENDAR_EXCLUDE_TAGS". The does work as a file
level keyword.

In an org file:

#+ICAL_EXCLUDE_TAGS: NOICAL


* Headline to not export                 :NOICAL:

(org-icalendar-combine-agenda-files) any dates in the headline are
exported to the ics file.

But instead:

#+ICALENDAR_EXCLUDE_TAGS: NOICAL

* Headline to not export                   :NOICAL:

(org-icalendar-combine-agenda-files) does not export any dates in the
headline to the ics file.

Could the docstring be updated to say "ICALENDAR_EXCLUDE_TAGS"? It may
save confusion for the next person looking at this.

Thanks.

Oh, and I realize I'm not on the HEAD, but

~/src/org-mode (stable) $ git diff origin/HEAD -- lisp/ox-icalendar.el 
~/src/org-mode (stable) $ 


Emacs  : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.16.4)
 of 2015-06-28 on trouble, modified by Debian
Package: Org-mode version 8.3.2 (release_8.3.2-1-g115c4b @ /home/james/src/org-mode/lisp/)
Sent with my mu4e

Re: Bug: doc string incorrect in org-icalendar-exclude-tags [8.3.2 (release_8.3.2-1-g115c4b @ /home/james/src/org-mode/lisp/)]

[Nicolas Goaziou]

Hello,

james@jamestechnotes.com writes:

> I've been trying to sort out the icalendar export bits. I've noticed the
> docstring of (org-icalendar-exclude-tags) states that the tag can be set
> with the ICAL_EXCLUDE_TAGS keyword. (it doesn't work). However in the
> code of (org-export-define-derived-backend), the :exclude-tags of
> :options-alist uses "ICALENDAR_EXCLUDE_TAGS". The does work as a file
> level keyword.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou