[O] texi to org?

[Lawrence Bottorff]

Is there such a thing as a converter from a raw texi file to an org file?
I'm experimenting with manual formats and would like to take texi/info
files and convert them to org files. I've tried two approaches with pandoc,
namely, html to org and text (markdown) to org -- and they've produced org
files that lock up Emacs (25.3) - Org (9.1.6). Yes, they come up after a
good half hour, but Emacs is still locked up with my CPUs racing. Right now
I'm working with Emacs Calc
's single
html manual. I've done

>pandoc -f html -t org -o GNUEmacsCalcManual.org GNUEmacsCalcManual.html

and it produces a 2.3 mb file that, as I say, doesn't come up well. This
was following Using Emacs Pandoc
.

I don't necessarily need to do this, but I've had this issue before with
semi-large org files, e.g., a mg-sized file with lots of scheduling stuff.
What sort of processing is going on to open an org file that it would bog
down so badly? Is there anything I can do outside of Emacs to help my
pandoc-produced org file?

LB

[O] Ridiculously long (2 minutes) startup time for org agenda

[JI Xiang]

Hello, first time posting on the mailing list. I encountered a problem 
where my agenda view (|C-c a a|) is taking ridiculously long (nearly 2 
minutes) to be shown the first time. From the second time onwards, the 
time is about 11 seconds, which is still very long by any means.


I wondered whether it has something to do with me having many files in 
the agenda list, so I tried to restrict the list to just one file. But 
still the first call to org-agenda-list took 12 seconds. This shouldn’t 
be normal, right?


The following are shown in the |Messages| buffer during the call.

|Press key for agenda command: Restoring clock data Loading 
/home/jx/.emacs.d/.cache/org-clock-save.el (source)...done [yas] 
Prepared just-in-time loading of snippets successfully. Importmagic 
and/or epc not found. importmagic.el will not be working. Setting up 
indent for shell type zsh Indentation variables are now local. 
Indentation setup for shell type zsh Using vacuous schema Shell native 
completion is disabled, using fallback |


I’m not sure why they would be there, especially the “using vacuous 
schema” and “shell native completion” part. Are the messages related to 
some |#BEGIN_SRC| blocks in the org files? I don’t think I would ever 
need source code blocks when I’m viewing an agenda buffer?


I posted the question on Emacs.SE 
 
and somebody suggested me use |elp-instrument| to perform a profiling. 
The results are as follows:


|Function Name, Call Count, Elapsed Time, Average Time org-agenda 1 
116.6048159 116.6048159 org-agenda-list 1 116.29427357 116.29427357 
org-agenda-prepare 1 109.15345470 109.15345470 
org-agenda-prepare-buffers 1 108.98258905 108.98258905 
org-agenda-get-day-entries 1288 7.0089191339 0.0054417074 
org-agenda-get-scheduled 1288 3.726361062 0.0028931374 
org-agenda-get-deadlines 1288 2.1579713230 0.0016754435 
org-agenda--timestamp-to-absolute 14544 1.1317418120 7.781...e-05 
org-agenda-get-timestamps 1288 0.3673404320 0.0002852021 
org-agenda-get-sexps 1288 0.3438970410 0.0002670008 
org-agenda-get-restriction-and-command 1 0.310503975 0.310503975 
org-agenda-get-blocks 1288 0.3083237900 0.0002393818 
org-agenda-prepare-window 1 0.157091024 0.157091024 org-agenda-skip 8624 
0.0781296389 9.059...e-06 org-agenda-files 49 0.026090686 0.0005324629 
org-agenda-finalize 1 0.013325178 0.013325178 org-agenda-mode 1 
0.009848546 0.009848546 org-agenda-finalize-entries 23 0.006178961 
0.0002686504 org-agenda-today-p 2604 0.0061717839 2.370...e-06 
org-agenda-skip-eval 16968 0.0052723920 3.107...e-07 
org-agenda-highlight-todo 112 0.0039840550 3.557...e-05 
org-agenda-format-item 112 0.0038309749 3.420...e-05 
org-agenda-new-marker 208 0.0031529359 1.515...e-05 
org-agenda-format-date-aligned 28 0.0007373120 2.633...e-05 
org-agenda-add-time-grid-maybe 28 0.0003810809 1.361...e-05 
org-agenda-fix-displayed-tags 112 0.000342384 3.057e-06 
org-agenda-fontify-priorities 1 0.00018465 0.00018465 
org-agenda-align-tags 1 0.000160119 0.000160119 org-agenda-get-day-face 
28 0.000156385 5.585...e-06 org-agenda-get-category-icon 112 
7.702...e-05 6.877...e-07 org-agenda-span-name 23 4.4484e-05 
1.934...e-06 org-agenda-span-to-ndays 1 2.3496e-05 2.3496e-05 
org-agenda-fit-window-to-buffer 1 2.0877e-05 2.0877e-05 
org-agenda-time-of-day-to-ampm-maybe 21 1.124...e-05 5.353...e-07 
org-agenda-set-mode-name 1 9.226e-06 9.226e-06 
org-agenda-mark-header-line 1 8.774e-06 8.774e-06 
org-agenda-reset-markers 1 4.829e-06 4.829e-06 org-agenda-deadline-face 
4 4.761e-06 1.19025e-06 org-agenda-update-agenda-type 1 1.575e-06 
1.575e-06 org-agenda-ndays-to-span 2 1.174e-06 5.87e-07 
org-agenda-mark-clocking-task 1 7.16e-07 7.16e-07 
org-agenda-use-sticky-p 1 5.02e-07 5.02e-07 |


