[O] olpath containing italics
the entry headline is /amazon/. note the //. not sure if this will work if programs or elisp uses the olpath. [i do not use any.] :ARCHIVE_OLPATH: housing/shop//amazon//household and foods including filters and pillow protectors/bed -- /pillow protectors/ etc. -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html The disease DOES progress. MANY people have died from it. And ANYBODY can get it at any time.
Re: [O] refreshing pictures that are results of code blocks
oh. :] i was looking forward to viewing the refreshing pictures you spoke of. wish i could help. On 5/15/19, Alan Schmitt wrote: > Hello, > > I'm playing with picture generating code like this: > > #+begin_src python :results file :session :var > matplot_lib_filename="figure2.png" :exports both > import matplotlib.pyplot as plt > > data = [14.0, 7.6, 11.2, 12.8, 12.5, 9.9, 14.9, 9.4, 16.9, 10.2, > 14.9, 18.1, 7.3, 9.8, 10.9, 12.2, 9.9, 2.9, 2.8, 15.4, 15.7, 9.7, > 13.1, 13.2, 12.3, 11.7, 16.0, 12.4, 17.9, 12.2, 16.2, 18.7, 8.9, > 11.9, 12.1, 14.6, 12.1, 4.7, 3.9, 16.9, 16.8, 11.3, 14.4, 15.7, > 14.0, 13.6, 18.0, 13.6, 19.9, 13.7, 17.0, 20.5, 9.9, 12.5, 13.2, > 16.1, 13.5, 6.3, 6.4, 17.6, 19.1, 12.8, 15.5, 16.3, 15.2, 14.6, > 19.1, 14.4, 21.4, 15.1, 19.6, 21.7, 11.3, 15.0, 14.3, 16.8, 14.0, > 6.8, 8.2, 19.9, 20.4, 14.6, 16.4, 18.7, 16.8, 15.8, 20.4, 15.8, > 22.4, 16.2, 20.3, 23.4, 12.1, 15.5, 15.4, 18.4, 15.7, 10.2, 8.9, > 21.0] > > plt.clf() > plt.hist(data, bins=10, edgecolor='black') > plt.grid(True) > plt.axis([0, 25, 0, 25]) > > plt.savefig(matplot_lib_filename) > matplot_lib_filename > #+end_src > > and it works great when I evaluate it: it creates a link to the > picture, > and when I hit Enter on the link, the picture is displayed in the > buffer. > > The problem is when I modify the code block and run it again, if I > hit > Enter on the resulting link, I see the old picture. The new one is > there > (if I open it, it is modified), but somehow the old picture is > cached. > > Is there a way to disable this cache? > > Thanks, > > Alan > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html The disease DOES progress. MANY people have died from it. And ANYBODY can get it at any time.
Re: [O] [PATCH] Ruby tests
Nicolas Goaziou writes: >> Ruby tests have been failing for quite some time, here's my fix. > > Feel free to push these changes if they fix tests for you. I no longer have the commit bit since the server software was changed. If it still requires an account on the server then I don't intend to create one, either. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] [PATCH] Add :target option for the TOC keyword
Hi! Here's a patch to allow table of contents to target a specified headline. I've added tests for HTML, ASCII, Markdown, and ODT export. I should have copyright assignment papers already on file. Does it work for anyone other than me? =) >From 81035b85a10ec62d7a8ddc594349189e97346960 Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Wed, 15 May 2019 14:22:05 -0400 Subject: [PATCH 1/1] Add :target option for the TOC keyword * doc/org-manual.org, etc/ORG_NEWS: Document :target option for the TOC keyword. * lisp/ox-ascii.el (org-ascii-keyword): Added :target to the TOC keyword. (org-ascii--build-toc): Changed LOCAL argument to SCOPE. * lisp/ox-html.el (org-html-keyword): Added :target to the TOC keyword. * lisp/ox-md.el (org-md-keyword): Added :target to the TOC keyword. (org-md--build-toc): Changed LOCAL argument to SCOPE. * lisp/ox-odt.el (org-odt-keyword): Added :target to the TOC keyword. * testing/examples/toc-with-fuzzy-target.org: New example file for testing target headlines by fuzzy matching. * testing/examples/toc-with-target.org: New example file for testing target headlines by CUSTOM_ID. * testing/lisp/test-ox-html.el: New file. * testing/lisp/test-ox-md.el: New file. * testing/lisp/test-ox-odt.el: New file. * testing/lisp/test-ox.el (test-org-export/collect-headlines): Added tests for specifying scope by CUSTOM_ID or by fuzzy matching. * testing/org-test.el (org-test-toc-with-target-file): New. (org-test-toc-with-fuzzy-target-file): New. --- doc/org-manual.org | 16 +++ etc/ORG-NEWS | 16 +++ lisp/ox-ascii.el | 27 +--- lisp/ox-html.el| 17 +++- lisp/ox-md.el | 27 +--- lisp/ox-odt.el | 17 +++- testing/examples/toc-with-fuzzy-target.org | 12 + testing/examples/toc-with-target.org | 12 + testing/lisp/test-ox-html.el | 51 ++ testing/lisp/test-ox-md.el | 51 ++ testing/lisp/test-ox-odt.el| 51 ++ testing/lisp/test-ox.el| 50 + testing/org-test.el| 6 +++ 13 files changed, 335 insertions(+), 18 deletions(-) create mode 100644 testing/examples/toc-with-fuzzy-target.org create mode 100644 testing/examples/toc-with-target.org create mode 100644 testing/lisp/test-ox-html.el create mode 100644 testing/lisp/test-ox-md.el create mode 100644 testing/lisp/test-ox-odt.el diff --git a/doc/org-manual.org b/doc/org-manual.org index 54b89e5bf..9f3fae308 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -11551,6 +11551,22 @@ file requires the inclusion of the titletoc package. Because of compatibility issues, titletoc has to be loaded /before/ hyperref. Customize the ~org-latex-default-packages-alist~ variable. +The following example inserts a table of contents that links to the +children of the specified target. + +#+begin_example +,* Target + :PROPERTIES: + :CUSTOM_ID: TargetSection + :END: +,** Heading A +,** Heading B +,* Another section +,#+TOC: headlines 1 :target "#TargetSection" +#+end_example + +The =:target= attribute is supported in HTML, Markdown, ODT, and ASCII export. + Use the =TOC= keyword to generate list of tables---respectively, all listings---with captions. diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS index 541559e64..95358ca7b 100644 --- a/etc/ORG-NEWS +++ b/etc/ORG-NEWS @@ -212,6 +212,22 @@ This attribute overrides the =:width= and =:height= attributes. [[https://orgmode.org/img/org-mode-unicorn-logo.png]] #+end_example +*** Allow specifying the target for a table of contents + +The =+TOC= keyword now accepts a =:target:= attribute that specifies +the headline to use for making the table of contents. + +#+begin_example +,* Target + :PROPERTIES: + :CUSTOM_ID: TargetSection + :END: +,** Heading A +,** Heading B +,* Another section +,#+TOC: headlines 1 :target "#TargetSection" +#+end_example + ** New functions *** ~org-dynamic-block-insert-dblock~ diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el index 7917e3dad..969f632b0 100644 --- a/lisp/ox-ascii.el +++ b/lisp/ox-ascii.el @@ -731,7 +731,7 @@ caption keyword." (org-export-data caption info)) (org-ascii--current-text-width element info) info) -(defun org-ascii--build-toc (info n keyword local) +(defun org-ascii--build-toc (info n keyword scope) "Return a table of contents. INFO is a plist used as a communication channel. @@ -742,10 +742,10 @@ depth of the table. Optional argument KEYWORD specifies the TOC keyword, if any, from which the table of contents generation has been initiated. -When optional argument LOCAL is non-nil, build a table of -contents according to the current headline." +When optional argument SCOPE is non-nil, build a table of +contents according to the
[O] Add :target option for the TOC keyword
Hi! Here's a patch to allow table of contents to target a specified headline. I've added tests for HTML, ASCII, Markdown, and ODT export. I should have copyright assignment papers already on file. Does it work for anyone other than me? =) >From 81035b85a10ec62d7a8ddc594349189e97346960 Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Wed, 15 May 2019 14:22:05 -0400 Subject: [PATCH 1/1] Add :target option for the TOC keyword * doc/org-manual.org, etc/ORG_NEWS: Document :target option for the TOC keyword. * lisp/ox-ascii.el (org-ascii-keyword): Added :target to the TOC keyword. (org-ascii--build-toc): Changed LOCAL argument to SCOPE. * lisp/ox-html.el (org-html-keyword): Added :target to the TOC keyword. * lisp/ox-md.el (org-md-keyword): Added :target to the TOC keyword. (org-md--build-toc): Changed LOCAL argument to SCOPE. * lisp/ox-odt.el (org-odt-keyword): Added :target to the TOC keyword. * testing/examples/toc-with-fuzzy-target.org: New example file for testing target headlines by fuzzy matching. * testing/examples/toc-with-target.org: New example file for testing target headlines by CUSTOM_ID. * testing/lisp/test-ox-html.el: New file. * testing/lisp/test-ox-md.el: New file. * testing/lisp/test-ox-odt.el: New file. * testing/lisp/test-ox.el (test-org-export/collect-headlines): Added tests for specifying scope by CUSTOM_ID or by fuzzy matching. * testing/org-test.el (org-test-toc-with-target-file): New. (org-test-toc-with-fuzzy-target-file): New. --- doc/org-manual.org | 16 +++ etc/ORG-NEWS | 16 +++ lisp/ox-ascii.el | 27 +--- lisp/ox-html.el| 17 +++- lisp/ox-md.el | 27 +--- lisp/ox-odt.el | 17 +++- testing/examples/toc-with-fuzzy-target.org | 12 + testing/examples/toc-with-target.org | 12 + testing/lisp/test-ox-html.el | 51 ++ testing/lisp/test-ox-md.el | 51 ++ testing/lisp/test-ox-odt.el| 51 ++ testing/lisp/test-ox.el| 50 + testing/org-test.el| 6 +++ 13 files changed, 335 insertions(+), 18 deletions(-) create mode 100644 testing/examples/toc-with-fuzzy-target.org create mode 100644 testing/examples/toc-with-target.org create mode 100644 testing/lisp/test-ox-html.el create mode 100644 testing/lisp/test-ox-md.el create mode 100644 testing/lisp/test-ox-odt.el diff --git a/doc/org-manual.org b/doc/org-manual.org index 54b89e5bf..9f3fae308 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -11551,6 +11551,22 @@ file requires the inclusion of the titletoc package. Because of compatibility issues, titletoc has to be loaded /before/ hyperref. Customize the ~org-latex-default-packages-alist~ variable. +The following example inserts a table of contents that links to the +children of the specified target. + +#+begin_example +,* Target + :PROPERTIES: + :CUSTOM_ID: TargetSection + :END: +,** Heading A +,** Heading B +,* Another section +,#+TOC: headlines 1 :target "#TargetSection" +#+end_example + +The =:target= attribute is supported in HTML, Markdown, ODT, and ASCII export. + Use the =TOC= keyword to generate list of tables---respectively, all listings---with captions. diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS index 541559e64..95358ca7b 100644 --- a/etc/ORG-NEWS +++ b/etc/ORG-NEWS @@ -212,6 +212,22 @@ This attribute overrides the =:width= and =:height= attributes. [[https://orgmode.org/img/org-mode-unicorn-logo.png]] #+end_example +*** Allow specifying the target for a table of contents + +The =+TOC= keyword now accepts a =:target:= attribute that specifies +the headline to use for making the table of contents. + +#+begin_example +,* Target + :PROPERTIES: + :CUSTOM_ID: TargetSection + :END: +,** Heading A +,** Heading B +,* Another section +,#+TOC: headlines 1 :target "#TargetSection" +#+end_example + ** New functions *** ~org-dynamic-block-insert-dblock~ diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el index 7917e3dad..969f632b0 100644 --- a/lisp/ox-ascii.el +++ b/lisp/ox-ascii.el @@ -731,7 +731,7 @@ caption keyword." (org-export-data caption info)) (org-ascii--current-text-width element info) info) -(defun org-ascii--build-toc (info n keyword local) +(defun org-ascii--build-toc (info n keyword scope) "Return a table of contents. INFO is a plist used as a communication channel. @@ -742,10 +742,10 @@ depth of the table. Optional argument KEYWORD specifies the TOC keyword, if any, from which the table of contents generation has been initiated. -When optional argument LOCAL is non-nil, build a table of -contents according to the current headline." +When optional argument SCOPE is non-nil, build a table of +contents according to the
[O] refreshing pictures that are results of code blocks
Hello, I'm playing with picture generating code like this: #+begin_src python :results file :session :var matplot_lib_filename="figure2.png" :exports both import matplotlib.pyplot as plt data = [14.0, 7.6, 11.2, 12.8, 12.5, 9.9, 14.9, 9.4, 16.9, 10.2, 14.9, 18.1, 7.3, 9.8, 10.9, 12.2, 9.9, 2.9, 2.8, 15.4, 15.7, 9.7, 13.1, 13.2, 12.3, 11.7, 16.0, 12.4, 17.9, 12.2, 16.2, 18.7, 8.9, 11.9, 12.1, 14.6, 12.1, 4.7, 3.9, 16.9, 16.8, 11.3, 14.4, 15.7, 14.0, 13.6, 18.0, 13.6, 19.9, 13.7, 17.0, 20.5, 9.9, 12.5, 13.2, 16.1, 13.5, 6.3, 6.4, 17.6, 19.1, 12.8, 15.5, 16.3, 15.2, 14.6, 19.1, 14.4, 21.4, 15.1, 19.6, 21.7, 11.3, 15.0, 14.3, 16.8, 14.0, 6.8, 8.2, 19.9, 20.4, 14.6, 16.4, 18.7, 16.8, 15.8, 20.4, 15.8, 22.4, 16.2, 20.3, 23.4, 12.1, 15.5, 15.4, 18.4, 15.7, 10.2, 8.9, 21.0] plt.clf() plt.hist(data, bins=10, edgecolor='black') plt.grid(True) plt.axis([0, 25, 0, 25]) plt.savefig(matplot_lib_filename) matplot_lib_filename #+end_src and it works great when I evaluate it: it creates a link to the picture, and when I hit Enter on the link, the picture is displayed in the buffer. The problem is when I modify the code block and run it again, if I hit Enter on the resulting link, I see the old picture. The new one is there (if I open it, it is modified), but somehow the old picture is cached. Is there a way to disable this cache? Thanks, Alan signature.asc Description: PGP signature
Re: [O] Show weekday in daily agenda view
Hey there, thank you very much, that is now perfect: I use (setq org-agenda-format-date ;; (1) "%Y-%m-%d %A ") ;; (1) (the (1) in brackets gives me an indication of where I got the initial code from) and it gives me 2019-05-15 Mittwoch all I want :) Cheers and have a good week J Richard Lawrence writes: > Hi Johanna, > > "Prof. Dr. Johanna May" writes: > >> thanks for pointing me at the variable org-agenda-format-date. There >> was a line in my dotemacs that included a formatting without the >> weekday (something like %y-%w-%d). > > Ah, ok, great! > >> I could not figure out how the name-of-the-weekday format would be >> called. But for now I'm fine with returning to the default which gives >> me an English date including the weekday. > > You probably want "%a" or "%A" somewhere in there, if you want a > locale-specific name of the weekday. See the docstring for the > format-time-string function.
Re: [O] Show weekday in daily agenda view
Dear Johanna, for me (setq calendar-day-name-array ["Sonntag" "Montag" "Dienstag" "Mittwoch" "Donnerstag" "Freitag" "Samstag"] calendar-month-name-array ["Januar" "Februar" "Maerz" "April" "Mai" "Juni" "Juli" "August" "September" "Oktober" "November" "Dezember"]) in .emacs results in German names. best regards, Heinz Prof. Dr. Johanna May wrote/hat geschrieben on/am 15.05.2019 07:42: Hi Richard, thanks for pointing me at the variable org-agenda-format-date. There was a line in my dotemacs that included a formatting without the weekday (something like %y-%w-%d). I could not figure out how the name-of-the-weekday format would be called. But for now I'm fine with returning to the default which gives me an English date including the weekday. Cheers, J Richard Lawrence writes: Hi Johanna, johanna@th-koeln.de writes: maybe I did not search the right way in google alias startpage. But I could not figure out how to write next to the date e.g. 2000-04-01 the weekday, i.e. the specific day of the week. It would come very handy to have the date displayed as 2019-05-14 Tu and 2019-05-15 We and so on. Or even have it spelled out as 2019-05-14 Tuesday. Probably there is a way of setting this. How does it work? Hmm. My daily agenda (the default one) starts like this: Day-agenda (W20): Tuesday14 May 2019 and tasks, etc. are listed below that. I don't think I've ever customized this. Are you seeing something different? Or maybe you mean something else by "agenda"? If you're talking about Org's built-in agenda, you might want to take a look at the `org-agenda-format-date' variable. Mine is set to the org-agenda-format-date-aligned function, which I assume is what outputs the example above. If you're just talking about timestamps in Org files, you might want to look at the `org-time-stamp-custom-formats' and `org-display-custom-times' variables. Hope that helps! -- Heinz Tüchler +436605653878
Re: [O] Show weekday in daily agenda view
Hi Johanna, "Prof. Dr. Johanna May" writes: > thanks for pointing me at the variable org-agenda-format-date. There > was a line in my dotemacs that included a formatting without the > weekday (something like %y-%w-%d). Ah, ok, great! > I could not figure out how the name-of-the-weekday format would be > called. But for now I'm fine with returning to the default which gives > me an English date including the weekday. You probably want "%a" or "%A" somewhere in there, if you want a locale-specific name of the weekday. See the docstring for the format-time-string function. -- Best, Richard
Re: [O] LaTex Output with Index
On Tuesday, 14 May 2019 at 23:58, Robert Love wrote:
> However, I have one hitch. How do I generate an index with an entry
> that has an “@“ symbol in it?
Unfortunately, this is beyond my latex-fu. May have something to do
with @ being a protected symbol. If you want to play, you could try
#+index: {\makeatletter @} term
but this could lead you down a rabbit hole. Not sure how org & LaTeX &
makeindex will interact...
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.2-290-g300f15
Re: [O] Show weekday in daily agenda view
Hi Richard, thanks for pointing me at the variable org-agenda-format-date. There was a line in my dotemacs that included a formatting without the weekday (something like %y-%w-%d). I could not figure out how the name-of-the-weekday format would be called. But for now I'm fine with returning to the default which gives me an English date including the weekday. Cheers, J Richard Lawrence writes: > Hi Johanna, > > johanna@th-koeln.de writes: > >> maybe I did not search the right way in google alias startpage. But I >> could not figure out how to write next to the date e.g. 2000-04-01 the >> weekday, i.e. the specific day of the week. It would come very handy to >> have the date displayed as 2019-05-14 Tu and 2019-05-15 We and so on. Or >> even have it spelled out as 2019-05-14 Tuesday. >> >> Probably there is a way of setting this. How does it work? > > Hmm. My daily agenda (the default one) starts like this: > > Day-agenda (W20): > Tuesday14 May 2019 > > and tasks, etc. are listed below that. I don't think I've ever > customized this. Are you seeing something different? Or maybe you mean > something else by "agenda"? > > If you're talking about Org's built-in agenda, you might want to take a > look at the `org-agenda-format-date' variable. Mine is set to the > org-agenda-format-date-aligned function, which I assume is what outputs > the example above. > > If you're just talking about timestamps in Org files, you might want to > look at the `org-time-stamp-custom-formats' and > `org-display-custom-times' variables. > > Hope that helps!
