[O] How to stop org delete surrounding newline when adding headlines?

[Shiyao Ma]

Hi,

I don't want org to automatically insert newline when adding headlines, so
I set this:

org-blank-before-new-entry '((heading . nil) (plain-list-item . nil))

But turns out, org *aggressively* delete the existing newlines when I press
ctrl-return.


How to tell org simply not to add newline when adding headline, meanwhile
not do anything else?


Regards.

Re: [O] ob-shell: using a table variable with bash

[George Kettleborough]

On 08/03/17 08:24, Nicolas Goaziou wrote:

I have no objection to this patch, but I think it needs to be
documented, if only as a code comment. IIRC, there is also some
documentation about "ob-shell" on Worg. It would be nice to document
this feature.


I can't actually find any documentation for ob-shell. I had to read the 
source code. I have documented it as a code comment in my patch (with 
proper commit message).


Thanks,

George.

>From 97dadaf0ba0f18772d4d8ac968ea63374937b179 Mon Sep 17 00:00:00 2001
From: George Kettleborough 
Date: Wed, 8 Mar 2017 11:25:37 +
Subject: [PATCH] ob-shell: use old table var behaviour when sep is used

When using the bash shell and an org table is used as a variable, the
default behaviour is to declare it as a bash array. The generic
behaviour is to convert the table to a string with columns separated by
a given separator string. This allows a user to choose the generic
behaviour by declaring the separator using a :separator option to the
code block.
---
 lisp/ob-shell.el | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/lisp/ob-shell.el b/lisp/ob-shell.el
