Re: [O] Generating sitemap: ‘org-publish-cache-get’ called, but no cache present

[Vikas Rawal]

> 
>> I have been using the following code block to generate a sitemap for my 
>> org-jkyll based blog.
>> 
>> #+begin_src emacs-lisp :results output silent :exports none :cache yes
>>  (org-publish-sitemap
>>   (assoc "indblog" org-publish-project-alist)
>>   "sitemap.org")
>> #+end_src
>> 
>> I had not generated the sitemap for a while, and now I find that it
>> ends with the following message, and sitemap.org 
>> is not recreated.
> 
> `org-publish-sitemap' is not meant to be called directly. It assumes
> project is properly set-up, which is done in its caller,
> `org-publish-projects'.
> 
> So, why don't you simply publish "indblog" project?

I use this to avoid having to publish the whole project each time I add a post. 
I would like to just publish the current file, and update the sitemap by 
running the above code block. Is that not okay?

Vikas

Re: [O] change in calling remote code blocks?

[edgar]

Message: 1
Date: Mon, 15 Jan 2018 10:07:33 -0800
From: John Kitchin 

with a syntax like:

#+call: si.org:figure-1() :wrap html


And C-c C-c on that line would call a code block named figure-1 in the 
file

si.org and insert the results.

in org 9.1.6, this does nothing. Does anyone know if this got changed, 
and

if there is a new way to do that?

John


You may try loading the file into the library of babel 
(org-babel-lob-ingest). Then, you can call the function without a 
reference to the file


#+CAPTION: s1.org
#+BEGIN_SRC org
  ,#+NAME: figure-1
  ,#+BEGIN_SRC python
return 2 + 2
  ,#+END_SRC
#+END_SRC

#+CAPTION: t.org
#+BEGIN_SRC org
  ,#+CALL: figure-1() :wrap html

  ,#+RESULTS:
  ,#+BEGIN_html
  4
  ,#+END_html
#+END_SRC


Message: 7
Date: Mon, 15 Jan 2018 23:49:54 +0100
From: Nicolas Goaziou 
To: John Kitchin 

This sounds like a bug.

Or missed feature?



It does ring a bell. However, I couldn't find any reference to this
syntax or behaviour in the manual. Am I missing something?


I only found the evident:
#+BEGIN_QUOTE
By calling a named code block(2) from an Org mode buffer or
a table.  Org can call the named ‘src’ code blocks from the
*current Org mode buffer* or from the *“Library of Babel”*
#+END_QUOTE
(bold added by me).



Message: 8
Date: Mon, 15 Jan 2018 16:08:26 -0800
From: John Kitchin 



babel documentation somewhere. I confirmed it does work in 8.2.10, e.g.
just with emacs -Q.


It would be nice if it did :) .

Thanks for working so well on Org. I have good news: Someone to whom I 
introduced Emacs is now using it! (not my advisor... yet).


-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  

Re: [O] Generating sitemap: ‘org-publish-cache-get’ called, but no cache present

[Nicolas Goaziou]

Hello,

Vikas Rawal  writes:

> I use this to avoid having to publish the whole project each time
> I add a post.

This is the default behaviour when publishing a project: it only
re-publishes modified files and the sitemap/index.

> I would like to just publish the current file, and
> update the sitemap by running the above code block. Is that not okay?

Does the suggestion above solve fulfill your need?

Regards,

-- 
Nicolas Goaziou

Re: [O] Orgmode repeater intervals with end date

[Nicolas Goaziou]

Hello,

torys.ander...@gmail.com (Tory S. Anderson) writes:

> Thanks; oddly, that works.
>
> *** TODO Personal Meeting
> DEADLINE: <2018-01-10 Wed 16:00 .+2w>--<2018-04-18 Wed>

FWIW, this syntax is not supported. It could do anything.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: Broken orgmode.org links in doc/misc/org.texi and lisp/org

[Tim Landscheidt]

Nicolas Goaziou  wrote:

> […]

