Re: Bug: invalid example for org-export-define-backend's :menu-entry argument [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Upon further testing, the third and fourth elements of the function should instead be wrapped in a single set of parentheses. There should only be three elements in the list. On Tue, Aug 3, 2021 at 12:36 AM Zachary Kanfer wrote: > Ox.el contains the function org-export-define-backend. One of its > keyword arguments is :menu-entry. The examples given include > (https://code.orgmode.org/bzg/org-mode/src/master/lisp/ox.el#L1214) > > '(?l "Export to LaTeX" > (?p "As PDF file" org-latex-export-to-pdf) > (?o "As PDF file and open" > (lambda (a s v b) >(if a (org-latex-export-to-pdf t s v b) > (org-open-file > (org-latex-export-to-pdf nil s v b)) > > This is invalid for two reasons: > > 1. The ?p and ?o elements should be wrapped in an extra layer of > parentheses. For example, the ?p element should be ((?p "As PDF file" > org-latex-export-to-pdf)). > 2. There is an extra parenthesis at the end of the block. > > I cannot submit a patch, as my employer currently will not sign the > copyright assignment. I hope someone else picks this up and fixes it. > > > > > Emacs : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version > 3.24.20, cairo version 1.16.0) > of 2021-07-09 > Package: Org mode version 9.4.4 (release_9.4.4 @ > /usr/local/share/emacs/28.0.50/lisp/org/) >
Bug: invalid example for org-export-define-backend's :menu-entry argument [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Ox.el contains the function org-export-define-backend. One of its keyword arguments is :menu-entry. The examples given include (https://code.orgmode.org/bzg/org-mode/src/master/lisp/ox.el#L1214) '(?l "Export to LaTeX" (?p "As PDF file" org-latex-export-to-pdf) (?o "As PDF file and open" (lambda (a s v b) (if a (org-latex-export-to-pdf t s v b) (org-open-file (org-latex-export-to-pdf nil s v b)) This is invalid for two reasons: 1. The ?p and ?o elements should be wrapped in an extra layer of parentheses. For example, the ?p element should be ((?p "As PDF file" org-latex-export-to-pdf)). 2. There is an extra parenthesis at the end of the block. I cannot submit a patch, as my employer currently will not sign the copyright assignment. I hope someone else picks this up and fixes it. Emacs : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, cairo version 1.16.0) of 2021-07-09 Package: Org mode version 9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)
columns view, org-lint, and native compilation
Hello all, TL;DR: org-lint fails, maybe due to native compilation Longer version: columns view (=org-columns=) doesn't work properly for me. If point is in some hierarchy where a higher level heading has a COLUMNS property, that higher level heading is highlighted and columns shown for it but none of the subheadings has its columns shown. In starting to debug this, I decided to make sure the structure of my file was okay so I invoked =org-lint= which then fails with back trace: Debugger entered--Lisp error: (search-failed "^[ \11]*#\\+[A-Za-z]+: + *$") #((fixed-width [...]) "") #f(compiled-function (datum) #)((fixed-width [...])) #f(compiled-function (--data) #)((fixed-width [...])) [...] org-element-map( [...] ) org-lint--collect-duplicates([...] ) org-lint-duplicate-name([...]) #f(compiled-function (c) #)(#s(org-lint-checker :name duplicate-name :description "Report duplicate NAME values" :categories (babel link) :trust high)) cl-mapcan(#f(compiled-function (c) #) [...]) org-lint--generate-reports([...]) org-lint--refresh-reports() org-lint--display-reports([...]) org-lint(nil) with a lot of text elided. Before I post something to bugs @ Emacs, has anybody else had problems with (a) org-columns and (b) org-lint, with or without native compilation? Thank you, eric -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-607-g185706 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: TMIO July Post: Introducing Citations
Does anyone know when this might land in Emacs’ master branch? R+ Timothy writes: Hi Everyone, Just letting you know that on my blog TMIO (This Month In Org) I've just published the July post. I've decided to focus entirely on citations this time :) Should this be of interest, here it is: https://blog.tecosaur.com/tmio/2021-07-31-citations.html Enjoy! -- Timothy -- Logic is a science of the necessary laws of thought, without which no employment of the understanding and the reason takes place. -- Immanuel Kant, 1785 Rudolf Adamkovič Studenohorská 25 84103 Bratislava Slovakia [he/him]
Re: TMIO July Post: Introducing Citations
> Timothy writes: > Hi Colin, >> Nice work. For me, however, I’m still at a loss, although I >> confess I’ve not kept up to-date with the org citation >> developments. >> >> 1. I don’t understand the relation between the new cite syntax >> and the old org-mode . Perhaps there isn’t one. >> >> 2. How is an `org-link-abbrev-alist' related to a global and/or >> local #+bibliography:? Even if I remove reference to my >> `org-link-abbrev-alist' the org-export (to pdf) still does not >> find a different local bibliography file. (I have >> org-cite-global-bibliography set to nil.) > I think the confusion you have lies in the similarity between the > link syntax and cite syntax — the new `[cite:@key]' citations are > *not* links. Hopefully that makes them a this a bit clearer :) Ah! Now that's helpful - thanks.
Re: TMIO July Post: Introducing Citations
Hi Colin, > Nice work. For me, however, I’m still at a loss, although I confess I’ve > not kept up to-date with the org citation developments. > > 1. I don’t understand the relation between the new cite syntax and the old > org-mode . Perhaps there isn’t one. > > 2. How is an `org-link-abbrev-alist' related to a global and/or local > #+bibliography:? Even if I remove reference to my `org-link-abbrev-alist' > the org-export (to pdf) still does not find a different local bibliography > file. (I have org-cite-global-bibliography set to nil.) I think the confusion you have lies in the similarity between the link syntax and cite syntax — the new `[cite:@key]' citations are *not* links. Hopefully that makes them a this a bit clearer :) All the best, Timothy
Re: TMIO July Post: Introducing Citations
Hello Timothy, > Timothy writes: > Hi Everyone, Just letting you know that on my blog TMIO (This > Month In Org) I've just published the July post. I've decided to > focus entirely on citations this time :) > Should this be of interest, here it is: > https://blog.tecosaur.com/tmio/2021-07-31-citations.html Nice work. For me, however, I'm still at a loss, although I confess I've not kept up to-date with the org citation developments. 1. I don't understand the relation between the new cite syntax and the old org-mode [[ bib:key ]]. Perhaps there isn't one. 2. How is an =org-link-abbrev-alist= related to a global and/or local #+bibliography:? Even if I remove reference to my =org-link-abbrev-alist= the org-export (to pdf) still does not find a different local bibliography file. (I have org-cite-global-bibliography set to nil.) I think I need to read the manual! Anyway, thanks to everyone for this new org citation. Best wishes, Colin.
Re: TMIO July Post: Introducing Citations
Hi Timothy, Timothy writes: > Hi Everyone, > > Just letting you know that on my blog TMIO (This Month In Org) I've just > published the July post. I've decided to focus entirely on citations > this time :) > > Should this be of interest, here it is: > https://blog.tecosaur.com/tmio/2021-07-31-citations.html Thank you very much for this comprehensive and very useful post: the best way to start my summer vacation! :-) And many thanks to those who have developed this interesting and promising new Org feature. Best regards, Juan Manuel
Re: TMIO July Post: Introducing Citations
On Mon, Aug 02, 2021 at 04:29:09AM +0800, Timothy wrote: > Hi Everyone, > > Just letting you know that on my blog TMIO (This Month In Org) I've just > published the July post. I've decided to focus entirely on citations > this time :) > > Should this be of interest, here it is: > https://blog.tecosaur.com/tmio/2021-07-31-citations.html Wow. Thanks! (Note that I'm not the target audience of this feature, but I'm nevertheless enjoying thoroughly your blog post!) Cheers - t signature.asc Description: Digital signature