index 9c22af8..8c7b4f1 100644
--- a/lisp/ob-shell.el
+++ b/lisp/ob-shell.el
@@ -140,7 +140,9 @@ This function is called by `org-babel-execute-src-block'."
 
 (defun org-babel--variable-assignments:bash (varname values  sep hline)
   "Represents the parameters as useful Bash shell variables."
-  (if (listp values)
+  ;; we declare org tables as bash array types, unless the user has
+  ;; set the :separator option
+  (if (and (listp values) (null sep))
   (if (and (listp (car values)) (= 1 (length (car values
 	  (org-babel--variable-assignments:bash_array varname values sep hline)
 	(org-babel--variable-assignments:bash_assoc varname values sep hline))
-- 
2.10.1.502.g6598894

Re: [O] jumping from Agenda/Timeline to .org source file

[Samuel Wales]

tangentially, jumping to org from agenda almost always or always puts
a pointless ellipsis at the top of the window for me.

in case it's relevant to tangential changes.

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

The NIH, FDA, and CDC are not there for you.  Not without activism.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.

Re: [O] HTML presentations using org-html-slideshow?

[Peter Salazar]

Excellent. Let me know what you think!

On Wed, Mar 8, 2017 at 3:52 AM, Julian M. Burgos  wrote:

> Thanks for the head up.  I will check it out.
>
> Peter Salazar writes:
>
> > If anyone's interested, there's a new working version of
> > org-html-slideshow that's compatible with org-mode 9.x available here:
> > https://github.com/aiba/org-html-slideshow.
> >
> > On Mon, Mar 6, 2017 at 10:04 AM, Peter Salazar 
> > wrote:
> >
> >> Hi everyone,
> >>
> >> I've been using the excellent org-html-slideshow (
> >> https://github.com/relevance/org-html-slideshow) to generate HTML
> slides
> >> from org-mode, and it's been working well for me for years.
> >>
> >> It generates HTML slides from org-mode using the org-mode heading
> >> hierarchy. Tag any heading with the org-tag :slide: and that heading and
> >> its contents automatically become their own slide once you export to
> HTML
> >> using org-export-dispatch.
> >>
> >> I prefer org-html-slideshow to org-reveal since it allows me the ability
> >> to easily customize the look and feel of slides—by creating a custom
> >> slide—simply by adding an org-tag. So if I tag an org-heading with the
> tag
> >> :fullscreenslide: for example (so that the heading looks like * Heading
> >> :slide:fullscreenslide:), it will then export that slide to HTML with
> >> class="fullscreenslide" — and I can then use CSS to customize the look
> and
> >> feel of all slides with that class.
> >>
> >> Org-html-slideshow also offers a great Presenter View, which opens in a
> >> separate tab in your browser, and displays your speaker notes, the
> current
> >> slide, and the next slide. Unfortunately, org-html-slideshow is no
> longer
> >> being actively developed, and a recent update to org-mode has broken the
> >> way Presenter View functions. Somehow with the new org-mode updates, the
> >> "next slide" view in Presenter Notes mode no longer advances correctly.
> The
> >> "next slide" slide gets stuck in a loop of 4-5 slides, and just repeats
> >> those few slides. It does not reliably show you what the next slide is
> >> going to be.
> >>
> >> I notice that the output from example.org when I export to HTML is
> fairly
> >> different from the example.html that's in the repo. Something in those
> >> differences is breaking the ability of Presenter Notes to advance to the
> >> next slide:
> >> https://gist.github.com/incandescentman/dca040c750a3e9e7e687942d69ebd5
> 3f
> >>
> >> Anyone else using org-html-slideshow? Does anyone have any thoughts on
> how
> >> to get this working again? Thanks!
> >>
>
>
> --
> Julian Mariano Burgos, PhD
> Hafrannsóknastofnun, rannsókna- og ráðgjafarstofnun hafs og vatna/
> Marine and Freshwater Research Institute
> Skúlagata 4, 121 Reykjavík, Iceland
> Sími/Telephone : +354-5752037
> Bréfsími/Telefax:  +354-5752001
> Netfang/Email: julian.bur...@hafogvatn.is
>

Re: [O] How to call a source code block from another one

[Eric S Fraga]

On Wednesday,  8 Mar 2017 at 11:20, Marcin Borkowski wrote:
> Hi all,
>
> and sorry if this is trivial, but I didn't find it in the manual.
>
> Assume that I have a few source code blocks (in my case, in bash) and
> I want to call them in sequence.  Is it possible to write another,
> "master" source code block which would then call those previous blocks?

You could use noweb to include other code blocks in a master one.
You reference other src blocks using <>.

e.g.
#+begin_src shell :noweb yes
<>
<>
#+end_src

where block1 and block2 are shell src blocks as well.

HTH,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.3-241-gc3d67b


signature.asc
Description: PGP signature

Re: [O] jumping from Agenda/Timeline to .org source file

[Alan Schmitt]

On 2017-03-08 12:02, Nicolas Goaziou  writes:

> Hello,
>
> Alan Schmitt  writes:
>
>> Hello,
>>
>> On 2017-03-01 13:28, use...@internet.lu writes:
>>
>>> When I jump from the Agenda-Timeline view to the source .org file,
>>> either with TAB, SPACE or by using the follow mode, Emacs will
>>> position me exactly *below* the source line in the org file (where the
>>> scheduled date is). On macOS or Linux this does not happen, the cursor
>>> is on the task description. I've tried to work with different line
>>> endings on Windows to no avail. Also, my org file and my Emacs config
>>> are minimal and identical between macOS and Windows.
>>
>> I'm on macOS, and when I jump using  I get to the headline.
>> However, when I jump using  I end up on the SCHEDULED or DEADLINE
>> line.
>>
>> I would also like to always end up on the headline.
>
> TAB and RET are bound to two different functions. Since both behaviours
> may be useful, I don't see any incentive to "fix" anything. You could
> bind RET to `org-agenda-goto', or is there anything I am missing?

