Re: The fate of ob-asymptote.el

2022-07-27 Thread Jarmo Hurri


Hello again.

Ihor Radchenko  writes:

> Jarmo Hurri  writes:
>> As a result, changes in Org are much more likely to affect
>> ob-asymptote.el than changes in Asymptote. I think basic software
>> development rules of thumb suggest that ob-asymptote.el should then
>> be bundled with Org.
>
> From my point of view ob-asymptote.el is as bare bones as babel
> library can be. It does not use any fancy Org babel features like
> sessions, error display of converting the output to various :results
> output options.
>
> In contrast, it does a lot of work trying to convert Elisp types to
> Asymptote in `org-babel-asymptote-var-to-asymptote`.

Fair point. Then again, the involved datatypes of Asymptote are,
practically, immutable.

I can not resist pointing out that we are having this discussion because
of changes in Org, not because of changes in Asymptote. I consider Org
much more volatile than Asymptote.

But I might be digressing. A bit of a summary:

- I embrace a (any) maintained feature which extends the applicability
  of Org without compromising "the core." I have had great moments
  noticing that Org already supports something new I need.

- Asymptote is brilliant. :-) I hope I can provide connectivity to Org
  for current and future users. When I shrivel away, this support might
  get buried next to me.

- Org contrib basically advertises itself as unmaintained. While that
  may change, and there is in fact a request to help maintain the
  add-ons on the github page, I am pessimistic. I would not install it,
  so I doubt others would either.

- I see Org as the logical place for ob-asymptote.el. If this is
  rejected, I may try inclusion into Asymptote if it is not an uphill
  battle.

> From my point of view, any kind of new functionality in
> ob-asymptote.el requires a deep knowledge about the Asymptote
> programming - the knowledge most of the Org devs lack. At the same
> time, changes in Org babel core functionality are unlikely to cause
> any issues in ob-asymptote - we try our best to keep backwards
> compatibility with third-party babel packages anyway.

Does this suggest that, from the point of view of Org, the risk of
supporting ob-asymptote.el is minimal?

All the best,

Jarmo




Re: Bug: Appointments duration and effort sums in agenda column view [9.3.7 (release_9.3.7-700-ga1e5be @ ~/.emacs.d/straight/build/org/)]

2022-07-27 Thread Mamoru Miura
Thank you for your helpful information!
I'll try it.

Best,
Mamoru

