From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to get === on a line by itself to be a special string
Date: Sun, 10 Feb 2013 10:01:20 +0100 [thread overview]
Message-ID: <87wqugfspr.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8vD_LDFsS8DoYNn1RC7x7jKXvAJJetm9RK7f+aNxaghTA@mail.gmail.com> (Samuel Wales's message of "Sat, 9 Feb 2013 22:16:28 -0700")
Hello,
Samuel Wales <samologist@gmail.com> writes:
> I want separators like this:
>
> ===
>
> to be treated as a special string in HTML. This was the
> case in the old exporter.
[...]
> I don't want them to be interpreted as code. I don't want
> to turn off all code just to get this one thing to work. I don't want
> to do ~===~.
>
> Does this mean some filter has to be used?
There are a few solutions to your problem: a macro, a hook, a filter...
> This did not work.
>
> (add-to-list 'org-export-filter-code-functions
> (lambda (text back-end &rest _rest)
> (if (eq back-end 'html)
> (replace-regexp-in-string "^===$" "~===~" text)
> text)))
That's because `html' back-end never returns "^===$", but
"<code>=</code>", as "=" is a verbatim marker. Also, the output of
a filter function will appear in the final output. I doubt that you want
"~===~" to appear in your HTML document.
Here is one solution, with a filter:
#+begin_src emacs-lisp
(defun my-rule-markup (paragraph backend info)
(when (and (org-export-derived-backend-p backend 'html)
(string-match "<p>\n<code>=</code>\n</p>\n*" paragraph))
"<hr width=\"10%\" style=\"width:10%;color:#000;background-color:#000;height:1px;border:none\"/>\n\n"))
(add-to-list 'org-export-filter-paragraph-functions 'my-rule-markup)
#+end_src
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-10 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 5:16 How to get === on a line by itself to be a special string Samuel Wales
2013-02-10 9:01 ` Nicolas Goaziou [this message]
2013-02-12 19:02 ` Samuel Wales
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=87wqugfspr.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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).