From: Scott Randby <srandby@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Customizing Org 8.0 Export
Date: Tue, 21 May 2013 11:29:09 -0400 [thread overview]
Message-ID: <519B92C5.1020402@gmail.com> (raw)
In-Reply-To: <CA+M2ft8=8YjwbAZkUcA=z0zDurq90a99wSMwFJgVA4arDPHZGQ@mail.gmail.com>
On 05/21/2013 10:48 AM, John Hendy wrote:
> On Tue, May 21, 2013 at 8:53 AM, Scott Randby <srandby@gmail.com> wrote:
>> On 05/21/2013 01:25 AM, John Hendy wrote:
>>> On May 20, 2013 9:03 PM, "Scott Randby" <srandby@gmail.com> wrote:
>>>> Is there any way to make all of org's variables available for
>>>> customization on startup?
>>>>
>>>
>>> Yes, see the original exporter announcement:
>>>
>>> http://article.gmane.org/gmane.emacs.orgmode/65574
>>>
>>> Section 3.0 calls out two methods of setting available backends. I'm
>>> guessing you are customizing org-export-backends vs (require 'ox-backend).
>>> Try requiring the backend and all associated variables will be there on
>>> startup.
>>>
>>> John
>>
>> Thanks for the solution.
>>
>> This is the second time in a row I've been referred to the original
>> exporter announcement. I'm sorry that my questions are so basic, but I
>> put off switching to 8.0 because my understanding of how org and Emacs
>> work is not very deep and I know little elisp. Once I have things set
>> up, I leave them alone and get to work. I'm very grateful to this list
>> for helping me figure out things that, in hindsight, are obvious.
>
> No problem, and I wouldn't say it was *that* obvious :) I found this
> document extremely helpful:
> - http://orgmode.org/worg/org-8.0.html
>
> I also started (and should really update again/maintain!) this as a
> landing place for documenting other things as they come up:
> - http://orgmode.org/worg/exporters/ox-overview.html
>
> And have a blog post walking through setting things up here, if it helps:
> - http://jwhendy.blogspot.com/2013/03/migrating-to-new-org-mode-exporter-org.html
Thanks for these links. I have been to the org-8.0.html page before, but
I only read part of it. If I would just read through all these nice
pages, then there would be no problem setting things up. But my approach
to Emacs and org is rather haphazard --- I pick up those things I need
and ignore all the rest. My init.el file is a sorry mess. One of these
days I'll go through everything methodically.
>
>
> Good luck! We're all learning here, so no worries on the mailing list.
> More things for Google to index for users stumbling on this after you!
Yes, this list is great. I've asked simple questions on other lists and
received nasty RTFM responses.
>
>
> John
>
>>
>> Scott Randby
>
next prev parent reply other threads:[~2013-05-21 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 2:03 Customizing Org 8.0 Export Scott Randby
2013-05-21 5:25 ` John Hendy
2013-05-21 13:53 ` Scott Randby
2013-05-21 14:48 ` John Hendy
2013-05-21 15:29 ` Scott Randby [this message]
2013-05-21 7:57 ` Sebastien Vauban
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=519B92C5.1020402@gmail.com \
--to=srandby@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
/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).