> Thank you! However, these patches do not seem to apply cleanly on maint
> tip. Could you rebase them against maint HEAD and send them again?

Sure.

> Also, if you haven't signed FSF papers, you need to add TINYCHANGE at
> the end of each commit message.

According to Emacs's CONTRIBUTE (referenced by
README_contribute), that should be
"Copyright-paperwork-exempt: yes"?  (Is
mk/make_emacs_changelog still used for anything?)

Tim

[O] Bug: Determining file name of included files for ox-publish caching

[Joseph Carter Osborn]

I have an org-mode document that imports sections from other org-mode
documents, like so:

#+BEGIN_QUOTE

* Part 1
#+INCLUDE: "./other.org::*Heading"
# and so on

#+END_QUOTE

I set up publishing for this document and encounter errors like this in
my *messages* buffer:

#+BEGIN_QUOTE
org-publish-cache-ctime-of-src: No such file: 
"/Users/jcosborn/path/to/project/“./other.org"
#+END_QUOTE

If I leave off the "::*..." component of the include I have no such
errors.  I believe the culprit is the capture in the regular expression
on ox-publish.el:1173, but I'm not sure why the bug exhibits in this
particular way with the stray quote being thrown into the string.
It seems like the regular expression should treat included org files
specially and split the string to avoid treating searches as part of the
file.

A minimal example has two org files "including.org" and "included.org",
where "included.org" has a heading "* Hello" and "including.org" just
has '#+INCLUDE: "./included.org::*Hello"'.

Then set up a trivial project like:

#+BEGIN_SRC elisp
(setq org-publish-project-alist
  '(("test"
:base-directory "~/test/"
:publishing-directory "~/test/"
:publishing-function org-latex-publish-to-latex)))
#+END_SRC

and try to publish it, or run:

#+BEGIN_SRC elisp
(org-publish-cache-file-needs-publishing "including.org")
#+END_SRC

And you, too, should encounter the same error.

For now I will work around it by turning off caching, but I do like the
caching feature so I hope to be able to use it again someday.

Emacs  : GNU Emacs 25.3.1 (x86_64-apple-darwin16.7.0, NS appkit-1504.83 Version 
10.12.6 (Build 16G29))
 of 2017-09-13
Package: Org mode version 9.1.6 (9.1.6-16-g86a382-elpaplus @ 
/Users/jcosborn/.emacs.d/elpa/org-plus-contrib-20180115/)

Thanks to the mailing list, as always, for being such an excellent
resource!

[O] Bug: org-store-link gives lisp error "wrong-type-argument" [9.1.3 (release_9.1.3-171-gb6df86)]

[Stefan-W. Hahn]

Hello,

when storing a link of an bibtex entry I get an lisp error. This happens
because I have more then one function for storing bibtex links and
org-store-link calls completing-read with initial-input as symbol not as
string.

This has been changed in commit

commit 0cc231a7bb9f261640205943ddeb42ad8cefc43d
Author: Nicolas Goaziou 
Date:   Fri Dec 1 19:33:35 2017 +0100


Not working:
(completing-read "what: " '(a b c) nil t 'a)