I’m not sure if that says much though.

Version information:

 *

   Emacs: |GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+
   Version 3.18.9) of 2018-02-18|

 *

   Orgmode: |Org mode version 9.1.6 (9.1.6-44-ge6f891-elpaplus @
   /home/jx/.emacs.d/elpa/develop/org-plus-contrib-20180205/)|.

 *

   I’m using Spacemacs’  develop
   branch.

However, this problem happens on both Ubuntu 16.04 LTS and the latest 
MacOS. Actually it has persisted for a very long period of time so I 
doubt if it’s related to any particular Emacs/Org version.


Any help would be much appreciated!

Best regards,

Xiang

​

[O] bug#28263: bug#28263: 24.5; Org: `C-c LETTER' keys

[Drew Adams]

> Drew Adams  writes:
> 
> > No.  I'm saying that Org should not suggest that
> > users bind keys that are reserved for use by users
> > to Org commands.
> >
> > And it should not then present those keys in the doc.
> >
> > And it should not say anything about the doc using
> > those keys for illustrative purposes or assuming
> > that users have bound those keys.
> >
> > Org should do _nothing_ with such reserved keys.
> > It should not mention them at all in its doc.
> 
> This is your own interpretation of the two paragraphs in
> the Elisp manual that treat about reserved keys, IMO.

It's my opinion of what Org mode _should_ do.

And it coincides with what other libraries do.  And it
fits what the manual suggests.

Your opinion is apparently that Emacs (in the Org-mode
doc) should recommend that users sacrifice those keys
to Org.  We disagree about that.

You want Emacs to (1) tell users that these keys are
reserved for them to bind, BUT also to (2) recommend
that if they use Org mode (which most users probably
do now) then they should bind them to Org commands.
I don't want Emacs to do #2.  #1 is good; #2 is bad,
and it, in effect, undercuts #1.

In my opinion no library should suggest that users
sacrifice their reserved keys for that library.
Users are free to do that, of course.  But it's
impolite, IMO, for a library to recommend that they
do so.

Users aren't stupid - they can figure out, if they
end up using some commands often, that they might
want to bind them to keys, including perhaps to
their reserved keys.  They don't need a library to
pitch them that idea.  And newbie users might well
get the wrong idea that they really need to follow
that suggestion or they could have a "bad experience".

Libraries that are purely 3rd-party can of course
do anything they like (not that they should, but
they can).

But I'd offer the same opinion for purely 3rd-party
libraries: Don't recommend that users globally bind
their reserved keys for your mode.

Org mode is not only a 3rd-party library.  It is
now part of GNU Emacs.  All the more reason to be
nice to users.

