emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Aviv <aviv@usna.edu>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+BEGIN_html/#+END_html tags not exporting literally to html anymore?
Date: Sun, 24 Jul 2016 11:53:49 -0400	[thread overview]
Message-ID: <CAJV1HczG8+-257Muk2MJ-YsVFjkFtCLh8sKL=wDf1u9j-2YmYw@mail.gmail.com> (raw)
In-Reply-To: <87poq5xtku.fsf@alphaville.usersys.redhat.com>

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

Thanks for the comments... very helpful! This is a perfect example of when
living on the bleeding edge of a library and searching for solutions can
come into conflict. I'll stick to looking at the docs built off the git
repo.

On Fri, Jul 22, 2016 at 5:15 PM, Nick Dokos <ndokos@gmail.com> wrote:

> Adam Aviv <aviv@usna.edu> writes:
>
> > On Fri, Jul 22, 2016 at 12:38 PM, Charles C. Berry <ccberry@ucsd.edu>
> wrote:
> >
> >     It is updated. For example, see
> >
> >             (info "(org) Special blocks")
> >     and
> >             (info "(org) results")
> >
> >     and in ORG-NEWS.
> >
> > I see that now, but the online documentation is still out dated:
> >
> > http://orgmode.org/manual/Quoting-HTML-tags.html
> >
> > Is there a push cycle to keep the online documents up to date with the
> source documentation? Or is that
> > controlled differently?
> >
>
> That's because the online docs are for the stable version (the version
> you get from the maint branch of the git repo).
>
> If you are using latest (i.e. the master branch of the git repo), then
> you have to build and use the docs that come with it:
>
>   make info
>
> I do
>
> --8<---------------cut here---------------start------------->8---
>
> INFOPATH=$HOME/src/emacs/org/org-mode/doc:/usr/local/share/info:/usr/share/info
> export INFOPATH
> --8<---------------cut here---------------end--------------->8---
>
> in my login shell initialization file to make sure that I pick the
> version I built over any other versions installed on my system.
> There are other ways to do that - and even for this one, you will
> have to modify the paths appropriately.
>
> --
> Nick
>
>
>


-- 
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655 <%28410%29%20293-%206655>*

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

  reply	other threads:[~2016-07-24 15:54 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
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 [this message]
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='CAJV1HczG8+-257Muk2MJ-YsVFjkFtCLh8sKL=wDf1u9j-2YmYw@mail.gmail.com' \
    --to=aviv@usna.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@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).