On 2023-06-27, at 13:00, Max Nikulin wrote:
>>> On 08/06/2023 22:18, Thomas Redelberger wrote:
http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
>>>
>>> At this page:
>>>
#+BIND: org-html-viewport nil
I do not need viewport information in the HTML.
>
> On 26/06/2023
On 08/06/2023 22:18, Thomas Redelberger wrote:
http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
At this page:
#+BIND: org-html-viewport nil
I do not need viewport information in the HTML.
On 26/06/2023 02:56, Marcin Borkowski wrote:
Do you mean this?
On 2023-06-24, at 17:04, Max Nikulin wrote:
> On 08/06/2023 22:18, Thomas Redelberger wrote:
>> I had a similar requirement for "simplest HTML" and have documented
>> how I tackled this under
>> http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
>
> At this page:
>
>> #+BIND:
On 08/06/2023 22:18, Thomas Redelberger wrote:
I had a similar requirement for "simplest HTML" and have documented how
I tackled this under
http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
At this page:
#+BIND: org-html-viewport nil
I do not need viewport information in the
On 2023-06-24, at 15:34, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>>> Org export passes the actual parsed and filtered AST that will be
>>> exported to `org-export-filter-parse-tree-functions'. You can modify and
>>> traverse the parse tree as you need.
>>
>> Yeah, that I do
Marcin Borkowski writes:
>> Org export passes the actual parsed and filtered AST that will be
>> exported to `org-export-filter-parse-tree-functions'. You can modify and
>> traverse the parse tree as you need.
>
> Yeah, that I do understand. Problem is, I don't know how the AST is
> structured,
On 2023-06-03, at 10:37, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>>> You can loop over links in the exported subtree and export any extra if
>>> necessary. For example, in the `org-export-filter-parse-tree-functions'.
>>
>> Interesting. The main problem with it is that the
On 2023-06-10, at 10:25, Thomas Redelberger wrote:
> Dear Marcin and everybody,
>
> I had a similar requirement for "simplest HTML" and have documented (incl.
> source code) how I tackled this under
> http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
>
> In summary, my solution is
> -
Dear Marcin and everybody,
I had a similar requirement for "simplest HTML" and have documented how I
tackled this under
http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
In summary, it is
- a few settings in init.el:
+ org-html-text-markup-alist similar to below
+ setting
Dear Marcin and everybody,
I had a similar requirement for "simplest HTML" and have documented (incl.
source code) how I tackled this under
http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
In summary, my solution is
- a few settings in init.el:
+ org-html-text-markup-alist similar
Marcin Borkowski writes:
>> You can loop over links in the exported subtree and export any extra if
>> necessary. For example, in the `org-export-filter-parse-tree-functions'.
>
> Interesting. The main problem with it is that the docstring is rather
> concise and I don't understand it well
On 2023-06-03, at 07:08, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>> On 2023-05-30, at 20:45, Marcin Borkowski wrote:
>>
Just use `org-export-as'.
>>>
>>> Thanks again, I didn't know about that function!
>>
>> I tried playing around with it, but it has one drawback - I can't
Marcin Borkowski writes:
> On 2023-05-30, at 20:45, Marcin Borkowski wrote:
>
>>> Just use `org-export-as'.
>>
>> Thanks again, I didn't know about that function!
>
> I tried playing around with it, but it has one drawback - I can't use it
> to export a subtree containing a link to another
On 2023-05-30, at 20:45, Marcin Borkowski wrote:
>> Just use `org-export-as'.
>
> Thanks again, I didn't know about that function!
I tried playing around with it, but it has one drawback - I can't use it
to export a subtree containing a link to another subtree, and that is
something I will
On 2023-05-30, at 17:32, Max Nikulin wrote:
> On 30/05/2023 10:47, Marcin Borkowski wrote:
>> since I'm going to
>> call my exporting function in a loop over many elements. I tried
>> (org-export-with-backend 'html (org-element-at-point (point)))
>
> There is `org-export-string-as', but
On 2023-05-30, at 08:21, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>> ... I tried this:
>>
>> (org-html-export-as-html nil nil nil t '(org-export-with-toc nil))
>
> You need (org-html-export-as-html nil nil nil t '(:with-toc nil))
> See `org-export-options-alist'.
Thanks. So
On 30/05/2023 10:47, Marcin Borkowski wrote:
since I'm going to
call my exporting function in a loop over many elements. I tried
(org-export-with-backend 'html (org-element-at-point (point)))
There is `org-export-string-as', but likely it is not suitable for you.
My guess is that you are
Marcin Borkowski writes:
> ... I tried this:
>
> (org-html-export-as-html nil nil nil t '(org-export-with-toc nil))
You need (org-html-export-as-html nil nil nil t '(:with-toc nil))
See `org-export-options-alist'.
> but the ToC still appears in the output. Also, I'd prefer to do it
> a bit
Hello everyone,
I'd like to export an Org buffer (or portion of it) to the simplest HTML
possible, prgrammatically. For example, I only want the body, I don't
want any generated IDs, and I don't want the ToC. I tried this:
(org-html-export-as-html nil nil nil t '(org-export-with-toc nil))
but
19 matches
Mail list logo