I would like to use `org-agenda-goto', but without splitting the frame.
In other words, I want to destination to be the one of
`org-agenda-goto', but the window handling to be the one of
`org-agenda-switch-to'.

Best,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-02: 406.42, 2016-02: 404.04


signature.asc
Description: PGP signature

Re: [O] How to call a source code block from another one

[Rasmus]

Marcin Borkowski  writes:

> Hi all,
>
> and sorry if this is trivial, but I didn't find it in the manual.
>
> Assume that I have a few source code blocks (in my case, in bash) and
> I want to call them in sequence.  Is it possible to write another,
> "master" source code block which would then call those previous blocks?

Couldn't you use ob noweb for that?

http://orgmode.org/org.html#noweb

The example here might be close to what you want, if I understand
correctly,

http://orgmode.org/org.html#noweb_002dref

Hope it helps,
Rasmus

-- 
There are known knowns; there are things we know that we know

Re: [O] Bug: org-export-as

[drymer]

Ah, I see, you're wright. I believe I can fix the problem, but I still don't 
understand why it behaves differently on that two versions. Anyway, thank you 
very much.

On Wed, Mar 08, 2017 at 11:58:57AM +0100, Nicolas Goaziou wrote:

Hello,

drymer  writes:


Hi,

Thanks for your time. Could you please retry and evaluate this:

,
| (defun test-org-export ()
|   (interactive)
|   (save-excursion
| (org-mark-element)
| (forward-line) ;; donot export title
| (setq b (region-beginning))
| (setq e (region-end)))
|   (message (org-export-as 'html t nil t)))
`

And execute `M-x test-org-export RET' on the example header:

 ,---
 | * TODO Testing:test:
 |   Nullam eu ante vel est convallis dignissim.  Fusce suscipit, wisi nec
 |   facilisis facilisis, est dui fermentum leo, quis tempor ligula erat
 |   quis odio.  Nunc porta vulputate tellus.  Nunc rutrum turpis sed pede.
 |   Sed bibendum.  Aliquam posuere.  Nunc aliquet, augue nec adipiscing
 |   interdum, lacus tellus malesuada massa, quis varius mi purus non odio.
 |   Pellentesque condimentum, magna ut suscipit hendrerit, ipsum augue
 |   ornare nulla, non luctus diam neque sit amet urna.  Curabitur
 |   vulputate vestibulum lorem.  Fusce sagittis, libero non molestie
 |   mollis, magna orci ultrices dolor, at vulputate neque nulla lacinia
 |   eros.  Sed id ligula quis est convallis tempor.  Curabitur lacinia
 |   pulvinar nibh.  Nam a sapien.
 `---

And see if it happens?


It does, but the problem is in `test-org-export'. There, `org-export-as'
is called outside the `save-excursion' so region beginning is not the
same as b anymore. The region then includes the headline, and "subtree
export" feature is ignored since there is an active region.


Regards,

--
Nicolas Goaziou0x80A93738



signature.asc
Description: PGP signature

Re: [O] limitation for macro expansion

[Nicolas Goaziou]

Hello,

Yasushi SHOJI  writes:

> Are you saying that it's possible to generate "a_20170307.txt" from
> "a_{{{timestamp}}}.txt" if I set those variables mentioned above
> correctly? without using '\under'?

Not at all. Sorry about the confusion.

The mentioned variables allow writing, e.g., a_b without worrying about
any subscript, if you don't use it.

> I know you said it's ambiguous.  So let me clarify what I said. What I
> said above was to change the syntax (or lex / parser's behavior) when
> some variable, let's say 'org-do-not-parse-sub-superscripts', is set
> to nil.
>
> So that a) org leaves '_' in "a_{{{somemacro}}}" as-is and the macro
> parser will pickup the "{{{somemacro}}}, b) when I want to use
> subscript, I can write "a\sub{someword or two}" to make a subscript.
>
> People like me don't use subscript much (to be honest, I've never
> wanted to use subscript since I started use Org, seven years?), but
> use '_' many times in a doc.  Hence, (setq org-use-sub-superscripts
> nil) in my init.el.  But for someone wanting to use subscripts in rare
> occasion, '\sub' would serve.
>
> I can understand if you say it's not good idea to change the _syntax_
> by a variable.

Actually, I strictly opposed to any variable controlling syntax. So the
above is not an option.

>> This is exactly what a nil `org-export-with-sub-superscripts' does.
>
> If that's the case, why doesn't macro parser pickup the
> "{{{timestamp}}}" in "a_{{{timestamp}}}"?