> Anyway, for the record, I modified Org manual (for Org 9.2) so it
> doesn't assume anymore users followed advice and bound `C-c a', `C-c
> l'... In fact, I removed every reference to user reserved keybindings,

Very good.  Thank you for doing the right thing there.

> but one, in the following paragraphs:
>
>   For a better experience, the three Org commands ~org-store-link~,
>   ~org-capture~ and ~org-agenda~ ought to be accessible anywhere in
>   Emacs, not just in Org buffers.  To that effect, you need to bind
>   them
>   to globally available keys, like the ones reserved for users (see
>   [[info:elisp::Key%20Binding%20Conventions]]).  Here are suggested
>   bindings, please modify the keys to your own liking.
> 
>   #+begin_src emacs-lisp
> (global-set-key "\C-cl" 'org-store-link)
> (global-set-key "\C-ca" 'org-agenda)
> (global-set-key "\C-cc" 'org-capture)
>   #+end_src

Not good, IMHO.

And there is _no need_ to mention those keys.
It should be fine and enough to leave off the part
about ", like the ones reserved ... #+end_src."

That part's not needed for users to understand
that if they want global behavior then they can
bind global keys - which is the only message you
need to get across about those commands.

And, once again, those words shamefacedly suggest
that users use those keys.  Same problem.

Again:

> > Org should not suggest that users bind keys that
> > are reserved for use by users to Org commands.

Org is widely used.  Recommending that users use
those keys for Org is nearly tantamount to no
longer reserving them for users.  Not quite as bad
as actually binding them to Org commands on their
behalf (which would clearly contravene the guideline),
but almost as bad.

And totally unnecessary.

> I dare to think this is a good enough advice to belong to the manual,
> with enough safeguards to let users know what it entails. I also think
> it is fair, because the manual doesn't talk about these bindings anymore
> later on.

I'm on record, at least, as disagreeing with that.
One opinion.

Anyway, thank you for no longer having the rest of
the Org manual depend on the assumption that users
have sacrificed those keys to Org.

Perhaps someday someone else will finish the job by
removing the manual's suggestion that they should
make that sacrifice, "for a better experience".

Re: [O] Ridiculously long (2 minutes) startup time for org agenda

[Thierry Banel]

On 18/02/2018 13:38, JI Xiang wrote:
Hello, first time posting on the mailing list. I encountered a problem 
where my agenda view (`C-c a a`) is taking ridiculously long (nearly 2 
minutes) to be shown the first time. From the second time onwards, the 
time is about 11 seconds, which is still very long by any means.


I wondered whether it has something to do with me having many files in 
the agenda list, so I tried to restrict the list to just one file. But 
still the first call to org-agenda-list took 12 seconds. This 
shouldn't be normal, right?


The following are shown in the `Messages` buffer during the call.

```
Press key for agenda command:
Restoring clock data
Loading /home/jx/.emacs.d/.cache/org-clock-save.el (source)...done
[yas] Prepared just-in-time loading of snippets successfully.
Importmagic and/or epc not found. importmagic.el will not be working.
Setting up indent for shell type zsh
Indentation variables are now local.
Indentation setup for shell type zsh
Using vacuous schema
Shell native completion is disabled, using fallback
```

I'm not sure why they would be there, especially the "using vacuous 
schema" and "shell native completion" part. Are the messages related 
to some `#BEGIN_SRC` blocks in the org files? I don't think I would 
ever need source code blocks when I'm viewing an agenda buffer?


