emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Aviv <aviv@usna.edu>
To: Eric S Fraga <e.fraga@ucl.ac.uk>, Adam Aviv <aviv@usna.edu>,
	"Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Re: #+BEGIN_html/#+END_html tags not exporting literally to html anymore?
Date: Fri, 22 Jul 2016 11:04:54 -0400	[thread overview]
Message-ID: <CAJV1HczRhiSMEzvVa8Ed7-jvtVyVakdpR9Tqopxj4ecF0Japng@mail.gmail.com> (raw)
In-Reply-To: <871t2l4v0y.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 719 bytes --]

On Fri, Jul 22, 2016 at 10:17 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

>
> > If so, is there a way to make compilation backwards compatible. I have
> > a lot of old org files that would be a pain to update.  Further, all
> > the documentation on the org site is also out of date.
>
> a simple regex replace (or two I guess) will fix all in a file?


Yes, I agree --- but that's a burden on long time users even if it is a
simple sed script.

I just wonder why the #+BEGIN_HTML was removed in the first place? What
harm was it doing? And, why was this change made without updating the
documentation to reflect it?




-- 
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*

[-- Attachment #2: Type: text/html, Size: 1644 bytes --]

  reply	other threads:[~2016-07-22 15:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <03f355f9d8a6478c816a612e156e2772@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-07-22 14:17 ` #+BEGIN_html/#+END_html tags not exporting literally to html anymore? Eric S Fraga
2016-07-22 15:04   ` Adam Aviv [this message]
2016-07-22 16:38     ` Charles C. Berry
2016-07-22 19:33       ` Adam Aviv
2016-07-22 20:58         ` Robert Klein
2016-07-22 21:15         ` Nick Dokos
2016-07-24 15:53           ` Adam Aviv
2016-07-22 13:46 Adam Aviv

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=CAJV1HczRhiSMEzvVa8Ed7-jvtVyVakdpR9Tqopxj4ecF0Japng@mail.gmail.com \
    --to=aviv@usna.edu \
    --cc=Emacs-orgmode@gnu.org \
    --cc=e.fraga@ucl.ac.uk \
    /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).