My bad. My sentence is inaccurate: it should be "more or less" instead
of "exactly".

Actually `org-export-with-sub-superscripts' doesn't alter the syntax,
and doesn't mess with parsers. The sub/superscript is parsed the usual
way, but then is turned back into plain Org syntax, i.e., a string, in
the parse tree. See `org-export--remove-uninterpreted-data' for details.

In most cases, the result is the same as if the sub/superscript never
had been parsed. Unfortunately, in this case, it differs. This variable
triggers way after macros have been expanded so it cannot help with
macros.

> Maybe this is my confusing point?  The component resposible defining
> the org "syntax" is different from the parser?

No, it isn't.

> Even if sub/super parser is by-passed, because the "syntax" is
> subscript, the macro parser won't be called on this substring?

No parser is by-passed, but its work may be undone, per above. So,
indeed, the macro parser isn't called.

> Is the syntax defined in org-element--object-regexp and
> org-element--object-lex?

The latter controls precedence among parsed objects.

Anyway, I think a simple solution to your problem is to 

1. Write a function turning _{{{...}}} into _... and add it to
   `org-export-before-processing-hook'.

2. Depending on the back-end, write a function removing the spurious
   brackets. Note that I pushed a fix in maint that should limit them in
   ASCII back-end.

Regards,

-- 
Nicolas Goaziou0x80A93738

[O] How to call a source code block from another one

[Marcin Borkowski]

Hi all,

and sorry if this is trivial, but I didn't find it in the manual.

Assume that I have a few source code blocks (in my case, in bash) and
I want to call them in sequence.  Is it possible to write another,
"master" source code block which would then call those previous blocks?

Best,

--
Marcin Borkowski

Re: [O] jumping from Agenda/Timeline to .org source file

[Nicolas Goaziou]

Hello,

Alan Schmitt  writes:

> Hello,
>
> On 2017-03-01 13:28, use...@internet.lu writes:
>
>> When I jump from the Agenda-Timeline view to the source .org file,
>> either with TAB, SPACE or by using the follow mode, Emacs will
>> position me exactly *below* the source line in the org file (where the
>> scheduled date is). On macOS or Linux this does not happen, the cursor
>> is on the task description. I've tried to work with different line
>> endings on Windows to no avail. Also, my org file and my Emacs config
>> are minimal and identical between macOS and Windows.
>
> I'm on macOS, and when I jump using  I get to the headline.
> However, when I jump using  I end up on the SCHEDULED or DEADLINE
> line.
>
> I would also like to always end up on the headline.

TAB and RET are bound to two different functions. Since both behaviours
may be useful, I don't see any incentive to "fix" anything. You could
bind RET to `org-agenda-goto', or is there anything I am missing?

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: org-export-as

[Nicolas Goaziou]

Hello,

drymer  writes:

