Re: example paper written in org completely
Hello, The thread is going far from the original post, and I'm pushing it further. Eric, sorry for that. But this is an interesting topic so just to have some more thoughts on this I'm jumping in. Org-mode has enhanced my organizational skills and I have still a lot to learn here. To continue this conversation, we need a philosopher here one I'm far from being one, so please take my comments lightly. On Saturday, 19 Jun 2021 at 09:26, Tim Cross wrote: > A major pitfall with todo lists and priorities is that we fail to make > the distinction between important and urgent tasks. What ends up > happening is that all our time gets consumed by urgent tasks and we > never get time to address important tasks. Unfortunately, it is the > important tasks which, once completed, will reduce the number or time > taken to deal with urgent tasks - we end up being more reactive and > proactive. First how do we make the distinction between urgent and important tasks? Many tasks are important because they are urgent but who and what defines their urgency? > > In our case, we all hated having to update/edit the course guides in MS > Office because it was painful and time consuming, but urgent. However, > nobody belt they had the time to fix matters, despite us all agreeing it > was important. This reminds me of the Aesop fable the [1] Mice in Council, which pushes the importance part to the extreme. [1]: https://aesopsfables.org/F184_The-Mice-in-Council.html. A way to solve this might be identify some heroes and compensate them for doing their job. Too many heroes never have their inner calling. > > What would have been really great is if we had more Emacs users. We You are in good company here. > could then just have used org mode for the base format and even less > work would have been required to convert from MS Office, but that will > never happen. On the up side, I do see more and more ideas originally > germinated in an Emacs environment finding there way into other tool > chains, so perhaps the environments of the future won't suck quite as > much as they might if MS Office had been the only source for > inspiration! As the Beta v VHS war demonstrated, great technology is not > enough, you also need to factor in marketing and advertising budgets of > the competition! [2] Monday.com raised $574 Million, in an IPO this month. Many times I'm forced to use pictures as replacement for table and I am still struggling to add more DONE states there. [2]: https://www.bloomberg.com/news/articles/2021-06-10/monday-com-prices-u-s-ipo-above-range-at-155-a-share I suspect that it would be difficult to compete with a front-end with org-mode at the back, but again, I'm telling more than I know. Best regards, -- Jeremie Juste
Re: publishing: no default publishing function, or symbol is not defined
Hi, Chris,
"Symbol's function definition is void" means there is no such function
defined.
Try org-html-publish-to-html instead.
Yours,
Christian
Christopher W. Ryan via General discussions about Org-mode. writes:
> I'm making my first foray into publishing a project. I'm running GNU
> Emacs 26.2 (build 1, x86_64-w64-mingw32) of 2019-04-13, on Windows 10.
>
> I've defined a single project, just to try it out and learn. Here is
> the relevant portion of my .emacs file
>
>
> ;; Projects and publishing
> ;;
> (setq org-publish-project-alist
> '(("CaseInvestigationTrainingAndReferenceManual"
> :base-directory
> "E:/DATA/BCHD/CD/ChinaCoronavirus2019/CommCare/Sandbox/"
> :publishing-directory
> "E:/DATA/BCHD/CD/ChinaCoronavirus2019/CommCare/Sandbox/StagingArea")))
>
>
> There is one org file in /Sandbox, called
> WorkAreaForIndexingTrainingAndReferenceManual-7-June.org
>
> (as the filename suggests, I'm mostly interested in learning how to make
> an index).
>
> If I execute C-c C-e P a whilie in the org file I am trying to publish,
> I get an error message that there is "No publishing function chosen". I
> thought org-publish-org-to-html was the default, as described here:
>
> https://www.gnu.org/software/emacs/manual/html_node/org/Publishing-action.html
>
> But if I modify the relevant section of my .emacs file like this,
> specifying a publishing action:
>
> ;; Projects and publishing
> ;;
> (setq org-publish-project-alist
> '(("CaseInvestigationTrainingAndReferenceManual"
> :base-directory
> "E:/DATA/BCHD/CD/ChinaCoronavirus2019/CommCare/Sandbox/"
> :publishing-directory
> "E:/DATA/BCHD/CD/ChinaCoronavirus2019/CommCare/Sandbox/StagingArea"
> :publishing-function org-publish-org-to-html)))
>
> and try again, I get an error message that I can't figure out: "Symbol’s
> function definition is void: org-publish-org-to-html"
>
> Grateful for any guidance.
>
> Thanks.
>
> --Chris Ryan
Re: publishing: no default publishing function, or symbol is not defined
Hi Christopher,
Christopher W. Ryan" via "General discussions about Org-mode. writes:
> I'm making my first foray into publishing a project. I'm running GNU
> Emacs 26.2 (build 1, x86_64-w64-mingw32) of 2019-04-13, on Windows 10.
>
> I've defined a single project, just to try it out and learn.
As Christian Moe said, the function you need is
`org-html-publish-to-html'.
In case it helps, I keep this blog about typography and TeX (in spanish),
made with org-publish: https://lunotipia.juanmanuelmacias.com/index.html
The blog's public repository is at:
https://gitlab.com/maciaschain/lunotipia
And this is the org-publish configuration for the blog:
;; lunotipia
("lunotipia-notes"
;; Org files
:base-directory "~/Git/lunotipia/org/"
:base-extension "org"
;; HTML files
:publishing-directory "~/Git/lunotipia/public/"
:publishing-function org-html-publish-to-html
:recursive t
:auto-sitemap t
:sitemap-title "Textos publicados"
:sitemap-function my-sitemap-function-lunotipia
:sitemap-filename "entradas.org"
:sitemap-style list
:sitemap-sort-files anti-chronologically
:exclude "org-rss\\|theindex\\|acerca-de\.org"
:makeindex t
:html-postamble mi-postamble)
;; static files
("lunotipia-static"
:base-directory "~/Git/lunotipia/org/images/"
:base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf"
:publishing-directory "~/Git/lunotipia/public/images/"
:recursive t
:publishing-function org-publish-attachment)
And my custom sitemap function:
(defun my-sitemap-function-lunotipia (title list)
"Return sitemap using TITLE and LIST returned by
`org-blog-sitemap-format-entry'."
(concat "#+TITLE: " title "\n\n"
"#+SETUPFILE:" "~/Git/lunotipia/html-lunotipia.setup"
"\n#+SETUPFILE:" "~/Git/gnutas/macros-gnutas.setup"
"\n#+AUTHOR:" "Juan Manuel Macías"
"\n#+LANGUAGE:" "es"
"\n#+begin_archive\n"
(mapconcat (lambda (li)
(format "@@html:@@ %s @@html:@@" (car li)))
(seq-filter #'car (cdr list))
"\n")
"\n#+end_archive\n"
"\n#+begin_export html"
"\n"
"\n"
"\n"
"\nAcerca de..."
"\n"
"\n"
"\nhttps://maciaschain.gitlab.io/lunotipia/rss.xml\";>RSS"
"\n"
"\n#+end_export\n"))
Best regards,
Juan Manuel
Re: example paper written in org completely
On Saturday, 19 Jun 2021 at 11:58, Jeremie Juste wrote: > The thread is going far from the original post, and I'm pushing it > further. Eric, sorry for that. > > But this is an interesting topic so just to have some more thoughts on > this I'm jumping in. It is indeed an interesting topic so no worries! Serendipity... I'm enjoying seeing where it's going. Org mode is more than just a toy: it's an enabling technology for a very wide range of activities and that's what makes it incredibly powerful. -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-566-gf0198e : Latest paper written in org: https://arxiv.org/abs/2106.05096
[PATCH] Re: Bug: org-agenda-buffer-name wrongly persists [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Here's a local-tested fix to the bug described previously. The attached patch does not change anything about the overall handling of the agenda buffer names, it only fixes org-follow-timestamp-link to introduce a let-binding similar to what the standard org-dispatcher does. >From 2c0166449de2f4252435ecfea8a2d1287eafc04b Mon Sep 17 00:00:00 2001 From: Ingo Lohmar Date: Sat, 19 Jun 2021 17:04:56 +0200 Subject: [PATCH] org.el (org-follow-timestamp-link): Do not set global agenda name The tmp value for the agenda buffer name is used in `org-agenda-list' to set `org-agenda-buffer-name'. Wrap the call in a let-binding for this symbol (like the agenda dispatcher does), since otherwise it inadvertently sets the global value. --- lisp/org.el | 36 +++- 1 file changed, 19 insertions(+), 17 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 1bd9e02eb..4fd8b6fa6 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -9165,24 +9165,26 @@ or to another Org file, automatically push the old position onto the ring." (defvar org-agenda-start-on-weekday) (defun org-follow-timestamp-link () "Open an agenda view for the time-stamp date/range at point." - (cond - ((org-at-date-range-p t) -(let ((org-agenda-start-on-weekday) - (t1 (match-string 1)) - (t2 (match-string 2)) tt1 tt2) - (setq tt1 (time-to-days (org-time-string-to-time t1)) - tt2 (time-to-days (org-time-string-to-time t2))) + ;; Avoid changing the global value. + (let ((org-agenda-buffer-name org-agenda-buffer-name)) +(cond + ((org-at-date-range-p t) + (let ((org-agenda-start-on-weekday) + (t1 (match-string 1)) + (t2 (match-string 2)) tt1 tt2) + (setq tt1 (time-to-days (org-time-string-to-time t1)) + tt2 (time-to-days (org-time-string-to-time t2))) + (let ((org-agenda-buffer-tmp-name + (format "*Org Agenda(a:%s)" + (concat (substring t1 0 10) "--" (substring t2 0 10) + (org-agenda-list nil tt1 (1+ (- tt2 tt1)) + ((org-at-timestamp-p 'lax) (let ((org-agenda-buffer-tmp-name - (format "*Org Agenda(a:%s)" - (concat (substring t1 0 10) "--" (substring t2 0 10) - (org-agenda-list nil tt1 (1+ (- tt2 tt1)) - ((org-at-timestamp-p 'lax) -(let ((org-agenda-buffer-tmp-name - (format "*Org Agenda(a:%s)" (substring (match-string 1) 0 10 - (org-agenda-list nil (time-to-days (org-time-string-to-time - (substring (match-string 1) 0 10))) - 1))) - (t (error "This should not happen" + (format "*Org Agenda(a:%s)" (substring (match-string 1) 0 10 + (org-agenda-list nil (time-to-days (org-time-string-to-time + (substring (match-string 1) 0 10))) + 1))) + (t (error "This should not happen") ;;; Following file links -- 2.30.2
Re: example paper written in org completely
Hey Tim, Some things to consider: - Org Roam - Org Brain - Even the philosophy of taking ideas from "Getting Things Done" to get a good system of tasks Also, I would label your headers for todo list items as "tasks" rather then "todo list items". Why? Because its a different mindset altogether and way more inviting. I do this for my work and personal org todo lists. I am in the camp where you have a giant org docs, since I think having multiple files for the same overall structured goal is a bit silly and unnecessary. I recommend having a giant todo list org doc for your work stuff. And then have a separate one called 'life.org' where you keep all your personal notes. This is so that in the future you can quickly search through your notes for anything you might have done but you forgot about. This helps me a ton as I record a lot of ideas that sometimes turn into cool projects either now, or later. Plus, organize your headers accordingly. Ex: * Things To Do ** Week Of (Current Week) * COMPLETED_TASKS: 2021 ** Week Of (Week That Has Already Taken Place) If you learn how to shuffle entire headings around your Org document accordingly, you can get a good workflow going. This means that you will have to learn how to use 'org-refile', as it will help you move tasks around and refile them in the "Getting Things Done" easily. You can even make org capture templates to quickly insert your ideas (Lord knows how many times I almost went to sleep and had amazing ideas that I'm super thankful that I wrote down). I also recommend using the Helm package, as its auto-completion and other features help SO much when it comes to org-mode tasks, and blows the other packages out of the water. Hope this helps :) ~ Sam On Sat, Jun 19, 2021, at 9:58 AM, Jeremie Juste wrote: > Hello, > > The thread is going far from the original post, and I'm pushing it > further. Eric, sorry for that. > > But this is an interesting topic so just to have some more thoughts on this > I'm jumping > in. Org-mode has enhanced my organizational skills and I have still a > lot to learn here. To continue this conversation, we need a philosopher > here one I'm far from being one, so please take my comments lightly. > > On Saturday, 19 Jun 2021 at 09:26, Tim Cross wrote: > > A major pitfall with todo lists and priorities is that we fail to make > > the distinction between important and urgent tasks. What ends up > > happening is that all our time gets consumed by urgent tasks and we > > never get time to address important tasks. Unfortunately, it is the > > important tasks which, once completed, will reduce the number or time > > taken to deal with urgent tasks - we end up being more reactive and > > proactive. > > First how do we make the distinction between urgent and important tasks? > Many tasks are important because they are urgent but who and what > defines their urgency? > > > > > In our case, we all hated having to update/edit the course guides in MS > > Office because it was painful and time consuming, but urgent. However, > > nobody belt they had the time to fix matters, despite us all agreeing it > > was important. > > This reminds me of the Aesop fable the [1] Mice in Council, which pushes the > importance part to the extreme. > > [1]: https://aesopsfables.org/F184_The-Mice-in-Council.html. > > A way to solve this might be identify some heroes and compensate them for > doing their job. Too many heroes never have their inner calling. > > > > > What would have been really great is if we had more Emacs users. We > You are in good company here. > > > could then just have used org mode for the base format and even less > > work would have been required to convert from MS Office, but that will > > never happen. On the up side, I do see more and more ideas originally > > germinated in an Emacs environment finding there way into other tool > > chains, so perhaps the environments of the future won't suck quite as > > much as they might if MS Office had been the only source for > > inspiration! As the Beta v VHS war demonstrated, great technology is not > > enough, you also need to factor in marketing and advertising budgets of > > the competition! > > [2] Monday.com raised $574 Million, in an IPO this month. Many times > I'm forced to use pictures as replacement for > table and I am still struggling to add more DONE states there. > > [2]: > https://www.bloomberg.com/news/articles/2021-06-10/monday-com-prices-u-s-ipo-above-range-at-155-a-share > > I suspect that it would be difficult to compete with a front-end with > org-mode at the back, but again, I'm telling more than I know. > > Best regards, > -- > Jeremie Juste > >
Re: publishing: no default publishing function, or symbol is not defined
Ah, I see I wrote the :publishing-function statement incorrectly. Thanks
to both of you.
But is there not a default publishing action, that requires no explicit
:publishing-function statement? This part of the documentation says
there is:
https://orgmode.org/manual/Publishing-action.html#Publishing-action
But I gave this a try:
(setq org-publish-project-alist
'(("CaseInvestigationTrainingAndReferenceManual"
:base-directory
"E:/DATA/BCHD/CD/ChinaCoronavirus2019/CommCare/Sandbox/"
:publishing-directory
"E:/DATA/BCHD/CD/ChinaCoronavirus2019/CommCare/Sandbox/StagingArea"
:publishing-function org-html-publish-to-html)))
and I got the expected output in the expected place: a file called
"E:/DATA/BCHD/CD/ChinaCoronavirus2019/CommCare/Sandbox/StagingArea/WorkAreaForIndexingTrainingAndReferenceManual-7-June.html
However, when I add this line:
:makeindex 1
so with a non-null value of :makeindex
The output consists *only* of the index: a file called theindex.html.
It looks like the expected index to the document, but the document
itself is not generated. How do I get both?
Thanks.
--Chris
Juan Manuel Macías wrote:
> Hi Christopher,
>
> Christopher W. Ryan" via "General discussions about Org-mode. writes:
>
>> I'm making my first foray into publishing a project. I'm running GNU
>> Emacs 26.2 (build 1, x86_64-w64-mingw32) of 2019-04-13, on Windows 10.
>>
>> I've defined a single project, just to try it out and learn.
>
> As Christian Moe said, the function you need is
> `org-html-publish-to-html'.
>
> In case it helps, I keep this blog about typography and TeX (in spanish),
> made with org-publish: https://lunotipia.juanmanuelmacias.com/index.html
>
> The blog's public repository is at:
> https://gitlab.com/maciaschain/lunotipia
>
> And this is the org-publish configuration for the blog:
>
> ;; lunotipia
> ("lunotipia-notes"
> ;; Org files
> :base-directory "~/Git/lunotipia/org/"
> :base-extension "org"
> ;; HTML files
> :publishing-directory "~/Git/lunotipia/public/"
> :publishing-function org-html-publish-to-html
> :recursive t
> :auto-sitemap t
> :sitemap-title "Textos publicados"
> :sitemap-function my-sitemap-function-lunotipia
> :sitemap-filename "entradas.org"
> :sitemap-style list
> :sitemap-sort-files anti-chronologically
> :exclude "org-rss\\|theindex\\|acerca-de\.org"
> :makeindex t
> :html-postamble mi-postamble)
>
> ;; static files
> ("lunotipia-static"
> :base-directory "~/Git/lunotipia/org/images/"
> :base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf"
> :publishing-directory "~/Git/lunotipia/public/images/"
> :recursive t
> :publishing-function org-publish-attachment)
>
> And my custom sitemap function:
>
> (defun my-sitemap-function-lunotipia (title list)
> "Return sitemap using TITLE and LIST returned by
> `org-blog-sitemap-format-entry'."
> (concat "#+TITLE: " title "\n\n"
> "#+SETUPFILE:" "~/Git/lunotipia/html-lunotipia.setup"
> "\n#+SETUPFILE:" "~/Git/gnutas/macros-gnutas.setup"
> "\n#+AUTHOR:" "Juan Manuel Macías"
> "\n#+LANGUAGE:" "es"
> "\n#+begin_archive\n"
> (mapconcat (lambda (li)
> (format "@@html:@@ %s @@html:@@" (car li)))
>(seq-filter #'car (cdr list))
>"\n")
> "\n#+end_archive\n"
> "\n#+begin_export html"
> "\n"
> "\n"
> "\n"
> "\nAcerca de..."
> "\n"
> "\n"
> "\n href=\"https://maciaschain.gitlab.io/lunotipia/rss.xml\";>RSS"
> "\n"
> "\n#+end_export\n"))
>
> Best regards,
>
> Juan Manuel
>
Re: [External Email] Re: publishing: no default publishing function, or symbol is not defined
Oops, spoke to soon about the structure of the index. Here is a section
of theindex.html
I
Incarceration
Incarceration
Interview
Interview
Interview
Interview
Interview
Isolation
Isolation
Isolation
I would expect each named entry in an index to appear once, with, if
necessary, multiple links next to it for all the places that index tag
occurs in the main document. At least, that's how the indices in books
work. Can the same be done in org mode?
Thanks.
--Chris
Juan Manuel Macías wrote:
> Hi Christopher,
>
> Christopher W. Ryan" via "General discussions about Org-mode. writes:
>
>> I'm making my first foray into publishing a project. I'm running GNU
>> Emacs 26.2 (build 1, x86_64-w64-mingw32) of 2019-04-13, on Windows 10.
>>
>> I've defined a single project, just to try it out and learn.
>
> As Christian Moe said, the function you need is
> `org-html-publish-to-html'.
>
> In case it helps, I keep this blog about typography and TeX (in spanish),
> made with org-publish: https://lunotipia.juanmanuelmacias.com/index.html
>
> The blog's public repository is at:
> https://gitlab.com/maciaschain/lunotipia
>
> And this is the org-publish configuration for the blog:
>
> ;; lunotipia
> ("lunotipia-notes"
> ;; Org files
> :base-directory "~/Git/lunotipia/org/"
> :base-extension "org"
> ;; HTML files
> :publishing-directory "~/Git/lunotipia/public/"
> :publishing-function org-html-publish-to-html
> :recursive t
> :auto-sitemap t
> :sitemap-title "Textos publicados"
> :sitemap-function my-sitemap-function-lunotipia
> :sitemap-filename "entradas.org"
> :sitemap-style list
> :sitemap-sort-files anti-chronologically
> :exclude "org-rss\\|theindex\\|acerca-de\.org"
> :makeindex t
> :html-postamble mi-postamble)
>
> ;; static files
> ("lunotipia-static"
> :base-directory "~/Git/lunotipia/org/images/"
> :base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf"
> :publishing-directory "~/Git/lunotipia/public/images/"
> :recursive t
> :publishing-function org-publish-attachment)
>
> And my custom sitemap function:
>
> (defun my-sitemap-function-lunotipia (title list)
> "Return sitemap using TITLE and LIST returned by
> `org-blog-sitemap-format-entry'."
> (concat "#+TITLE: " title "\n\n"
> "#+SETUPFILE:" "~/Git/lunotipia/html-lunotipia.setup"
> "\n#+SETUPFILE:" "~/Git/gnutas/macros-gnutas.setup"
> "\n#+AUTHOR:" "Juan Manuel Macías"
> "\n#+LANGUAGE:" "es"
> "\n#+begin_archive\n"
> (mapconcat (lambda (li)
> (format "@@html:@@ %s @@html:@@" (car li)))
>(seq-filter #'car (cdr list))
>"\n")
> "\n#+end_archive\n"
> "\n#+begin_export html"
> "\n"
> "\n"
> "\n"
> "\nAcerca de..."
> "\n"
> "\n"
> "\n href=\"https://maciaschain.gitlab.io/lunotipia/rss.xml\";>RSS"
> "\n"
> "\n#+end_export\n"))
>
> Best regards,
>
> Juan Manuel
>
Re: [External Email] Re: publishing: no default publishing function, or symbol is not defined
Hi Christopher, Christopher W. Ryan" via "General discussions about Org-mode. writes: > I would expect each named entry in an index to appear once, with, if > necessary, multiple links next to it for all the places that index tag > occurs in the main document. At least, that's how the indices in books > work. Can the same be done in org mode? I'm afraid that in HTML that is not possible. Page numbers are used in books to refer to an index entry, but on a web site we don't have page numbers: Where would we apply the links? What I usually do with my web index is: use first-level entries for the general concept and second or third level entries for concepts more concrete. P.ej: In document A: #+INDEX: GNU Emacs!external packages!projectile In document B: #+INDEX: GNU Emacs!external packages!helm Links to document A and B go to projectile and Helm Anyway, I think in this scenario it's better to use tags, but org-publish doesn't provide tags out of the box. You need to do some elisp hacking to get something like blog tags in your web site. Best regards, Juan Manuel
Re: Default entry in org-src-block-faces
Hi, Augusto Stoffel writes: Would it make sense to allow a default entry (t FACE) in `org-src-block-faces', to be applied to all src blocks without a more specific entry in that alist? There seems to be no other way to specify a face to be applied to all src blocks, and only src blocks. Makes sense to me. I also wonder if there's any reason for the `org-block' face not to apply to "greater" blocks. -- Sébastien Miquel
