From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: RFC: Proposal for an Org Special Block for ox-html Date: Thu, 24 May 2018 15:25:59 -0400 Message-ID: References: <87o9h56jdl.fsf@gmail.com> <87lgc87vf1.fsf@gmail.com> <87in7c7tye.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000e09233056cf89fb9" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLvsO-00088p-U6 for emacs-orgmode@gnu.org; Thu, 24 May 2018 15:26:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fLvsN-0007y7-Gr for emacs-orgmode@gnu.org; Thu, 24 May 2018 15:26:16 -0400 Received: from mail-wr0-x232.google.com ([2a00:1450:400c:c0c::232]:36936) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fLvsN-0007xY-4K for emacs-orgmode@gnu.org; Thu, 24 May 2018 15:26:15 -0400 Received: by mail-wr0-x232.google.com with SMTP id i12-v6so5130528wrc.4 for ; Thu, 24 May 2018 12:26:15 -0700 (PDT) In-Reply-To: <87in7c7tye.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-org list --000000000000e09233056cf89fb9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Aaron, I just went ahead and removed that "---" syntax from ox-hugo. Updated links= : 1. https://ox-hugo.scripter.co/doc/details-and-summary/ 2. https://ox-hugo.scripter.co/test/posts/details-and-summary/ (it was easy as I had committed that feature just yesterday.) On Thu, May 24, 2018 at 3:08 PM Aaron Ecay wrote: > > Is it important for open to be a =E2=80=9Cbare=E2=80=9D attribute (not su= re of the > official name) like =E2=80=9C
=E2=80=9D as opposed to =E2=80= =9C
open=3D"open">=E2=80=9D? I'm not so sure.. I just followed the documentation here: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details#Creating_= an_open_disclosure_box > The latter form is already supported (in fact the second > =E2=80=9Copen=E2=80=9D can be any string). Just add > > #+attr_html: :open any-string-you-want > I know, but I did not test that.. just thought of doing as in that example in the mozilla documentation. That's why I am using (org-element-property :attr_html special-block) in the code to get the raw values to #+attr_html. > The only thing I know off the top of my head is that CSS can be quite > hairy, Heh, of course :) > so I would not be surprised if this wrapper is sometimes needed. > And indeed, support for it would be missing. > Is it something that is > likely to crop up for other elements as well, such that it would be > desirable to support it in org core? That would be great. I myself wasn't sure if I should bring that up to Org core.. I had just implemented #+attr_css support for ox-hugo. It looks like this: #+attr_html: :class red-text #+attr_css: :color red - Red list item 1 - Red list item 2 Above will generate