I posted the question [on 
Emacs.SE](https://emacs.stackexchange.com/questions/30489/what-could-cause-org-agenda-to-take-very-long-to-start-up) 
and somebody suggested me use `elp-instrument` to perform a profiling. 
The results are as follows:


```

Function Name, Call Count, Elapsed Time, Average Time

org-agenda 1   116.6048159   116.6048159
org-agenda-list 1   116.29427357  116.29427357
org-agenda-prepare 1   109.15345470  109.15345470
org-agenda-prepare-buffers 1   108.98258905 108.98258905
org-agenda-get-day-entries 12887.0089191339 0.0054417074
org-agenda-get-scheduled 12883.726361062 0.0028931374
org-agenda-get-deadlines 12882.1579713230 0.0016754435
org-agenda--timestamp-to-absolute 14544   1.1317418120 
7.781...e-05

org-agenda-get-timestamps 12880.3673404320 0.0002852021
org-agenda-get-sexps 12880.3438970410  0.0002670008
org-agenda-get-restriction-and-command 1 0.310503975   0.310503975
org-agenda-get-blocks 12880.3083237900  0.0002393818
org-agenda-prepare-window 1   0.157091024 0.157091024
org-agenda-skip 86240.0781296389  9.059...e-06
org-agenda-files 49  0.026090686   0.0005324629
org-agenda-finalize 1   0.013325178   0.013325178
org-agenda-mode 1   0.009848546   0.009848546
org-agenda-finalize-entries 23  0.006178961 0.0002686504
org-agenda-today-p 26040.0061717839  2.370...e-06
org-agenda-skip-eval 16968   0.0052723920  3.107...e-07
org-agenda-highlight-todo 112 0.0039840550 3.557...e-05
org-agenda-format-item 112 0.0038309749  3.420...e-05
org-agenda-new-marker 208 0.0031529359  1.515...e-05
org-agenda-format-date-aligned 28  0.0007373120 2.633...e-05
org-agenda-add-time-grid-maybe 28  0.0003810809 1.361...e-05
org-agenda-fix-displayed-tags 112 0.000342384 3.057e-06
org-agenda-fontify-priorities 1   0.00018465 0.00018465
org-agenda-align-tags 1   0.000160119   0.000160119
org-agenda-get-day-face 28  0.000156385   5.585...e-06
org-agenda-get-category-icon 112 7.702...e-05 6.877...e-07
org-agenda-span-name 23  4.4484e-051.934...e-06
org-agenda-span-to-ndays 1   2.3496e-052.3496e-05
org-agenda-fit-window-to-buffer 1   2.0877e-05 2.0877e-05
org-agenda-time-of-day-to-ampm-maybe 21  1.124...e-05 
5.353...e-07

org-agenda-set-mode-name 1   9.226e-06 9.226e-06
org-agenda-mark-header-line 1   8.774e-06 8.774e-06
org-agenda-reset-markers 1   4.829e-06 4.829e-06
org-agenda-deadline-face 4   4.761e-06 1.19025e-06
org-agenda-update-agenda-type 1   1.575e-06 1.575e-06
org-agenda-ndays-to-span 2   1.174e-06 5.87e-07
org-agenda-mark-clocking-task 1   7.16e-07 7.16e-07
org-agenda-use-sticky-p 1   5.02e-07  5.02e-07
```

I'm not sure if that says much though.

Version information:

- Emacs: `GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ 
Version 3.18.9) of 2018-02-18`


- Orgmode: `Org mode version 9.1.6 (9.1.6-44-ge6f891-elpaplus @ 
/home/jx/.emacs.d/elpa/develop/org-plus-contrib-20180205/)`.


- I'm using [Spacemacs'](https://github.com/syl20bnr/spacemacs) 
develop branch.


However, this problem happens on both Ubuntu 16.04 LTS and the latest 
MacOS. Actually it has persisted for a very long period of time so I 
doubt if it's related to any particular Emacs/Org 

[O] Ridiculously long (2 minutes) startup time for org agenda

[JI Xiang]

Hello, first time posting on the mailing list. I encountered a problem 
where my agenda view (`C-c a a`) is taking ridiculously long (nearly 2 
minutes) to be shown the first time. From the second time onwards, the 
time is about 11 seconds, which is still very long by any means.


I wondered whether it has something to do with me having many files in 
the agenda list, so I tried to restrict the list to just one file. But 
still the first call to org-agenda-list took 12 seconds. This shouldn't 
be normal, right?


The following are shown in the `Messages` buffer during the call.

```
Press key for agenda command:
Restoring clock data
Loading /home/jx/.emacs.d/.cache/org-clock-save.el (source)...done
[yas] Prepared just-in-time loading of snippets successfully.
Importmagic and/or epc not found. importmagic.el will not be working.
Setting up indent for shell type zsh
Indentation variables are now local.
Indentation setup for shell type zsh
Using vacuous schema
Shell native completion is disabled, using fallback
```

I'm not sure why they would be there, especially the "using vacuous 
schema" and "shell native completion" part. Are the messages related to 
some `#BEGIN_SRC` blocks in the org files? I don't think I would ever 
need source code blocks when I'm viewing an agenda buffer?


I posted the question [on 
Emacs.SE](https://emacs.stackexchange.com/questions/30489/what-could-cause-org-agenda-to-take-very-long-to-start-up) 
and somebody suggested me use `elp-instrument` to perform a profiling. 
The results are as follows:


```

    Function Name, Call Count, Elapsed Time, Average Time

    org-agenda 1   116.6048159   116.6048159
    org-agenda-list 1   116.29427357  116.29427357
    org-agenda-prepare 1   109.15345470  109.15345470
    org-agenda-prepare-buffers 1   108.98258905  108.98258905
    org-agenda-get-day-entries 1288    7.0089191339  0.0054417074
    org-agenda-get-scheduled 1288    3.726361062   0.0028931374
    org-agenda-get-deadlines 1288    2.1579713230  0.0016754435
    org-agenda--timestamp-to-absolute 14544   1.1317418120  
7.781...e-05

    org-agenda-get-timestamps 1288    0.3673404320  0.0002852021
    org-agenda-get-sexps 1288    0.3438970410  0.0002670008
    org-agenda-get-restriction-and-command 1   0.310503975   
0.310503975

    org-agenda-get-blocks 1288    0.3083237900  0.0002393818
    org-agenda-prepare-window 1   0.157091024   0.157091024
    org-agenda-skip 8624    0.0781296389  9.059...e-06
    org-agenda-files 49  0.026090686   0.0005324629
    org-agenda-finalize 1   0.013325178   0.013325178
    org-agenda-mode 1   0.009848546   0.009848546
    org-agenda-finalize-entries 23  0.006178961   0.0002686504
    org-agenda-today-p 2604    0.0061717839  2.370...e-06
    org-agenda-skip-eval 16968   0.0052723920  3.107...e-07
    org-agenda-highlight-todo 112 0.0039840550  3.557...e-05
    org-agenda-format-item 112 0.0038309749  3.420...e-05
    org-agenda-new-marker 208 0.0031529359  1.515...e-05
    org-agenda-format-date-aligned 28  0.0007373120  2.633...e-05
    org-agenda-add-time-grid-maybe 28  0.0003810809  1.361...e-05
    org-agenda-fix-displayed-tags 112 0.000342384   3.057e-06
    org-agenda-fontify-priorities 1   0.00018465    0.00018465
    org-agenda-align-tags 1   0.000160119   0.000160119
    org-agenda-get-day-face 28  0.000156385   5.585...e-06
    org-agenda-get-category-icon 112 7.702...e-05  6.877...e-07
    org-agenda-span-name 23  4.4484e-05    1.934...e-06
    org-agenda-span-to-ndays 1   2.3496e-05    2.3496e-05
    org-agenda-fit-window-to-buffer 1   2.0877e-05    2.0877e-05
    org-agenda-time-of-day-to-ampm-maybe 21  1.124...e-05  
5.353...e-07

    org-agenda-set-mode-name 1   9.226e-06 9.226e-06
    org-agenda-mark-header-line 1   8.774e-06 8.774e-06
    org-agenda-reset-markers 1   4.829e-06 4.829e-06
    org-agenda-deadline-face 4   4.761e-06 1.19025e-06
    org-agenda-update-agenda-type 1   1.575e-06 1.575e-06
    org-agenda-ndays-to-span 2   1.174e-06 5.87e-07
    org-agenda-mark-clocking-task 1   7.16e-07  7.16e-07
    org-agenda-use-sticky-p 1   5.02e-07  5.02e-07
```

I'm not sure if that says much though.

Version information:

- Emacs: `GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 
3.18.9) of 2018-02-18`


- Orgmode: `Org mode version 9.1.6 (9.1.6-44-ge6f891-elpaplus @ 
/home/jx/.emacs.d/elpa/develop/org-plus-contrib-20180205/)`.


- I'm using [Spacemacs'](https://github.com/syl20bnr/spacemacs) develop 
branch.


However, this problem happens on both Ubuntu 16.04 LTS and the latest 
MacOS. Actually it has persisted for a very long period of time so I 
doubt if it's related to any particular 

Re: [O] Images in HTML export

[Thomas S. Dye]

Aloha Eric,

Eric S Fraga writes:


On Saturday, 17 Feb 2018 at 12:01, Thomas S. Dye wrote:

Aloha all,

Using an up-to-date Org mode from Elpa, I'm not getting inline
images when the description part of the Org link is itself a 
link.
Instead, the browser shows the alt text, which points to the 
link.


[...]

I have org-html-inline-images set to t, and am viewing the 
output

in an up-to-date Mozilla Firefox browser.


Maybe check org-html-inline-image-rules to ensure that it covers 
.jpeg

files?


Thanks for the suggestion.

As is often the case, Org mode is doing just what I tell it to do 
and the problem is that I've been telling it to do the wrong 
thing. Sorry for the noise.


All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com

[O] [PATCH] adding flexibility to ASCII bar plot

[Thierry Banel]

Someone named novoid on GitHub suggested to add some flexibility to the 
ASCII bar plot.

Attached is a patch implementing it.

Example:

| 1 | WWW  |
| 2 | WW   |
| 3 | W|
| 4 |  |
#+TBLFM: $2='(orgtbl-ascii-draw $1 0 @>$1 12)

Note the @>$1 cell reference passed to the MAX parameter.
Previously, only hard coded values like 4 could be used.

Regards
Thierry











>From f12eea7d34bf7d6445dc8a03923264fef73279a2 Mon Sep 17 00:00:00 2001
From: Thierry Banel 
Date: Sun, 18 Feb 2018 17:59:16 +0100
Subject: [PATCH] Added flexibility for ASCII bar plots

* org-table.el (orgtbl-ascii-draw): MIN and MAX
  parameters now accept cell formulas such as @>$2
* manual.org, org.texi: reflect added feature
  in reference documentation.

Thanks to github/novoid for suggesting this
---
 contrib/manual.org | 3 ++-
 doc/org.texi   | 3 ++-
 lisp/org-table.el  | 4 
 3 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/contrib/manual.org b/contrib/manual.org
index 8a7a0b9..0db2ddf 100644
--- a/contrib/manual.org
+++ b/contrib/manual.org
@@ -3022,7 +3022,8 @@ Draw an ASCII bar in a table.
 
 {{{var(MIN)}}} is the value displayed as an empty bar.  {{{var(MAX)}}}
 is the value filling all the {{{var(WIDTH)}}}.  Sources values outside
-this range are displayed as =too small= or =too large=.
+this range are displayed as =too small= or =too large=.  They can be
+constant values, or references to cells, like {{{var(@>$2)}}}.
 
 {{{var(WIDTH)}}} is the number of characters of the bar plot.  It
 defaults to =12=.
diff --git a/doc/org.texi b/doc/org.texi
index 9b4a4de..603fb42 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -3353,7 +3353,8 @@ The formula is an elisp call:
 @item MIN MAX
   are the minimal and maximal values displayed.  Sources values
   outside this range are displayed as @samp{too small}
-  or @samp{too large}.
+  or @samp{too large}.  They can be constant values, or references
+  to cells, like @samp{@>$2}.
 
 @item WIDTH
   is the width in characters of the bar-plot.  It defaults to @samp{12}.
diff --git a/lisp/org-table.el b/lisp/org-table.el
index 9ab15e6..9060400 100644
--- a/lisp/org-table.el
+++ b/lisp/org-table.el
@@ -5672,6 +5672,10 @@ of regular ascii characters."
 	 (len(1- (length characters)))
 	 (value  (float (if (numberp value)
 value (string-to-number value
+	 (min(float (if (numberp min)
+min (string-to-number min
+	 (max(float (if (numberp max)
+max (string-to-number max
 	 (relative   (/ (- value min) (- max min)))
 	 (steps  (round (* relative width len
 (cond ((< steps 0) "too small")
-- 
2.1.4

Re: [O] Images in HTML export

[Eric S Fraga]

On Saturday, 17 Feb 2018 at 12:01, Thomas S. Dye wrote:
> Aloha all,
>
> Using an up-to-date Org mode from Elpa, I'm not getting inline 
> images when the description part of the Org link is itself a link. 
> Instead, the browser shows the alt text, which points to the link.

[...]

> I have org-html-inline-images set to t, and am viewing the output 
> in an up-to-date Mozilla Firefox browser.

Maybe check org-html-inline-image-rules to ensure that it covers .jpeg
files?

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-118-g134243


signature.asc
Description: PGP signature

Re: [O] N tasks per week with sexp diary entries

[Gour]

On Sun, 18 Feb 2018 09:42:03 +0100
Julius Dittmar  wrote:

> What I do in this case is create three (different) weekly entries.
> They all repeat with a ++1ŵ schedule (starting on, say, a Monday).
> That way I can tick them off one by one. As those are displayed in
> direct sequence in the agena I can easily see where I stand
> exercise-wise.

Thanks a lot for the suggestion!! That seems to be good-enough for my purpose. 
:-)


Sincerely,
Gour

-- 
Even a man of knowledge acts according to his own nature, for
everyone follows the nature he has acquired from the three modes.
What can repression accomplish?

Re: [O] N tasks per week with sexp diary entries

[Julius Dittmar]

On 18.02.2018 08:43, Gour wrote:

In my case, there is no fixed schedule per week, but it simply depends
on my free time which does vary from week to week and I only want to be
sure that I did fixed number of workouts per week. Moreover, if e.g.
the program does last 10 weeks, I most probably want to just continue
with it from the 11th week, iow. continuous exercising. So, it seems I
have to create schedule manually...


What I do in this case is create three (different) weekly entries. They 
all repeat with a ++1ŵ schedule (starting on, say, a Monday). That way I 
can tick them off one by one. As those are displayed in direct sequence 
in the agena I can easily see where I stand exercise-wise.


Perhaps that's a work-around you can live with too.

Julius