emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: publishuing in html5
Date: Tue, 31 Dec 2013 11:41:31 -0500	[thread overview]
Message-ID: <878uv1geh0.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: CAJ98PDyVUC4fCQpXAp4CygacX5aFUM-gD49ZJL3ryGb+H1jjMA@mail.gmail.com

Catonano <catonano@gmail.com> writes:

> Nick,
>
> 2013/12/18 Nick Dokos <ndokos@gmail.com>
>
>     I'm not suggesting that you write this stuff in each and every file in
>     your blog. I'm just suggesting that before you can even have a blog (at
>     least using this mechanism), you have to first figure out what the
>     problem is and resolve it. Then you can optimize.
>    
>     If the above works, then it's straigthforward to translate this into
>     settings that you can put into your .emacs. If it doesn't, anything else
>     you or we do is wasted effort (of which there's been plenty in this
>     thread).
>
> I'm sorry that you feel this thread to contain wasted effort.
>
> I have to say that I disagree.
>
> In fact, it's solved, it works now, and it works by indicating html5 in the configuration rather than in a file.
>
> I was probably confused by reading both the manual and the Worg guide.
>
> I see your point of starting from the easy and then figuring how to generalize. But, you know, cognitive paths are personal.
>
> That's why I published a simple example project for anyone to inspect.
>
> Sometimes wasting effort is due to assuming your peer is traveling along the same cognitive path that you would.
>

Truer words were never uttered... But my interpretation of them differs
from yours :-)

> As you can see, it worked.
>
> Thanks anyway for your help
>
> I think I will have to use your suggestion to move from a configuration based html5 publishing to a templates based one.
>
> I'll let you know

Nick

  parent reply	other threads:[~2013-12-31 16:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 17:46 publishuing in html5 Catonano
2013-12-09 17:59 ` Catonano
2013-12-09 18:48   ` Catonano
2013-12-09 19:53 ` Nick Dokos
2013-12-11  0:41   ` Scott Randby
2013-12-11 12:58     ` Nick Dokos
2013-12-11 14:13       ` Scott Randby
2013-12-11 15:04         ` Nick Dokos
2013-12-11 15:20           ` Scott Randby
2013-12-11 15:24             ` Nicolas Goaziou
2013-12-11 15:47               ` Scott Randby
2013-12-11 16:03                 ` Nicolas Goaziou
2013-12-11 16:30                   ` Scott Randby
2013-12-14 17:01                   ` Catonano
2013-12-14 19:40                     ` Nick Dokos
2013-12-14 21:22                       ` Alan L Tyree
2013-12-14 21:36                       ` Achim Gratz
2013-12-18 10:16                       ` Catonano
2013-12-18 16:41                         ` Nick Dokos
2013-12-31 11:31                           ` Catonano
2013-12-31 12:47                             ` Catonano
2013-12-31 16:41                             ` Nick Dokos [this message]
2013-12-15 10:00                     ` Nicolas Goaziou
2013-12-15 18:30                     ` Scott Randby
2013-12-11 15:43         ` Leading headline of a subtree tag export Scott Randby
2013-12-11 15:57           ` Nicolas Goaziou
2013-12-11 16:35             ` Scott Randby
2013-12-11 10:00   ` publishuing in html5 Catonano
2013-12-09 19:57 ` Nicolas Goaziou
2013-12-11  9:56   ` Catonano
2013-12-15 10:07     ` Nicolas Goaziou
2013-12-18 10:04       ` Catonano
2013-12-18 13:02         ` Nicolas Goaziou
2013-12-31 11:06           ` Catonano
2013-12-20 20:06         ` Scott Randby
2013-12-31 11:42           ` Catonano
2013-12-31 11:47   ` Catonano
2013-12-31 16:28     ` Nick Dokos

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=878uv1geh0.fsf@alphaville.bos.redhat.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).