From: Nick Dokos <nicholas.dokos@hp.com>
To: Rasmus Pank Roulund <rasmus@gmx.us>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Publish HTML Without Title
Date: Sun, 27 Nov 2011 18:11:17 -0500 [thread overview]
Message-ID: <5091.1322435477@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Rasmus Pank Roulund <rasmus@gmx.us> of "Sun, 27 Nov 2011 12:06:05 GMT." <87r50twz0y.fsf@gmail.com>
Rasmus Pank Roulund <rasmus@gmx.us> wrote:
> The thing is, this is a 'new' thing, as the git blame log also
> suggests. Which is bothersome. But okay.
>
The scenario probably went something like this: a) move the title to the
preamble because that's the Right Thing (TM) b) oops - org-info.js broke
c) revert a) and make a note to fix it once org-info.js is fixed.
Things like this happen all the time: the question is what exactly broke
your web site. You could do some git archaelogy e.g. and figure out when
things were working and when they broke and go through the ML and figure out
why things changed the way they did etc. I suspect it's not worth your time
though.
> > Next question: can't you get rid of the instance in your preamble at
> > least
> > temporarily? Does it have to be in the "top" div?
>
> Well, you know, I would have to redesign my website. It is possible,
> but I like it. . .
>
> The header on each side is something like:
>
> | Title | | Menu |
> | Left aligned | empty space | Right aligned |
>
> Which is rather neat IMO.
>
> It used to work. I don't know under which version of Org I wrote
> (probably mostly stole :) the original CSS but I am guessing 7.6.
>
> I had hoped for some command I could #+BIND to have Org behave as
> before, (e.g. similar to the BIND for removing \maketitle in LaTeX).
>
You can just use your own private patch to org-html.el to get rid of the
offending entry and just keep rebasing it on top of any updates. There
is a section in the FAQ that describes the process. Then when things settle
down and depending on *how* they settle down, you can either throw the patch
away (if everything ends up working without it) or submit it for inclusion.
The relevant section of the FAQ is
http://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development
Nick
prev parent reply other threads:[~2011-11-27 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 2:23 Publish HTML Without Title Rasmus
2011-11-26 7:40 ` Nick Dokos
2011-11-26 13:40 ` Rasmus Pank Roulund
2011-12-11 16:23 ` Bastien
2011-12-12 1:11 ` Rasmus
2011-11-27 3:31 ` Nick Dokos
2011-11-27 12:06 ` Rasmus Pank Roulund
2011-11-27 23:11 ` Nick Dokos [this message]
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=5091.1322435477@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).