From: Ihor Radchenko <email@example.com>
To: Jim Wisniewski <firstname.lastname@example.org>
Subject: Re: [PATCH] ox.el: Customize org-export-dispatch options
Date: Sat, 15 Apr 2023 09:49:33 +0000 [thread overview]
Message-ID: <87bkjplbki.fsf@localhost> (raw)
Jim Wisniewski <email@example.com> writes:
> Here's a small enhancement I wrote to add customizable variables for the
> `org-export-dispatch' UI options that don't already have one. I almost always
> export with "Body only" switched on, and I got tired of manually toggling it
> each time; while I was at it I also added variables for "Visible only" and
> "Force publishing", because why not. Hopefully others will find this helpful as
Thanks! Looks like reasonable addition. See some minor comments below.
> I sent in the copyright assignment form but haven't gotten the contract back to
> sign yet.
FSF should reply within 5 working days. If not, follow up with them once.
> * doc/org-manual.org: Document the new export variables.
In addition to the manual, please announce the new customization options
> +(defcustom org-export-body-only nil
> + "The initial \"Body only\" setting when exporting with `org-export-dispatch'.
> +Non-nil means only export body code, without the surrounding
> + :group 'org-export-general
> + :version "30.0"
Here, and in other new options, :version is not needed.
> + :package-version '(Org . "9.7")
> + :type 'boolean)
You can also add :safe keyword as these options are safe to set as
Ihor Radchenko // yantar92,
Org mode contributor,
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>
next prev parent reply other threads:[~2023-04-15 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 4:48 [PATCH] ox.el: Customize org-export-dispatch options Jim Wisniewski
2023-04-15 9:49 ` Ihor Radchenko [this message]
2023-04-15 20:36 ` Jim Wisniewski
2023-04-16 13:00 ` Ihor Radchenko
2023-04-19 21:44 ` Jim Wisniewski
2023-04-20 8:48 ` Ihor Radchenko
2023-04-21 18:04 ` Jim Wisniewski
2023-04-22 12:40 ` Ihor Radchenko
2023-05-02 21:05 ` Jim Wisniewski
2023-05-03 11:46 ` Ihor Radchenko
2023-05-14 13:21 ` Bastien Guerry
2023-05-14 14:19 ` Ihor Radchenko
2023-05-14 18:35 ` Jim Wisniewski
2023-04-15 11:08 ` Max Nikulin
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).