Working:
(completing-read "what: " '(a b c) nil t "a")

In the version before the given commit then initial-input parameter was
the "symbol-name" of the value.

The following change repairs the problem, perhaps this is sufficient.

#+begin_src diff
diff --git a/lisp/org.el b/lisp/org.el
index 061776065..51e95a6c8 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -9197,7 +9197,7 @@ org-store-link
 (cdr (assoc-string
   (completing-read
"Which function for creating the link? "
-   (mapcar #'car results-alist) nil t name)
+   (mapcar #'car results-alist) nil t (symbol-name 
name))
   results-alist)))
  t
(setq link (plist-get org-store-link-plist :link))
#+end_src


With kind regards,
Stefan

Emacs  : GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
 of 2017-12-24
Package: Org mode version 9.1.3 (release_9.1.3-171-gb6df86 @ 
/home/hs/.emacs.d/lib/org-mode/lisp/)

-- 
Stefan-W. Hahn  It is easy to make things.
It is hard to make things simple.

Re: [O] Bug: org-store-link gives lisp error "wrong-type-argument" [9.1.3 (release_9.1.3-171-gb6df86)]

[Nicolas Goaziou]

Hello,

"Stefan-W. Hahn"  writes:

> Hello,
>
> when storing a link of an bibtex entry I get an lisp error. This happens
> because I have more then one function for storing bibtex links and
> org-store-link calls completing-read with initial-input as symbol not as
> string.
>
> This has been changed in commit
>
> commit 0cc231a7bb9f261640205943ddeb42ad8cefc43d
> Author: Nicolas Goaziou 
> Date:   Fri Dec 1 19:33:35 2017 +0100
>
>
> Not working:
> (completing-read "what: " '(a b c) nil t 'a)
>
> Working:
> (completing-read "what: " '(a b c) nil t "a")
>
> In the version before the given commit then initial-input parameter was
> the "symbol-name" of the value.
>
> The following change repairs the problem, perhaps this is sufficient.

Fixed. Thank you for the report and the patch.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: Determining file name of included files for ox-publish caching

[Nicolas Goaziou]

Hello,

Joseph Carter Osborn  writes:

> I have an org-mode document that imports sections from other org-mode
> documents, like so:
>
> #+BEGIN_QUOTE
>
> * Part 1
> #+INCLUDE: "./other.org::*Heading"
> # and so on
>
> #+END_QUOTE
>
>
> I set up publishing for this document and encounter errors like this in
> my *messages* buffer:
>
> #+BEGIN_QUOTE
> org-publish-cache-ctime-of-src: No such file: 
> "/Users/jcosborn/path/to/project/./other.org"
> #+END_QUOTE
>
>
> If I leave off the "::*..." component of the include I have no such
> errors.  I believe the culprit is the capture in the regular expression
> on ox-publish.el:1173, but I'm not sure why the bug exhibits in this
> particular way with the stray quote being thrown into the string.
> It seems like the regular expression should treat included org files
> specially and split the string to avoid treating searches as part of the
> file.
>
> A minimal example has two org files "including.org" and "included.org",
> where "included.org" has a heading "* Hello" and "including.org" just
> has '#+INCLUDE: "./included.org::*Hello"'.
>
> Then set up a trivial project like:
>
> #+BEGIN_SRC elisp
> (setq org-publish-project-alist
>   '(("test"
> :base-directory "~/test/"
> :publishing-directory "~/test/"
> :publishing-function org-latex-publish-to-latex)))
> #+END_SRC
>
>
> and try to publish it, or run:
>
> #+BEGIN_SRC elisp
> (org-publish-cache-file-needs-publishing "including.org")
> #+END_SRC
>
> And you, too, should encounter the same error.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: Broken orgmode.org links in doc/misc/org.texi and lisp/org

[Nicolas Goaziou]

Tim Landscheidt  writes:

> According to Emacs's CONTRIBUTE (referenced by
> README_contribute), that should be
> "Copyright-paperwork-exempt: yes"?  

Our commits do not appear in Emacs' history, so we are not required to
follow their conventions for commit messages.

> (Is mk/make_emacs_changelog still used for anything?)

I don't think so.

Regards,

Re: [O] Bug: Broken orgmode.org links in doc/misc/org.texi and lisp/org

[Tim Landscheidt]

Nicolas Goaziou  wrote:

>> According to Emacs's CONTRIBUTE (referenced by
>> README_contribute), that should be
>> "Copyright-paperwork-exempt: yes"?  

> Our commits do not appear in Emacs' history, so we are not required to
> follow their conventions for commit messages.

Could you then please document TINYCHANGE in
README_contribute?  Merci!

Tim

Re: [O] Bug: Broken orgmode.org links in doc/misc/org.texi and lisp/org

[Tim Landscheidt]

Nicolas Goaziou  wrote:

> […]

> Thank you! However, these patches do not seem to apply cleanly on maint
> tip. Could you rebase them against maint HEAD and send them again?

> […]

I have attached the patches rebased on maint, with
TINYCHANGE.  (I've switched patches #4 and #5 as #4 is
easier to review than #5.)

Patch #1 updates only URLs from http to https that I consid-
er "uncontroversial".

Patch #2 makes some links to the manual and external URLs in
docstrings clickable.

Patch #3 updates URLs from http to https in old entries of
etc/ORG-NEWS.  There is an argument for keeping them as is,
and I have no strong opinion on that.

Patch #4 just adds a trailing slash to two links to
https://orgmode.org/worg/org-contrib/babel.

Patch #5 updates URLs from http to https in source code and
test cases.  These need to be reviewed more carefully, espe-
cially as there probably should remain some test cases for
http URLs.  (I get a test failure for
test-org/timestamp-from-time, but AFAICT this is unrelated.)

Tim
>From defa7770f7b136d6ec122f91ee84a471d6a83462 Mon Sep 17 00:00:00 2001
From: Tim Landscheidt 
Date: Tue, 16 Jan 2018 16:22:00 +
Subject: [PATCH 1/5] Use https for links to orgmode.org

TINYCHANGE
---
 Makefile |  2 +-
 README_ELPA  |  4 +-
 README_git   |  4 +-
 README_maintainer|  2 +-
 contrib/lisp/ob-csharp.el|  2 +-
 contrib/lisp/ob-eukleides.el |  2 +-
 contrib/lisp/ob-fomus.el |  2 +-
 contrib/lisp/ob-mathomatic.el|  2 +-
 contrib/lisp/ob-oz.el|  2 +-
 contrib/lisp/ob-tcl.el   |  2 +-
 contrib/lisp/ob-vbnet.el |  2 +-
 contrib/lisp/org-bibtex-extras.el|  2 +-
 contrib/lisp/org-collector.el|  2 +-
 contrib/lisp/org-contribdir.el   |  2 +-
 contrib/lisp/org-depend.el   |  2 +-
 contrib/lisp/org-effectiveness.el|  2 +-
 contrib/lisp/org-eval-light.el   |  2 +-
 contrib/lisp/org-eval.el |  2 +-
 contrib/lisp/org-index.el|  2 +-
 contrib/lisp/org-learn.el|  2 +-
 contrib/lisp/org-license.el  |  2 +-
 contrib/lisp/org-link-edit.el| 16 
 contrib/lisp/org-mairix.el   |  2 +-
 contrib/lisp/org-man.el  |  2 +-
 contrib/lisp/org-mew.el  |  2 +-
 contrib/lisp/org-notmuch.el  |  2 +-
 contrib/lisp/org-passwords.el|  2 +-
 contrib/lisp/org-screenshot.el   |  2 +-
 contrib/lisp/org-sudoku.el   |  2 +-
 contrib/lisp/org-track.el|  6 +--
 contrib/lisp/org-vm.el   |  2 +-
 contrib/lisp/org-wikinodes.el|  2 +-
 contrib/lisp/org-wl.el   |  2 +-
 contrib/lisp/ox-rss.el   |  2 +-
 contrib/orgmanual.org| 52 
 contrib/scripts/org-docco.org|  6 +--
 contrib/scripts/staticmathjax/README.org |  2 +-
 doc/orgguide.texi| 70 
 etc/ORG-NEWS |  4 +-
 etc/styles/README|  2 +-
 lisp/ob-C.el |  2 +-
 lisp/ob-J.el |  2 +-
 lisp/ob-R.el |  2 +-
 lisp/ob-asymptote.el |  2 +-
 lisp/ob-awk.el   |  2 +-
 lisp/ob-calc.el  |  2 +-
 lisp/ob-clojure.el   |  2 +-
 lisp/ob-comint.el|  2 +-
 lisp/ob-coq.el   |  2 +-
 lisp/ob-core.el  |  2 +-
 lisp/ob-css.el   |  2 +-
 lisp/ob-ditaa.el |  2 +-
 lisp/ob-dot.el   |  2 +-
 lisp/ob-ebnf.el  |  2 +-
 lisp/ob-emacs-lisp.el|  2 +-
 lisp/ob-eval.el  |  2 +-
 lisp/ob-exp.el   |  2 +-
 lisp/ob-forth.el |  2 +-
 lisp/ob-fortran.el   |  2 +-
 lisp/ob-gnuplot.el   |  2 +-
 lisp/ob-groovy.el|  2 +-
 lisp/ob-haskell.el   |  2 +-
 lisp/ob-hledger.el   |  2 +-
 lisp/ob-io.el|  2 +-
 lisp/ob-java.el  |  2 +-
 lisp/ob-js.el|  2 +-
 lisp/ob-keys.el  |  2 +-
 lisp/ob-latex.el |  2 +-
 lisp/ob-ledger.el|  2 +-
 lisp/ob-lilypond.el  |  4 +-
 lisp/ob-lisp.el  |  2 +-
 lisp/ob-lob.el   |  2 +-
 lisp/ob-lua.el   |  2 +-
 lisp/ob-makefile.el  |  2 +-
 lisp/ob-m

[O] [PATCH] Remove obsolete mk/list-hooks.pl

[Tim Landscheidt]

The functionality of mk/list-hooks.pl has been implemented by mk/eldo.el.

* mk/list-hooks.pl: Remove.

TINYCHANGE
---
 mk/list-hooks.pl | 32 
 1 file changed, 32 deletions(-)
 delete mode 100755 mk/list-hooks.pl

diff --git a/mk/list-hooks.pl b/mk/list-hooks.pl
deleted file mode 100755
index ffacd7c79..0
-- 
2.13.6

[O] Emacs repo comment about org-element's use of avl-tree--*

[Kyle Meyer]

Hello,

The commit below was made in Emacs's master branch (fe15532eef).  I'm
posting it here for review/discussion rather than backporting it.

-- >8 --
From: Stefan Monnier 
Date: Thu, 11 Jan 2018 11:33:03 -0500
Subject: [PATCH] * lisp/org/org-element.el: Add comment about use of internal
 functions

---
 lisp/org/org-element.el | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/lisp/org/org-element.el b/lisp/org/org-element.el
index 7a40d6933c..844349c2fc 100644
--- a/lisp/org/org-element.el
+++ b/lisp/org/org-element.el
@@ -4950,6 +4950,7 @@ org-element--cache-compare
 (defsubst org-element--cache-root ()
   "Return root value in cache.
 This function assumes `org-element--cache' is a valid AVL tree."
+  ;; FIXME: Why use internal functions of avl-tree?
   (avl-tree--node-left (avl-tree--dummyroot org-element--cache)))
 
 
@@ -4978,6 +4979,7 @@ org-element--cache-find
(aref (car org-element--cache-sync-requests) 0)))
(node (org-element--cache-root))
lower upper)
+;; FIXME: Why use internal functions of avl-tree?
 (while node
   (let* ((element (avl-tree--node-data node))
 (begin (org-element-property :begin element)))
-- 
2.11.0

Re: [O] Equation references in HTML export

[Thibault Marin]

> To avoid having to hack the code, you could try using the mathtools
> package and ask it to only number equations that are referenced:
>
> \usepackage{mathtools}  
> \mathtoolsset{showonlyrefs}  

Thanks, if there is a mechanism to alter the preamble when creating the
image, that may be a preferable approach.  I'll try to look into this.

Re: [O] Equation references in HTML export

[Eric S Fraga]

On Thursday, 18 Jan 2018 at 22:09, Thibault Marin wrote:
> Thanks, if there is a mechanism to alter the preamble when creating the
> image, that may be a preferable approach.  I'll try to look into this.

Have a look at org-format-latex-header.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-352-g92176c


signature.asc
Description: PGP signature