2022年7月27日(水) 13:05 Ihor Radchenko :
>
> Mamoru Miura  writes:
>
> >>But I am not even sure if this calculation is always same in different 
> >>agenda types...
> >
> > Where can I get the specification of agenda types? I'm interested in
> > the refactoring (but cannot work on it immediately...)
>
> 1. 11.2 The Agenda Dispatcher section of the manual
> 2. org-agenda-custom-commands docstring
> 3. org-agenda function inside org-agenda.el
>Look for the lines
>(pcase type
> (`agenda
>
> Hope it helps.
>
> Best,
> Ihor
>
> P.S. Take your time if you need some and feel free to ask questions if
>  you have any. We are not in hurry here. It is unlikely that anyone
>  else will make significant changes in the agenda code any time
>  soon.



Re: [PATCH] * lisp/org.el (org-store-log-note): Do not indent empty lines

2022-07-27 Thread Tor Kringeland
Ihor Radchenko  writes:

> See the attached patch.

Thanks!  This works as expected now.


Re: [BUG] inserting notes at end

2022-07-27 Thread Tor Kringeland
Ihor Radchenko  writes:

> I get note after empty lines below the headline in both the cases.
> This behavior is intentional according to org-log-beginning.

I see.  Maybe this could be noted in the docstring for org-add-note?  If
org-log-into-drawer is non-nil, then the behavior is different (the
drawer is always placed at the first newline below the heading).


Re: Something has happened such that I can't export to latex

2022-07-27 Thread Fraga, Eric
> Despite git pulling, etc, and restarting emacs, the problem still
> remains.
>
> This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
> /home/boudiccas/git/org-mode/lisp/)'

Sharon,

this looks like an old version (see my signature for a more recent version 
number).  Maybe you have a mixed installation?

-- 
: Eric S Fraga, with org release_9.5.4-648-gdf1814 in Emacs 29.0.50


Re: Something has happened such that I can't export to latex

2022-07-27 Thread Ihor Radchenko
Sharon Kimble  writes:

> Despite git pulling, etc, and restarting emacs, the problem still
> remains.
>
> This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
> /home/boudiccas/git/org-mode/lisp/)'
>
> Any ideas please?

Org 9.5.2 is a relatively old Org version. However, the error you are
getting was introduced in development version of Org (9.5.4+).
I suspect that you are loading some part of Org distribution from other
place. Not the Git folder you fetched.

Please make sure that you set the load-path for Org correctly early in
your config before you load Org or any package depending on Org.

Best,
Ihor



Re: Something has happened such that I can't export to latex

2022-07-27 Thread Sharon Kimble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Ihor Radchenko  writes:

> Sharon Kimble  writes:
>
>> Despite git pulling, etc, and restarting emacs, the problem still
>> remains.
>>
>> This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
>> /home/boudiccas/git/org-mode/lisp/)'
>>
>> Any ideas please?
>
> Org 9.5.2 is a relatively old Org version. However, the error you are
> getting was introduced in development version of Org (9.5.4+).
> I suspect that you are loading some part of Org distribution from other
> place. Not the Git folder you fetched.
>
> Please make sure that you set the load-path for Org correctly early in
> your config before you load Org or any package depending on Org.
>
> Best,
> Ihor

Thanks Ihor.

I eventually tracked down that I was loading org-mode from 
'/usr/local/share/emacs/29.0.50/lisp/org/'.

So I've done a 'make clean', and then configured and built emacs to run from 
bootstrap, and now my org-version shows as 'Org mode version 9.5.2 
(release_9.5.2-25-gaf6f12 @ /home/boudiccas/git/org-mode/lisp/)'.

However, if I build org-mode from git it shows as 'org-loaddefs: 9.5.4 
(release_9.5.4-682-g5be0c7).

So I've rebooted and now emacs is showing my org-version as still 'Org mode 
version 9.5.2 (release_9.5.2-25-gaf6f12 @ /home/boudiccas/git/org-mode/lisp/)'.

So I've looked at my config file, and the first time that org is mentioned is -
=
** installation
#+BEGIN_SRC emacs-lisp :tangle "~/.emacs.d/init.el" :exports code :results 
silent
;;; init.el --- sharon's config -*- eval: (read-only-mode 1) -*-
(require 'package)
(setq package-enable-at-startup nil)
(package-initialize)

(require 'ob-tangle)
(org-babel-load-file "~/.emacs.d/config22.org")
#+END_SRC
=
and the first time that org-mode is mentioned is - 
=
** set pathways

#+begin_src emacs-lisp
;;(setq load-path (cons "~/.emacs.d/lisp" load-path))
;; This sets up the load path so that we can override it
(package-initialize nil)
;; Override the packages with the git version of Org and other packages
;;(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-mode/"))
(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name 
"/home/boudiccas/git/org-contrib/lisp"))
;; Load the rest of the packages
(add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/lisp"))
;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/personal-elisp")
;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/test")
(add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/elpa"))
;; (add-to-list 'load-path "/home/boudiccas/git")
(setq custom-file "/home/boudiccas/.emacs.d/lisp/custom.el")

(load custom-file)
#+end_src
=

So how can I load the correct org-mode please?

Thanks
Sharon.
- -- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 11, fluxbox 1.3.7, emacs 29.0.50, org 9.5.2
-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLhV6kdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1se5g//bhQw5DnHJs4QxJtU
dnIXs9A33Q8561XvkUd9rmUf1fRhfitj+dIX9m7lYCr5CoeFzzBDHd/N+Me/nkAo
FbGGjVTEeQ1ypqoHe9w4w4U9Dv4vKKUVbmGFpA4svdrKnDgDXlAWckvNf7okjJin
qjbq7Y0gysrfW/hgtvWIq0AVdCoG9HzRXP1GV8aysRwqMhBCyGefNpj5noRAd6z/
0q4poqDMxozLZJvgkN20tbsrg/XVuHvEKkcyyMEyJNmyFUviY3iiUZ0X99Zp/S2F
MOUs/+h4RjqA3CLE6+RX2UUzYydD+ifosDWgO6uhWaHAqBxmcuK/Bo/Hlu4apVrC
s6lrNde7T3ub+s7Xxd8Goq+ARiuwtGU5df7Sb/8k+4PjU1mfUr61ySayGvHpaRVm
GLNURlG2RbNUijd0he7zXnXANcymHCKLkh4VXMOKETtLqP2vG7p2IKKX2iv9pztA
VomZscAL+stmEKSt6zr0jg3f1rCdkltG5VYKG0ZwJSdhwEuBjugOgYBXEKe6QXqy
GEi+FediBlbMiOAbOMvuLvWAdH16fYLegKoVLCbClhchRdeUztkCyAA2TeEZsaX7
sgVAb4ckFYST0lLBTLcl3i2x1rKTT4r0quf8pwMryeI+/UIhuHsvA4wpH9KEbD6X
+d/TwvxzbUt7pGTFjCwi7zfCW80=
=VvU8
-END PGP SIGNATURE-



Re: Something has happened such that I can't export to latex

2022-07-27 Thread Fraga, Eric
On Wednesday, 27 Jul 2022 at 16:20, Sharon Kimble wrote:
> So I've looked at my config file, and the first time that org is mentioned is 
> -

So you use org-babel-load-file *before* you set the load-path.  Move the
two lines that set the load path for org to before you use
org-babel-load-path.  In my own init files, setting the path to org is
the first thing I do.

-- 
: Eric S Fraga, with org release_9.5.4-648-gdf1814 in Emacs 29.0.50


Re: [PATCH] org-test: Run all ol tests on make test

2022-07-27 Thread Max Nikulin

On 27/07/2022 10:49, Ihor Radchenko wrote:


You missed the

(org-test-selector
 (if org-test-selector org-test-selector "\\(org\\|ob\\)"))


I have notices that cases in test-oc.el are named test-org-cite/... So I 
am considering renaming tests in test-ol.el in the same way from 
test-ol/... to test-org-link/... instead of modifying selectors. I have 
not noticed with approach to naming is recommended.





count TODO in columnview

2022-07-27 Thread Uwe Brauer


Hi 

I can count checkboxes but not TODOS in columnview it seems.

Here is an example
#+begin_src 

* Everything
  :PROPERTIES:
  :COLUMNS:   %TODO %ITEM  %Nr %Comp1 %Comp2  
  :COMP1:[3/4]
  :COMP2:[3/4]
  :TODO:  [ ] 
  :END:


** DONE Books
   :PROPERTIES:
   :Nr:   1
   :Comp1: [X]
   :Comp2: [X]
   :END:

** TODO Car
   :PROPERTIES:
   :Nr:   2
   :Comp1: [X]
   :Comp2: [X]
   :END:

** DONE Food
   :PROPERTIES:
   :Nr:   3
   :Comp1:[ ]
   :Comp2:[X]
   :END:

** WAIT Dr. Computer
   :PROPERTIES:
   :Nr:   4
   :Comp1:[X]
   :Comp2: [ ]
   :END:

#+BEGIN: columnview :maxlevel 2 :skip-empty-rows t :hlines 1 :indent nil  
:format "%5TODO(Status) %5Nr(Nr) %5Comp1(Comp1){X/} %5Comp2(Comp2){X/}"
| Status | Nr | Comp1 | Comp2 |
|++---+---|
||| [3/4] | [3/4] |
| DONE   |  1 | [X]   | [X]   |
| TODO   |  2 | [X]   | [X]   |
| DONE   |  3 | [ ]   | [X]   |
| WAIT   |  4 | [X]   | [ ]   |
#+END:


#+end_src

Any suggestion?

Regards 

Uwe Brauer 
-- 
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine. 




Re: [PATCH] lisp/ob-plantuml.el: Insert results in buffer

2022-07-27 Thread Joseph Turner
Ihor Radchenko  writes:
> You can examine :result-params property inside params plist. If that
> property does not explicitly mention different results Type (see 16.6
> Results of Evaluation), ob-plantuml may set the type to "file" with
> plist-put.

Perhaps I'm confused, but I think org-babel-default-header-args:plantuml
is actually an alist, right?

I tried removing the (:results . "file") from
org-babel-default-header-args:plantuml, and then overwriting the params
argument inside the let* block like so:

```
  (let* ((do-export (cdr (assq :file params)))
 (params (if do-export
 (add-to-list 'params '(:results . "file")))
 (out-file ...
```

Logging the params variable after the let* block reveals that :results
is set to "file", but I still get "Code block produced no output" when
I try to evaluate the plantuml org src block.

Thoughts?

Joseph



Re: Something has happened such that I can't export to latex

2022-07-27 Thread Tim Cross


Note that identifying when org is loaded is not always
straight-forward. There are lots of packages which include org support
which can result in org being loaded as a side effect when you load
them. This is especially true of non-core packages which will use
explicit require statements rather than relying on autoloads etc.

For this reason, I always ensure that anything relating to org source
paths etc is loaded as early as possible. 

Sharon Kimble  writes:

>
> So I've looked at my config file, and the first time that org is mentioned is 
> -
> =
> ** installation
> #+BEGIN_SRC emacs-lisp :tangle "~/.emacs.d/init.el" :exports code :results 
> silent
> ;;; init.el --- sharon's config -*- eval: (read-only-mode 1) -*-
> (require 'package)
> (setq package-enable-at-startup nil)
> (package-initialize)
>
> (require 'ob-tangle)
> (org-babel-load-file "~/.emacs.d/config22.org")
^
This is when org is being loaded as ob-tangle is part of org. This will
mean the built-in/bundled version of org is loaded.

> #+END_SRC
> =
> and the first time that org-mode is mentioned is - 
> =
> ** set pathways
>
> #+begin_src emacs-lisp
> ;;(setq load-path (cons "~/.emacs.d/lisp" load-path))
> ;; This sets up the load path so that we can override it
> (package-initialize nil)
> ;; Override the packages with the git version of Org and other packages
> ;;(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-mode/"))
> (add-to-list 'load-path (expand-file-name 
> "/home/boudiccas/git/org-mode/lisp"))
> (add-to-list 'load-path (expand-file-name 
> "/home/boudiccas/git/org-contrib/lisp"))
^^
This isn't going to work as you hope. You have already loaded org mode
when you called (require 'ob-tangle),

so what this is doing is adding an additional path to a latter version
of org which is going to result in a 'mixed' version. This will cause
lots of issues.

You either  need to move the above lines *above* the require 'ob-tangle
or move the earlier lines to after these ones. I think earlier is better
when it comes to org as there are many packages which include org
support and which will load org as a hidden side effect. 

> ;; Load the rest of the packages
> (add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/lisp"))
> ;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/personal-elisp")
> ;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/test")
> (add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/elpa"))
> ;; (add-to-list 'load-path "/home/boudiccas/git")
> (setq custom-file "/home/boudiccas/.emacs.d/lisp/custom.el")
>
> (load custom-file)
> #+end_src
> =
>
> So how can I load the correct org-mode please?
>

I note your appear to be running both the development version of Emacs
as well as the git version of org mode. While this will give you the
most recent versions of both, it will also mean your working with the
most unstable versions of both. If you rely on org for your daily
workflow, I would recommend

1. Just running with the version of org bundled with Emacs. Being the
development version, it will stay reasonably up-to-date as you really
need to update and re-build Emacs every week or so anyway.

or

2. Just use the org from ELPA and org-contrib from non-GNU ELPA. These
are usually the most stable versions with bug fixes applied. This would
be my recommendation. 

I think few people actually need to run from the head of the git
repository. Your messages indicated that having a broken org
installation was a significant issue for you and getting the issues
resolved are quite urgent. Using the ELPA/non-GNU packages will ensure
you get important bug fixes while keeping your org version current with
the most recent stable version and is probably the best choice for
anyone who needs a reliable org for production/daily use. 




[SOLVED] (was: count TODO in columnview)

2022-07-27 Thread Uwe Brauer
>>> "UB" == Uwe Brauer  writes:

> Hi 

> I can count checkboxes but not TODOS in columnview it seems.

> Here is an example

> #+begin_src 

According to https://orgmode.org/manual/Breaking-Down-Tasks.html

a simple [/] is enough, and indeed it is:

* Everything [/]

Which indeed it is 

After adding this and running org-todo I obtain 


#+begin_src 

* Everything [3/4]
  :PROPERTIES:
  :COLUMNS:   %TODO %ITEM  %Nr %Comp1 %Comp2  
  :COMP1:[3/4]
  :COMP2:[3/4]
  :TODO:  [ ] 
  :END:

** DONE Books
   :PROPERTIES:
   :Nr:   1
   :Comp1: [X]
   :Comp2: [X]
   :END:

** DONE Car
   :PROPERTIES:
   :Nr:   2
   :Comp1: [X]
   :Comp2: [X]
   :END:

** DONE Food
   :PROPERTIES:
   :Nr:   3
   :Comp1:[ ]
   :Comp2:[X]
   :END:

** WAIT Dr. Computer
   :PROPERTIES:
   :Nr:   4
   :Comp1:[X]
   :Comp2: [ ]
   :END:

#+BEGIN: columnview :maxlevel 2 :skip-empty-rows t :hlines 1 :indent nil  
:format "%5TODO(Status) %5Nr(Nr) %5Comp1(Comp1){X/} %5Comp2(Comp2){X/}"
| Status | Nr | Comp1 | Comp2 |
|++---+---|
||| [3/4] | [3/4] |
| DONE   |  1 | [X]   | [X]   |
| TODO   |  2 | [X]   | [X]   |
| DONE   |  3 | [ ]   | [X]   |
| WAIT   |  4 | [X]   | [ ]   |
#+END:



#+end_src


smime.p7s
Description: S/MIME cryptographic signature