Re: [PATCH 0/1] Add option to delay fontification of source blocks
Leo Okawa Ericson writes: > Fontification of long code blocks can be very slow. The patch, which should be > in another other email, mitigates this by > adding an option to delay the fontification after the user has become idle by > using idle timers. This seems to be faster from my limited testing, but I'm > not > sure if something will go horribly wrong because of the timers. Thanks for the patch. My initial reaction is that I'm not sure about adding an idle timer for a particular aspect of fontification. If we do go this route, I think the case needs to be made why this spot is special, and why we don't expect or would reject follow-up patches for this and that other area. Have you explored whether jit-lock (e.g., jit-lock-defer-time) helps for your use case?
Re: [PATCH 1/2] org-manual.org: Fix typo in org-protocol capture example
Maxim Nikulin writes: > * doc/org-manual.org: Use "&" as parameter separator in query part > of example for org-protocol capture URI. Thank you. Pushed this and the next patch (4de2fff87), with a minor formatting tweak to the second commit message.
Re: Shutting down Org ELPA: No new release of Org on Org ELPA after Org 9.5
ok so org releases will be [just guesses here] - emacs core - there is a gnu elpa - there is a nongnu elpa - there is an org git correct? On 3/28/21, Bastien wrote: > Hi Tim, > > Tim Cross writes: > >> To clarify, does this mean org 9.6 will be the first version only >> released via GNU elpa (i.e. bug fixes for 9.5 will still be released >> via Org elpa e.g. 9.5.1)? > > No, it means 9.5 will be the last version released on Org ELPA, > further bugfix releases will only be distributed through GNU ELPA. > > 9.5.1 won't be on Org ELPA, which will not get new releases after 9.5. > > I hope this is clearer now, thanks for asking, > > -- > Bastien > > -- The Kafka Pandemic Please learn what misopathy is. https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
Re: Shutting down Org ELPA: No new release of Org on Org ELPA after Org 9.5
Hi Tim, Tim Cross writes: > To clarify, does this mean org 9.6 will be the first version only > released via GNU elpa (i.e. bug fixes for 9.5 will still be released > via Org elpa e.g. 9.5.1)? No, it means 9.5 will be the last version released on Org ELPA, further bugfix releases will only be distributed through GNU ELPA. 9.5.1 won't be on Org ELPA, which will not get new releases after 9.5. I hope this is clearer now, thanks for asking, -- Bastien
Re: Org 9.4.5
Hi Detlef, Detlef Steuer writes: > Would it be possible to have the changelog in the mail announcements? > Either as an attachment or just copied verbatim? Thanks for the suggestion. I'm attaching the output of: ~$ git log --pretty=oneline --abbrev-commit release_9.4.4..release_9.4.5 > I really think that would improve the chances the changelog is read :-), > at least for me :-) Sure, but remember bugfixes releases are just about bug fixes, so casual users are not required to read these changelogs. All best, -- Bastien 287af207f lisp/org.el: Bump version header to 9.4.5 36622362d org.el (org-do-latex-and-related): Fix duplicate 'latex faces 478929ae6 ox-html: Fix org-html-format-drawer-function's docstring 4f98c86b3 manual: Grammar fix d15639944 Update example :publishing-function names in manual 5450d6420 ob-export: Give more informative error on unknown call reference 5db61eb0f org.el: Avoid xdg-open silent failure dbc84311c ob-smiles.el: Fix reference to free variable 1738b455b ob-smiles.el: Update org babel API e07cb2ad3 manual: Fix org-latex-listings reference in footnote 7470ee93a test-org-clock: Avoid daylight saving time failure b712b9618 manual: Add publishing-function to publishing example 8244e7ba8 manual: Fix org-html-publish-to-html reference 3a522ad53 agenda: Restore org-agenda-goto-date's date argument 4ab2a4be5 org-adapt-indentation: Tweak headline-data addition ee4ffa567 org-clock: fix runtime error in org-clock-in 75ccb9719 Allow tags containing capital letters in org-agenda-filter 61336f80d mk/targets.mk: Add version fallback for tag-less repos 862048d4c ob-sql.el: Respect the value of sql-postgres-program e87959615 footnote: Silence byte-compiler under 'make single' 2ed1c20ff Remove Emacs 21 compat code for bookmark-after-jump-hook 3e64d3475 capture: Fix handling of time range for :time-prompt 0abd4a44c ox-latex.el: Use [Objective]Caml dialect a50a42cea Use lexical-binding cookie in some trivial files 13e98e2a1 ox-latex.el: fix interpretation of org-latex-pdf-process b99beaad1 org-macs: Add basic tests for org-matcher-time aeb9f036f org-macs: Allow specifying relative time in hours 9e8215f4a ob-C.el: Fix missing C, C++ declaration 1806abdc3 org-footnote: Fix inserting new footnote mangling drawers d02c0218e testing/lisp/test-org-archive.el: Fix test 33de2bd8e org-compat: Take in obsolete org-copy 248dfcd71 Backport commit 5ada3eece from Emacs 332da69b3 element: Fix table.el parsing... again! 273391c97 duration: Avoid recursive load error 99eafe378 Update copyright year to 2021 bd1c3187c .dir-locals.el: Set indent-tabs-mode to nil in Elisp sources 97f1d8e34 element: Improve table.el tables dectection 118da7d28 element: Fix table.el tables parsing
Re: [PATCH] org-protocol: Make org protocol defaults work on windows
On 20/11/2020 23:26, Robert wrote: > Attached a little patch to make the default org-protocol > handlers work on windows. Unsure, but the issue might be addressed by the following change: https://code.orgmode.org/bzg/org-mode/commit/928e67df org-protocol: Allow slashes after sub-protocol I am curious if alternative approach could help. Have you tried one or three slashes after "org-protocol:"? E.g. org-protocol:/capture?template=... or org-protocol:///capture?template=... instead of org-protocol://capture?template=... I suspect that with double slash subprotocol is considered as a name of some host so "/" as path before query part is added. With other number of slashes subprotocol does not look like a host name similar to file:/// scheme. See https://orgmode.org/list/s3flvl$a48$1...@ciao.gmane.io/
[PATCH 2/2] Add quotes to emacsclient arguments in examples
* doc/org-manual.org, lisp/org-protocol.el: Quote emacsclient arguments
in examples to prevent interpreting of ampersands as intent
to run processes in background by bash and similar shells.
Single quotes may cause a problem with cmd.exe, so use
double quotes despite they are a bit less safe in bash and Co.
---
doc/org-manual.org | 6 +++---
lisp/org-protocol.el | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index e2fbdceb4..efe956877 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19588,7 +19588,7 @@ passed to Emacs through the =emacsclient= command, so
you also need to
ensure an Emacs server is running. More precisely, when the
application calls
-: emacsclient org-protocol://PROTOCOL?key1=val1=val2
+: emacsclient "org-protocol://PROTOCOL?key1=val1=val2"
#+texinfo: @noindent
Emacs calls the handler associated to {{{var(PROTOCOL)}}} with
@@ -19611,7 +19611,7 @@ Using the ~store-link~ handler, you can copy links, to
that they can
be inserted using {{{kbd(M-x org-insert-link)}}} or yanking. More
precisely, the command
-: emacsclient org-protocol://store-link?url=URL=TITLE
+: emacsclient "org-protocol://store-link?url=URL=TITLE"
#+texinfo: @noindent
stores the following link:
@@ -19640,7 +19640,7 @@
javascript:location.href='org-protocol://store-link?url='+
Activating the "capture" handler pops up a =Capture= buffer in Emacs,
using acapture template.
-: emacsclient org-protocol://capture?template=X=URL=TITLE=BODY
+: emacsclient "org-protocol://capture?template=X=URL=TITLE=BODY"
To use this feature, add a bookmark with an arbitrary name, e.g.,
=Org: capture=, and enter this as =Location=:
diff --git a/lisp/org-protocol.el b/lisp/org-protocol.el
index 6f8cf00e9..731f51e19 100644
--- a/lisp/org-protocol.el
+++ b/lisp/org-protocol.el
@@ -49,7 +49,7 @@
;; 4.) Try this from the command line (adjust the URL as needed):
;;
;; $ emacsclient \
-;;
org-protocol://store-link?url=http:%2F%2Flocalhost%2Findex.html=The%20title
+;;
"org-protocol://store-link?url=http:%2F%2Flocalhost%2Findex.html=The%20title"
;;
;; 5.) Optionally add custom sub-protocols and handlers:
;;
--
2.25.1
[PATCH 1/2] org-manual.org: Fix typo in org-protocol capture example
* doc/org-manual.org: Use "&" as parameter separator in query part of example for org-protocol capture URI. --- doc/org-manual.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index 258576b24..e2fbdceb4 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -19640,7 +19640,7 @@ javascript:location.href='org-protocol://store-link?url='+ Activating the "capture" handler pops up a =Capture= buffer in Emacs, using acapture template. -: emacsclient org-protocol://capture?template=X?url=URL?title=TITLE?body=BODY +: emacsclient org-protocol://capture?template=X=URL=TITLE=BODY To use this feature, add a bookmark with an arbitrary name, e.g., =Org: capture=, and enter this as =Location=: -- 2.25.1
Re: Exam LaTeX class
Dear Diego,
Gracias!
I slightly modified your solution.
I added the #+INCLUDE line to the end of #+LATEX_HEADER, because then it
will overwrite any previous \printanswers and \noprintanswers defined in
the HEADER.
#+TITLE:...
...
#+LATEX_HEADER: \usepackage{hyperref}
#+INCLUDE: ./latex-exam-printanswers-switch.org
I used the file name latex-exam-printanswers-switch.org, instead of
printanswers.org, because it gives a better indication of what it does.
I used your function as it was, except that I changed the function name
and updated the switch org file.
(defun org-latex-export-to-pdf-exam ()
(interactive)
(write-region "#+LATEX_HEADER: \\printanswers" nil
"latex-exam-printanswers-switch.org")
(org-latex-export-to-pdf)
(rename-file (org-export-output-file-name ".pdf")
(org-export-output-file-name "-with_answers.pdf"))
(write-region "" nil "latex-exam-printanswers-switch.org")
(org-latex-export-to-pdf)
)
It works very fine!
Have a nice Easter!
Yours sincerely,
Xianwen
On 2021-03-24 13:16, Diego Zamboni wrote:
Hi Xianwen,
I think the easiest way to conditionally include text in the preamble
of the document would be by including a file which can be empty
sometimes, and contain the appropriate text when needed. For example,
you could have something like this in your Org file:
#+include: ./printanswers.org [1]
#+TITLE: Test
...
Then the following function will automatically export the file twice,
one with the \printanswers command inserted then rename the resulting
file, and export again without:
(defun org-latex-export-exams ()
(interactive)
(write-region "#+latex_header: \\printanswers" nil "printanswers.org
[1]")
(org-latex-export-to-pdf)
(rename-file (org-export-output-file-name ".pdf")
(org-export-output-file-name "-with_answers.pdf"))
(write-region "" nil "printanswers.org [1]")
(org-latex-export-to-pdf))
You can then run M-x org-latex-export-exams to generate both files.
Hope this helps,
--Diego
On Wed, Mar 24, 2021 at 11:21 AM Xianwen Chen (陈贤文)
wrote:
Dear Christine (and CC list),
Thank you!
On 2021-03-19 10:13, Christine Köhn wrote:
Here is one way to do the latex part. You could pass a jobname to
latex.
I have this
\IfEndWith*{\jobname}{withsolution}{%
\usepackage{todonotes}
\printanswers
}{\usepackage[disable]{todonotes}}
in a myexam.sty file to switch between modes (with or without solutions
and todo notes) and use it in the latex file with
\usepackage{myexam}
You could add your own latex class to org-latex-classes and add this
line there.
The jobname has to be passed to latex with something like -jobname
withsolution if you want it to be with solutions. I use a Makefile for
this purpose which calls latexmk
latexmk -pdf -pdflatex="pdflatex --interaction=errorstopmode" -use-make
and adds -jobname=$(basename $@) if asked to create a pdf ending with
withsolution.pdf. I can send you the Makefile if you're interested.
That's very interesting way to solve the problem using LaTeX. Thank you
for sharing this. At the moment I'm leaning more towards solving it
using emacs lisp.
To use the jobname from within orgmode, you'll have to change
org-latex-pdf-process to use the jobname if needed. I think one way to
achieve this is to add a new export backend which is derived from latex
(see org-export-define-derived-backend) and which sets
org-latex-pdf-process accordingly (and resets it afterwards).
Thank you again. I'm thinking of a function like following. I'm using
comments to express the programming detail that I don't know how to do
yet.
(deffun org-latex-export-to-pdf-exam ()
(interactive)
# do some emacs lisp to add \printanswers to the end of org document
header, i.e., adding a line of #+LATEX_HEADER: \printanswers
(org-latex-export-to-pdf)
# do some emacs lips to move the foo.pdf to foo-with_solutions.pdf
# do some emacs lisp to add \noprintanswers to the end of org document
header, i.e., removing the line of #+LATEX_HEADER: \printanswers and
adding a line of #+LATEX_HEADER: \noprintanswers
(org-latex-export-to-pdf)
# remove the line of #+LATEX_HEADER: \noprintanswers
)
I don't know enough emacs lisp to fill in the details here for now.
However, I think this would be a way to do it within emacs. So each
time I call org-latex-export-to-pdf-exam, it would export two PDF
files, one with solutions and one without.
What do you think?
Yours sincerely,
Xianwen
Links:
--
[1] http://printanswers.org
Re: Starting from 9.5, Org contrib will be distributed as a separate NonGNU ELPA package
> Bastien writes: >> Is it still the intention to put the files in a new >> org-contrib.git repo on code.orgmode.org? > Yes, org-contrib.git will live in one of these forges: > https://code.orgmode.org https://savannah.nongnu.org https://sr.ht Great! Thanks, Bastien. Best wishes,
Re: Starting from 9.5, Org contrib will be distributed as a separate NonGNU ELPA package
Hi Colin, Colin Baxter writes: >> Bastien writes: > > > Hi all, starting from Org 9.5, org-contrib will be distributed as > > a NonGNU ELPA package. You will find it here: > > https://elpa.nongnu.org/nongnu/ > > > See for https://orgmode.org/list/87wnzfy60h@bzg.fr/ for > > context. > > Is it still the intention to put the files in a new org-contrib.git repo > on code.orgmode.org? Yes, org-contrib.git will live in one of these forges: https://code.orgmode.org https://savannah.nongnu.org https://sr.ht > This would be useful for those of us who do not > use packages. Indeed! -- Bastien
Re: Starting from 9.5, Org contrib will be distributed as a separate NonGNU ELPA package
> Bastien writes: > Hi all, starting from Org 9.5, org-contrib will be distributed as > a NonGNU ELPA package. You will find it here: > https://elpa.nongnu.org/nongnu/ > See for https://orgmode.org/list/87wnzfy60h@bzg.fr/ for > context. Is it still the intention to put the files in a new org-contrib.git repo on code.orgmode.org? This would be useful for those of us who do not use packages. Best wishes,
Re: How to undo all items, including headings?
* Ihor Radchenko [2021-03-28 15:35]: > Jean Louis writes: > > > I would like to undo all TODO/DONE/PENDING tags and list items in a > > list of lists similar like this below. > > ... > > Does similar function exist already? > > org-checklist.el from contrib may be what you need. Thank you. I found some functions like: (org-todo 'none) and M-x org-update-checkbox-count For now I used those in macro and with one repeated key I have disabled many, then made a template out of the one heading with many checkbox counts. The package may be doing what I wish, but is not a repeated function really. Thanks, Jean
Re: How to undo all items, including headings?
Jean Louis writes: > I would like to undo all TODO/DONE/PENDING tags and list items in a > list of lists similar like this below. > ... > Does similar function exist already? org-checklist.el from contrib may be what you need. Best, Ihor
Re: Shutting down Org ELPA: No new release of Org on Org ELPA after Org 9.5
* Bastien [2021-03-28 09:58]: > Hi all, > > over the years, Org ELPA at https://orgmode.org/elpa/ has been useful > to make it possible to install Org and Org+Contrib as ELPA packages, > but maintaining a separate ELPA space just for Org is not necessary. Good decision, it lessens confusion on it. > Org 9.5 will be the last release to be distributed on Org ELPA. After > 9.5, we won't use Org ELPA for new releases. Past releases will still > be available, though maybe not indefinitely. Maybe previous versions you can also push to GNU ELPA, it is anyway full of various previous versions for other packages. It this is considered important. Jean
How to undo all items, including headings?
I would like to undo all TODO/DONE/PENDING tags and list items in a list of lists similar like this below. *** PENDING Administration and office [13/15] [86%] 1) [X] Office desk 2) [X] Pocket notebooks, for 2 months even 20-50 small pocket notebooks are required 3) [X] Boxes for documents Does similar function exist already? Jean
Re: Org 9.4.5
Detlef Steuer writes: > Would it be possible to have the changelog in the mail announcements? > Either as an attachment or just copied verbatim? FWIW, if you have the org-mode repo handy, you can hew out a GNU-style changelog with *breathes in* $ git log release_9.4.4..release_9.4.5 --format=format:'%as %an <%ae>%n%n%w(0,8,8)%s%n%n%b' | sed 's/^ *$//' See attached result. git shortlog release_9.4.4..release_9.4.5 works quite well too, depending on your taste (attached as well). 2021-03-28 Bastien lisp/org.el: Bump version header to 9.4.5 2021-03-19 Sébastien Miquel org.el (org-do-latex-and-related): Fix duplicate 'latex faces * lisp/org.el (org-do-latex-and-related): Do not add a 'org-latex-and-related face beyond the fontification limit. 2021-03-24 Kyle Meyer ox-html: Fix org-html-format-drawer-function's docstring * lisp/ox-html.el (org-html-format-drawer-function): Drop leftover text from when an example used to be included. adcebf38f (Fix errors reported by cus-test.el, 2013-11-14) dropped the example but left the leading part. Reported-by: Jean-Baptiste Mazon Ref: https://orgmode.org/list/0e5569e6-15a7-d4c4-0558-8b0ef96a5...@gmail.com 2021-03-24 Kyle Meyer manual: Grammar fix * doc/org-manual.org (Publishing action): Fix conjugation. 2021-03-22 Greg Minshall Update example :publishing-function names in manual * doc/org-manual.org (Publishing action): Fix references to org-latex-publish-to-pdf and org-org-publish-to-org. 2021-03-21 Kyle Meyer ob-export: Give more informative error on unknown call reference * lisp/ob-exp.el (org-babel-exp-process-buffer): Signal user-error with an informative message rather than letting org-babel-exp-do-export call fail due to an invalid INFO argument. * testing/lisp/test-ob-exp.el (ob-exp/unknown-call-reference): Add test. Reported-by: Greg Minshall Ref: https://orgmode.org/list/628738.1616259...@apollo2.minshall.org 2021-03-20 Maxim Nikulin org.el: Avoid xdg-open silent failure * lisp/org.el (org-open-file): Use 'pipe :connection-type instead of 'pty to prevent killing of background process on handler exit. (Bug#44824) Problem happens only in some desktop environments where configured through `org-file-apps' or mailcap handlers launches actual viewer (as defined in .desktop files and obtained from mimeapps.list) in background. E.g. xdg-open invokes "gio open" or kde-open5 for Gnome or KDE accordingly and these handlers launches e.g. eog or okular in background. As soon as main process exits, temporary terminal session created by `start-process-shell-command' is terminated. As a result background processes receive SIGHUP. Previously command were executed with no buffer, so the change does not affect "needsterminal" and "copiousoutput" mailcap features, they are not supported as earlier. If handler main process fails then show a message with exit reason. Output (including error messages) is ignored as before. Gtk application tends to report significant amount of failed asserts hardly informative for majority of users. TINYCHANGE 2021-03-19 Kyle Meyer ob-smiles.el: Fix reference to free variable * contrib/lisp/ob-smiles.el (molecule-jump): Format string with NAME argument rather than undefined variable `path'. 2021-03-16 Lein Matsumaru ob-smiles.el: Update org babel API * contrib/lisp/ob-smiles.el (org-link): Fix from org-add-link-type to org-link-set-parameters TINYCHANGE 2021-03-15 Kyle Meyer manual: Fix org-latex-listings reference in footnote * doc/org-manual.org (Footnotes): Refer to org-latex-listings instead of org-export-latex-listings. The last occurrence of org-export-latex-listings was deleted with the contrib/oldexp/ removal in Org 8. 2021-03-14 Kyle Meyer test-org-clock: Avoid daylight saving time failure * testing/lisp/test-org-clock.el (test-org-clock/clocktable/match): Shift times away from the beginning of the day to avoid unexpected time totals due to DST changes. test-org-clock/clocktable/match fails today in the US because at 2:00 clocks jumped to 3:00, and the total time check uses the range 2:00-4:00. 2021-03-02 Kyle Meyer manual: Add publishing-function to publishing example * doc/org-manual.org (Example: simple publishing configuration): Add :publishing-function to org-publish-project-alist. This appears to have been necessary since 0ccf650b4 (org-e-publish: Remove default value for publishing function, 2012-10-08).
How to have a repeating item within some hours?
Hi Orgers, I'd like to have a repeating time block on the agenda, say every Monday from 5:15 to 6:15. I tried this: ** <2021-03-29 Mon 05:15 +7d>--<2021-03-29 Mon 06:15 +7d> Time block but it didn't show on the agenda, and this: ** Time block SCHEDULED: <2021-03-29 Mon 05:15 +7d>--<2021-03-29 Mon 06:15 +7d> but it didn't show the end time. Any hints? -- Marcin Borkowski http://mbork.pl
Re: Org 9.4.5
Hi Bastien, thx for all the work, as usual! :-) Would it be possible to have the changelog in the mail announcements? Either as an attachment or just copied verbatim? I really think that would improve the chances the changelog is read :-), at least for me :-) All the best and thx again! Detlef Am Sun, 28 Mar 2021 08:59:14 +0200 schrieb Bastien : > Hi all, > > Org 9.4.5, a bugfix release, is out. > > Enjoy! >
Re: Shutting down Org ELPA: No new release of Org on Org ELPA after Org 9.5
Thanks Bastien. To clarify, does this mean org 9.6 will be the first version only released via GNU elpa (i.e. bug fixes for 9.5 will still be released via Org elpa e.g. 9.5.1)? Tim Bastien writes: > Hi all, > > over the years, Org ELPA at https://orgmode.org/elpa/ has been useful > to make it possible to install Org and Org+Contrib as ELPA packages, > but maintaining a separate ELPA space just for Org is not necessary. > > Org 9.5 will be the last release to be distributed on Org ELPA. After > 9.5, we won't use Org ELPA for new releases. Past releases will still > be available, though maybe not indefinitely. > > The Org package will continue to be available through GNU ELPA (from > https://elpa.gnu.org/packages/) and a new Org-Contrib package will be > available from https://elpa.nongnu.org/nongnu/. > > Only stable releases will be distributed through both GNU and NonGNU > ELPA repositories. For those who want to test the unstable version of > Org, please install Org from Git: > > ~$ git clone https://code.orgmode.org/bzg/org-mode.git > > See https://orgmode.org/manual/Installation.html#Installation > > If you used Org ELPA and are affected by this change, please tell us > if this change affects you. > > Thanks! -- Tim Cross
Org 9.4.5
Hi all, Org 9.4.5, a bugfix release, is out. Enjoy! -- Bastien
Shutting down Org ELPA: No new release of Org on Org ELPA after Org 9.5
Hi all, over the years, Org ELPA at https://orgmode.org/elpa/ has been useful to make it possible to install Org and Org+Contrib as ELPA packages, but maintaining a separate ELPA space just for Org is not necessary. Org 9.5 will be the last release to be distributed on Org ELPA. After 9.5, we won't use Org ELPA for new releases. Past releases will still be available, though maybe not indefinitely. The Org package will continue to be available through GNU ELPA (from https://elpa.gnu.org/packages/) and a new Org-Contrib package will be available from https://elpa.nongnu.org/nongnu/. Only stable releases will be distributed through both GNU and NonGNU ELPA repositories. For those who want to test the unstable version of Org, please install Org from Git: ~$ git clone https://code.orgmode.org/bzg/org-mode.git See https://orgmode.org/manual/Installation.html#Installation If you used Org ELPA and are affected by this change, please tell us if this change affects you. Thanks! -- Bastien
Starting from 9.5, Org contrib will be distributed as a separate NonGNU ELPA package
Hi all, starting from Org 9.5, org-contrib will be distributed as a NonGNU ELPA package. You will find it here: https://elpa.nongnu.org/nongnu/ See for https://orgmode.org/list/87wnzfy60h@bzg.fr/ for context. Thanks, -- Bastien
Re: Starting from 9.5, Org contrib will be distributed as a separate Org ELPA package
Hi all, Bastien writes: > Org 9.5 will ship without the packages in the contrib/ directory. Just FWIW, this is still the plan. > Emacs lisp files in contrib/ will be packaged as an Org ELPA package > that you can install independentely from there. The files will live > in a new org-contrib.git repo on code.orgmode.org. There is a change here - instead of being published as an Org ELPA package, org-contrib will be published as a NonGNU ELPA package. You will find it here: https://elpa.nongnu.org/nongnu/ > In the long run, every Emacs file in org-contrib.git need to find a > proper maintainer (who will decide where to maintain it) or to be > listed in the list of Emacs orphan packages. This is still the case: volunteers are welcome. Thanks, -- Bastien
