emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Help with new exporter
Date: Fri, 12 Jul 2013 11:28:55 -0400	[thread overview]
Message-ID: <871u734x1k.fsf@gmail.com> (raw)
In-Reply-To: b650a89f7364dfeab5708338223e63b6@johnrakestraw.com

John Rakestraw <lists@johnrakestraw.com> writes:

> Success!
>
> Thanks to all for your help. I really do appreciate your time.
>
> I cannot figure out why I'm getting the brackets that no one else is
> getting (Rasmus -- my problem is that they're there and I don't want
> them), but I now have a filter that will take them out:
>
>       (defun jr-org-delete-brackets-from-tex-file
>         (text backend info)
>         (replace-regexp-in-string "\\[\\]" "" text))
>
>       (add-to-list 'org-export-filter-final-output-functions
>                    'jr-org-delete-brackets-from-tex-file)
>
> Now to explore how to implement this only when I'm using the exam 
> document
> class, perhaps by using a derived backend. (It may be that it won't 
> cause
> any problems with other classes, but it seems sloppy to have it working
> all the time, no?)
>
> Thanks to Robert for the detailed and careful responses, to Charles for
> suggesting the filters, and to Rasmus for the example that helped me
> straighten me out at the end.
>
> And I can't resist an aside to Nick -- I've really appreciated both
> the tone and the content of your detailed contributions to this list
> over the years. I find it difficult to believe that you're more
> pessimistic than I am, but I take some odd pleasure in making
> something work that you thought wouldn't work. ;-)
>

You underestimate my pessimism :-) I had no doubt that you can get rid
of specific artifacts using specific filters like this - you could after
all, run a sed script on the latex output and get rid of this stuff - it
wouldn't be an org-only solution, but that's OK in my book.

I hope you are ultimately successful in producing exams that look
exactly like you want them, using these mechanisms. But I have my doubts
- you have won a battle, but the war is still raging afaict. OTOH, if
you prove me wrong, I would be delighted!

-- 
Nick

  parent reply	other threads:[~2013-07-12 15:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51DFEC7B.7050504@mpip-mainz.mpg.de>
2013-07-12 11:47 ` Help with new exporter Robert Klein
2013-07-12 13:41   ` Nick Dokos
2013-07-12 14:12     ` Rasmus
2013-07-12 14:59       ` Nick Dokos
2013-07-12 15:05         ` John Rakestraw
2013-07-12 15:27           ` Rasmus
2013-07-12 15:47             ` John Rakestraw
2013-07-12 15:28           ` Nick Dokos [this message]
2013-07-12 15:49             ` John Rakestraw
2013-07-12 16:20               ` Nick Dokos
2013-07-10 16:32 John Rakestraw
2013-07-10 16:58 ` Robert Klein
2013-07-10 17:27   ` John Rakestraw
2013-07-10 19:37 ` Robert Klein
2013-07-10 20:46   ` John Rakestraw
2013-07-10 21:04     ` John Rakestraw
2013-07-11  4:04       ` Charles Berry
2013-07-11  5:22     ` Robert Klein
2013-07-11 15:15       ` John Rakestraw
2013-07-11 23:05         ` John Rakestraw
2013-07-12  3:00           ` Thomas S. Dye
2013-07-10 19:56 ` Rasmus

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=871u734x1k.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@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).