From: Bastien <bzg@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 15887@debbugs.gnu.org
Subject: bug#15887: Possibly incorrect custom :types
Date: Thu, 14 Nov 2013 14:11:54 +0100 [thread overview]
Message-ID: <87habfw2jp.fsf@bzg.ath.cx> (raw)
In-Reply-To: <itd2m46omg.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 13 Nov 2013 15:19:35 -0500")
Glenn Morris <rgm@gnu.org> writes:
> Package: org-mode
>
> cus-test.el suggests the following variables may have incorrect
> custom :types. (There may be some false positives.)
> This refers to Org mode in current Emacs trunk.
>
> Eg, org-texinfo-filename does not have "nil" as an option.
>
> org-agenda-deadline-leaders
> org-agenda-search-view-max-outline-level
> org-ascii-format-drawer-function
> org-ascii-format-inlinetask-function
> org-babel-latex-htlatex
> org-babel-latex-htlatex-packages
> org-babel-lob-files
> org-babel-python-None-to
> org-babel-python-mode
> org-babel-ruby-nil-to
> org-export-async-init-file
> org-export-with-creator
> org-html-format-drawer-function
> org-html-format-headline-function
> org-html-format-inlinetask-function
> org-html-with-latex
> org-latex-format-drawer-function
> org-latex-format-inlinetask-function
> org-log-note-headings
> org-mouse-1-follows-link
> org-odt-format-drawer-function
> org-odt-format-headline-function
> org-odt-format-inlinetask-function
> org-odt-with-latex
> org-plantuml-jar-path
> org-texinfo-filename
> org-texinfo-format-drawer-function
> org-texinfo-format-headline-function
> org-texinfo-format-inlinetask-function
> orgstruct-heading-prefix-regexp
I fixed those problems in Org's maintainance branch, this will be part
of the next merge. Thanks!
--
Bastien
next prev parent reply other threads:[~2013-11-14 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:19 bug#15887: Possibly incorrect custom :types Glenn Morris
2013-11-14 13:11 ` Bastien [this message]
2013-11-14 17:18 ` Glenn Morris
2013-11-15 5:25 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87habfw2jp.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=15887@debbugs.gnu.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).