> Hi,
>
> Thanks for your time. Could you please retry and evaluate this:
>
> ,
> | (defun test-org-export ()
> |   (interactive)
> |   (save-excursion
> | (org-mark-element)
> | (forward-line) ;; donot export title
> | (setq b (region-beginning))
> | (setq e (region-end)))
> |   (message (org-export-as 'html t nil t)))
> `
>
> And execute `M-x test-org-export RET' on the example header:
>
>  ,---
>  | * TODO Testing:test:
>  |   Nullam eu ante vel est convallis dignissim.  Fusce suscipit, wisi nec
>  |   facilisis facilisis, est dui fermentum leo, quis tempor ligula erat
>  |   quis odio.  Nunc porta vulputate tellus.  Nunc rutrum turpis sed pede.
>  |   Sed bibendum.  Aliquam posuere.  Nunc aliquet, augue nec adipiscing
>  |   interdum, lacus tellus malesuada massa, quis varius mi purus non odio.
>  |   Pellentesque condimentum, magna ut suscipit hendrerit, ipsum augue
>  |   ornare nulla, non luctus diam neque sit amet urna.  Curabitur
>  |   vulputate vestibulum lorem.  Fusce sagittis, libero non molestie
>  |   mollis, magna orci ultrices dolor, at vulputate neque nulla lacinia
>  |   eros.  Sed id ligula quis est convallis tempor.  Curabitur lacinia
>  |   pulvinar nibh.  Nam a sapien.
>  `---
>
> And see if it happens?

It does, but the problem is in `test-org-export'. There, `org-export-as'
is called outside the `save-excursion' so region beginning is not the
same as b anymore. The region then includes the headline, and "subtree
export" feature is ignored since there is an active region.


Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] ob-shell: using a table variable with bash

[Nicolas Goaziou]

Hello,

"George Kettleborough (EI)"  writes:

> I recently updated my org-mode from version 7 (I think) to the latest. 
> The behaviour of using a table as a variable in a shell code source 
> block has changed. I use to use it like this:
>
> #+BEGIN_SRC sh :results output :var table=synteny-names :separator ,
>IFS=','
>while read col1 col2; do
># do stuff
>done <$table
>EOF
> #+END_SRC
>
> This just stopped working with the new version and I could not figure 
> out why for a long time. But I looked in the new ob-shell.el code and 
> figured out that when the shell is bash it now makes an associative 
> array if the variable is a table. I couldn't seem to find this 
> documented anywhere.
>
> This new behaviour seems like it would be useful in a lot of cases, but 
> in my case, the tables are not key-value pairs, they are merely things I 
> want to iterate over. I wonder if simply checking to see if :separator 
> is set and using the old behaviour if so would be better? This would 
> seem to be a fine fix which maintains backwards compatibility unless 
> there is a reason to set :separator but still expect the new
> behaviour.

I have no objection to this patch, but I think it needs to be
documented, if only as a code comment. IIRC, there is also some
documentation about "ob-shell" on Worg. It would be nice to document
this feature.

Also, could you provide a proper commit message?

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] publishing files with images to latex

[Nicolas Goaziou]

Hello,

Robert Klein  writes:

> when I publish a project to PDF org-mode does not include the images in
> the exported PDF (i.e. LaTeX doesn't find them), when I start the
> publishing process from a buffer which is /not/ in the directory to be
> published.
>
>
> E.e. when I have the org files in ~/Documents/mpipdocs/linux and
> publish to the same directory, but I'm in a buffer ~/.emacs, the images
> show not up in the PDF export and in the *Messages* I get messages "PDF
> file exported with errors" or so.
>
> However, when I'm visiting, e.g. ~/Documents/mpipdocs/linux/index.org
> and start the publishing process, everything goes Ok.

Fixed. Could you confirm it?

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: org-export-as

[drymer]

Hi,

Thanks for your time. Could you please retry and evaluate this:

,
| (defun test-org-export ()
|   (interactive)
|   (save-excursion
| (org-mark-element)
| (forward-line) ;; donot export title
| (setq b (region-beginning))
| (setq e (region-end)))
|   (message (org-export-as 'html t nil t)))
`

And execute `M-x test-org-export RET' on the example header:

 ,---
 | * TODO Testing:test:
 |   Nullam eu ante vel est convallis dignissim.  Fusce suscipit, wisi nec
 |   facilisis facilisis, est dui fermentum leo, quis tempor ligula erat
 |   quis odio.  Nunc porta vulputate tellus.  Nunc rutrum turpis sed pede.
 |   Sed bibendum.  Aliquam posuere.  Nunc aliquet, augue nec adipiscing
 |   interdum, lacus tellus malesuada massa, quis varius mi purus non odio.
 |   Pellentesque condimentum, magna ut suscipit hendrerit, ipsum augue
 |   ornare nulla, non luctus diam neque sit amet urna.  Curabitur
 |   vulputate vestibulum lorem.  Fusce sagittis, libero non molestie
 |   mollis, magna orci ultrices dolor, at vulputate neque nulla lacinia
 |   eros.  Sed id ligula quis est convallis tempor.  Curabitur lacinia
 |   pulvinar nibh.  Nam a sapien.
 `---

And see if it happens? I see it clearly different when using different versions of 
emacs, and I know I'm not the only one[1]. On >emacs25 it does not execute 
`forward-line' for some reason and it includes the header.

If you still see the expected behaviour, what would you recommend me to do?

Regards

1 - https://github.com/redguardtoo/org2nikola/issues/5
On Wed, Mar 08, 2017 at 12:24:38AM +0100, Nicolas Goaziou wrote:

Hello,

drymer  writes:


I'm trying to debug the package org2nikola, which works on emacs-24.5
but not on >emacs-25. What I'm trying to see is why the title is
exported when using >emacs-25 but not when prior versions. For what I've
being testing, it doesn't seem related to the package but to org-mode or
emacs. I'll explain why I think this. An example text I want to export would be:

 ,---
 | * TODO Testing:test:
 |   Nullam eu ante vel est convallis dignissim.  Fusce suscipit, wisi nec
 |   facilisis facilisis, est dui fermentum leo, quis tempor ligula erat
 |   quis odio.  Nunc porta vulputate tellus.  Nunc rutrum turpis sed pede.
 |   Sed bibendum.  Aliquam posuere.  Nunc aliquet, augue nec adipiscing
 |   interdum, lacus tellus malesuada massa, quis varius mi purus non odio.
 |   Pellentesque condimentum, magna ut suscipit hendrerit, ipsum augue
 |   ornare nulla, non luctus diam neque sit amet urna.  Curabitur
 |   vulputate vestibulum lorem.  Fusce sagittis, libero non molestie
 |   mollis, magna orci ultrices dolor, at vulputate neque nulla lacinia
 |   eros.  Sed id ligula quis est convallis tempor.  Curabitur lacinia
 |   pulvinar nibh.  Nam a sapien.
 `---

I would execute the function `org2nikola-export-subtree' in the
header. More or less, this function would guide us until the next
function with the above text, but not the header, marked as a region:

 ,
 | (org-export-as 'html t nil t)
 `

In emacs-24.5 this function returns:

 ,
 | 
 | Nullam eu ante vel est convallis dignissim.  Fusce suscipit, wisi nec 
facilisis
 | facilisis, est dui fermentum leo, quis tempor ligula erat quis odio.  Nunc 
porta
 | vulputate tell us.  Nunc rutrum turpis sed pede.  Sed bibendum.  Aliquam 
posuere.
 | Nunc aliquet, augue nec adipiscing interdum, lacus tellus malesuada massa, 
quis
 | varius mi purus non odio.  Pellentesque condimentum, magna ut suscipit 
hendrerit,
 | ipsum augue ornare nulla, non luctus diam neque sit amet urna.  Curabitur 
vulputate
 | vestibulum lorem.  Fusce sagittis, libero non molestie mollis, magna orci 
ultrices
 | dolor, at vulputate neque nulla lacinia eros.  Sed id ligula quis est 
convallis
 | tempor.  Curabitur lacinia pulvinar nibh.  Nam a sapien.
 | 
 `

In >emacs-25 this function returns:

 ,
 | 
 | Testing
 | 
 | 
 | Nullam eu ante vel est convallis dignissim.  Fusce suscipit, wisi nec 
facilisis
 | facilisis, est dui fermentum leo, quis tempor ligula erat quis odio.  Nunc 
porta
 | vulputate tellus.  Nunc rutrum turpis sed pede.  Sed bibendum.  Aliquam 
posuere.
 | Nunc aliquet, augue nec adipiscing interdum, lacus tellus malesuada massa, 
quis
 | varius mi purus non odio.  Pellentesque condimentum, magna ut suscipit 
hendrerit,
 | ipsum augue ornare nulla, non luctus diam neque sit amet urna.  Curabitur 
vulputate
 | vestibulum lorem.  Fusce sagittis, libero non molestie mollis, magna orci 
ultrices
 | dolor, at vulputate neque nulla lacinia eros.  Sed id ligula quis est 
convallis
 | tempor.  Curabitur lacinia pulvinar nibh.  Nam a sapien.
 | 
 | 
 | 
 `


FWIW, I cannot reproduce it. When calling (org-export-as 'html t nil t)
gets me the the first output. However, I get the latter when region
includes the heading.

Actually you cannot 

Re: [O] HTML presentations using org-html-slideshow?

[Fabrice Popineau]

If only it were written in emacs-lisp, it would have been much easier to
adapt to newer releases of Org.

Fabrice

Re: [O] HTML presentations using org-html-slideshow?

[Julian M. Burgos]

Thanks for the head up.  I will check it out.

Peter Salazar writes:

> If anyone's interested, there's a new working version of
> org-html-slideshow that's compatible with org-mode 9.x available here:
> https://github.com/aiba/org-html-slideshow.
>
> On Mon, Mar 6, 2017 at 10:04 AM, Peter Salazar 
> wrote:
>
>> Hi everyone,
>>
>> I've been using the excellent org-html-slideshow (
>> https://github.com/relevance/org-html-slideshow) to generate HTML slides
>> from org-mode, and it's been working well for me for years.
>>
>> It generates HTML slides from org-mode using the org-mode heading
>> hierarchy. Tag any heading with the org-tag :slide: and that heading and
>> its contents automatically become their own slide once you export to HTML
>> using org-export-dispatch.
>>
>> I prefer org-html-slideshow to org-reveal since it allows me the ability
>> to easily customize the look and feel of slides—by creating a custom
>> slide—simply by adding an org-tag. So if I tag an org-heading with the tag
>> :fullscreenslide: for example (so that the heading looks like * Heading
>> :slide:fullscreenslide:), it will then export that slide to HTML with
>> class="fullscreenslide" — and I can then use CSS to customize the look and
>> feel of all slides with that class.
>>
>> Org-html-slideshow also offers a great Presenter View, which opens in a
>> separate tab in your browser, and displays your speaker notes, the current
>> slide, and the next slide. Unfortunately, org-html-slideshow is no longer
>> being actively developed, and a recent update to org-mode has broken the
>> way Presenter View functions. Somehow with the new org-mode updates, the
>> "next slide" view in Presenter Notes mode no longer advances correctly. The
>> "next slide" slide gets stuck in a loop of 4-5 slides, and just repeats
>> those few slides. It does not reliably show you what the next slide is
>> going to be.
>>
>> I notice that the output from example.org when I export to HTML is fairly
>> different from the example.html that's in the repo. Something in those
>> differences is breaking the ability of Presenter Notes to advance to the
>> next slide:
>> https://gist.github.com/incandescentman/dca040c750a3e9e7e687942d69ebd53f
>>
>> Anyone else using org-html-slideshow? Does anyone have any thoughts on how
>> to get this working again? Thanks!
>>


--
Julian Mariano Burgos, PhD
Hafrannsóknastofnun, rannsókna- og ráðgjafarstofnun hafs og vatna/
Marine and Freshwater Research Institute
Skúlagata 4, 121 Reykjavík, Iceland
Sími/Telephone : +354-5752037
Bréfsími/Telefax:  +354-5752001
Netfang/Email: julian.bur...@hafogvatn.is