From: Eric Schulte <schulte.eric@gmail.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [babel] Collection of code block snippets
Date: Tue, 06 Sep 2011 09:16:16 -0600 [thread overview]
Message-ID: <877h5lzolk.fsf@gmail.com> (raw)
In-Reply-To: CAGhLh6FrgD8wUCXG7V06aU5yAahZsL9aZTmhNZdQojoT1-F61w@mail.gmail.com
Hi Rainer,
>
>> - exporting to some backend and checking the resulting export file
>> would either leave out some results or possibly be very brittle to
>> small changes (e.g., changes in the exporter backend)
>>
>
> This might be actually be an advantage - if changes are detected, the
> exported file can be evaluated visually and added to the "aceptable
> results", either generally or for a user.
>
Makes sense. Well, this process shouldn't be difficult, you could
simply export scraps.org to say scraps.html at a time when you know that
your config is working (you may have to edit parts of scraps.org). You
can then save the resulting scraps.html file, and in the future you can
re-export scraps.org and compare the results with your reserved
scraps.html using the diff utility. If you see more differences than
simply the date you may have problems.
>
> Yes - I have a few times run into problems due to my configuration file and
> only realized it later - if there would be ab org file which I could use to
> test easily my configuration directly after making the changes, life would
> have been much easier for me. This would also be useful for questions on the
> mailing list and for a kind of "quality control" for published configs on
> the web.
>
Is there a reason that you can't just use the existing test suite for
this purpose? Running the test suite should be as simple as loading the
org-test.el file in org/testing/lisp/org-test.el and then calling the
`org-test-run-all-tests' function.
Best -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-09-06 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 16:35 [babel] Collection of code block snippets Eric Schulte
2011-09-05 8:29 ` Rainer M Krug
2011-09-05 16:54 ` Eric Schulte
2011-09-06 8:26 ` Rainer M Krug
2011-09-06 15:16 ` Eric Schulte [this message]
2011-09-06 15:35 ` Martyn Jago
2011-09-06 17:13 ` Eric Schulte
2011-09-07 8:19 ` Rainer M Krug
2011-09-07 18:24 ` Martyn Jago
2011-09-07 18:15 ` Martyn Jago
2011-09-08 15:16 ` Eric Schulte
2011-09-08 16:18 ` Martyn Jago
2011-09-08 17:44 ` Eric Schulte
2011-09-08 18:34 ` Martyn Jago
2011-09-08 22:03 ` Martyn Jago
2011-09-09 8:22 ` Rainer M Krug
2011-09-09 10:58 ` Martyn Jago
2011-09-09 11:11 ` Martyn Jago
2011-09-09 20:39 ` Eric Schulte
2011-09-10 8:09 ` Martyn Jago
2011-09-11 20:57 ` Eric Schulte
2011-09-14 4:49 ` David Maus
2011-09-14 12:10 ` Martyn Jago
2011-09-09 19:19 ` Eric Schulte
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=877h5lzolk.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@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).