Org ELPA: does not include 9.5 as expected, archives appear largely identical?

2021-11-19 Thread Damian
https://www.orgmode.org/Changes.html indicates that the Org ELPA should 
include 9.5, but currently that does not appear to be the case: 
https://orgmode.org/elpa/ only has 9.4.6. Could 9.5 be included to match 
the documentation? Or is there something I am missing?


https://orgmode.org/elpa/ has archives from '20210726' to '20210920', 
but all of the files report the exact same size of 6461440. I examined 
'org-20210726.tar' and 'org-20210920.tar', and their org.el files both 
indicate version '9.4.6', and most files are identical with the 
exception of 'org-keys.el', 'org-pkg.el', 'org-version.el', and 
'orgcard.pdf' (only 'org-keys.el' has any functional changes). This 
seems suspicious, but I'm not familiar with org releases.


Thanks,

-Damian




[O] org-scheduled-time-hour-regexp doesn't capture split repeats used by habit

2019-06-26 Thread Damian
The ':scheduled*' value for org-agenda-entry-types uses 
org-scheduled-time-hour-regexp to match related entries. The current 
regexp doesn't match entries with split repeats like those used by 
habits- for example:   'SCHEDULED: <2019-06-25 Tue 20:30 .+1d/2d>'. 
Because those entries show up in the agenda with a timestamp I believe 
they should be caught by the regexp.


org.el:
 (defconst org-scheduled-time-hour-regexp
  (concat "\\<" org-scheduled-string
  " *<\\([^>]+[0-9]\\{1,2\\}:[0-9]\\{2\\}[0-9+:hdwmy 
\t.-]*\\)>")
  "Matches the SCHEDULED keyword together with a time-and-hour 
stamp.")


Fix?
   (defconst org-scheduled-time-hour-regexp
  (concat "\\<" org-scheduled-string
  " *<\\([^>]+[0-9]\\{1,2\\}:[0-9]\\{2\\}[0-9+:hdwmy 
\t./-]*\\)>")
  "Matches the SCHEDULED keyword together with a time-and-hour 
stamp.")


Thanks,
-Damian




Re: [O] Bug: missing `save-excursion' in `org-fast-tag-selection' [9.2.3 (9.2.3-9-g0803e2-elpa @ /home/il/.emacs.d/elpa/org-20190422/)]

2019-05-01 Thread Damian

Ingo Lohmar  writes:

> I tried to use `org-agenda-set-tags'.  The source buffer (where the
> change should be applied) is visible at the same time as the agenda is.
> Also, fast tag selection with a single key is enabled.
>
> Under these circumstances, the tag text is appended to the line (not
> even necessarily a heading!) where point is in the source buffer visible
> next to the agenda, instead of the correct heading that I acted upon.
>
> I tracked this done to a missing `save-excursion' wrapped around the
> `save-window-excursion' in `org-fast-tag-selection' (org.el line 14567
> in my version).  This would be analogous to what is done in
> `org-fast-todo-selection' and fixes my issue.


I am experiencing the same issue. Based on Ingo's analysis I made the 
following change which resolved the problem for me.


Thanks,
-Damian


diff --git a/lisp/org.el b/lisp/org.el
index 94713a7e5..3f2bd5758 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -12484,6 +12484,7 @@ Returns the new tags string, or nil to not 
change the current settings."

   " "
 (make-string (- org-tags-column (current-column)) ?\ 
))

 (move-overlay org-tags-overlay ov-start ov-end)
+    (save-excursion
 (save-window-excursion
   (if expert
  (set-buffer (get-buffer-create " *Org tags*"))
@@ -12645,7 +12646,7 @@ Returns the new tags string, or nil to not 
change the current settings."

   (delete-overlay org-tags-overlay)
   (if rtn
  (mapconcat 'identity current ":")
-   nil
+    nil)

 (defun org-make-tag-string (tags)
   "Return string associated to TAGS.




[O] Code block evaluation is disabled

2016-01-09 Thread Damian Bernardini
Whenever I try to evaluate code I get the following:

Evaluation of this xxx code-block (x) is disabled.

Sometime I evaluated these code-blocks, I don't know what has changed since
the last time they worked.
I've tried with sh and ledger codes with the same results.

I've read the manual but I haven't found anything about it.

Org-mode version: 8.3.3
Emacs version: 24.5.1

;; Babel
(org-babel-do-load-languages
 'org-babel-load-languages
 '((R . t)
  (emacs-lisp . t)
  (gnuplot . t)
  (calc . t)
  (ditaa . t)
  (latex . t)
  (org . t)
  (sqlite . t)
  (sh . t)
  (dot . t )
  (sql . t)
  (lisp . t)
  (ledger . t)
  ))


Re: [O] Source code evaluation problem

2015-04-25 Thread Damian Bernardini
After a reinstallation I forgot to do make autoloads.
Now, it's working perfectly.
It was my mistake, sorry and thank you for your help.

2015-04-25 18:26 GMT+00:00 Eric S Fraga e.fr...@ucl.ac.uk:

 On Saturday, 25 Apr 2015 at 17:55, Damian Bernardini wrote:
  You were right.
  If I do M-x org-version it says:
  Org-mode version 8.3beta (release_8.3beta-1062-gce4e64-git @ mixed
  installation! /usr/share/emacs/24.5/lisp/org/ and
  /home/damian/git/org-mode/lisp/)
 
  I've downloaded org from git and loaded it with:
  (add-to-list 'load-path ~/git/org-mode/lisp)
  (add-to-list 'load-path ~/git/org-mode/contrib/lisp)

 which is what I have:

   (add-to-list 'load-path ~/git/org-mode/lisp)
   (add-to-list 'load-path ~/git/org-mode/contrib/lisp/)
   (require 'org)

 Maybe you have something earlier in your initialisation that brings in
 the old version?  Have you done make in your ~/git/org-mode directory?

 What happens if you start emacs with -Q, execute the lines above
 and then visit your ledger org file?

 --
 : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org
 release_8.3beta-1062-gce4e64



Re: [O] Source code evaluation problem

2015-04-25 Thread Damian Bernardini
You were right.
If I do M-x org-version it says:
Org-mode version 8.3beta (release_8.3beta-1062-gce4e64-git @ mixed
installation! /usr/share/emacs/24.5/lisp/org/ and
/home/damian/git/org-mode/lisp/)

I've downloaded org from git and loaded it with:
(add-to-list 'load-path ~/git/org-mode/lisp)
(add-to-list 'load-path ~/git/org-mode/contrib/lisp)

How can I tell emacs to not load the /usr/share/emacs/24.5/lisp/org package?

2015-04-25 17:35 GMT+00:00 Eric S Fraga e.fr...@ucl.ac.uk:

 On Saturday, 25 Apr 2015 at 15:47, Damian Bernardini wrote:
  I'm trying to use ledger blocks inside org with babel:

 [...]

  I'm trying the noweb example from:
  http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-ledger.html
 
  I can evaluate and get results from income and expenses blocks, but when
 I
  try to run C-c C-c on balance block I get:
  Symbol's function definition is void: org-id-find-id-file

 What version of org are you using?  How are you loading org?

 The error message you get is rather suspicious and makes me think you
 might have an installation of org that is possibly a mix of old and new.
 That function is in org-id.el which is required by org-attach which
 itself is required by org...

 What is the output of M-x find-library RET org RET?

 Finally, maybe prepare a minimal example and post it to this list.  I
 use ledger in org all the time and it works fine.
 --
 : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org
 release_8.3beta-1062-gce4e64



[O] Source code evaluation problem

2015-04-25 Thread Damian Bernardini
I'm trying to use ledger blocks inside org with babel:

Babel language config:
(org-babel-do-load-languages
 'org-babel-load-languages
 '((R . t)
   (emacs-lisp . t)
   (ledger . t)))

Ledger lisp path:
(autoload 'ledger-mode ledger-mode A major mode for Ledger t)
(add-to-list 'load-path
 (expand-file-name /home/damian/git/ledger/lisp/))
(add-to-list 'auto-mode-alist '(\\.ledger$ . ledger-mode))

I'm trying the noweb example from:
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-ledger.html

I can evaluate and get results from income and expenses blocks, but when I
try to run C-c C-c on balance block I get:
Symbol's function definition is void: org-id-find-id-file

Ledger mode and ledger from the command line are working.


[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

2015-02-20 Thread Damian Nadales
  PMJI, but at
 http://permalink.gmane.org/gmane.emacs.orgmode/95159,
  Nicolas Goaziou said This should be fixed.
 
  Perhaps this bug report can simply be closed then ?

 If it's fixed, please close it.
[Damian Nadales]
Thanks for the fix.

I must add that I discovered the bug by accident. Normally I don't change the 
mode when editing an special org buffer.

Best,
Damian.
-- The information contained in this communication and any attachments is 
confidential and may be privileged, and is for the sole use of the intended 
recipient(s). Any unauthorized review, use, disclosure or distribution is 
prohibited. Unless explicitly stated otherwise in the body of this 
communication or the attachment thereto (if any), the information is provided 
on an AS-IS basis without any express or implied warranties or liabilities. To 
the extent you are relying on this information, you are doing so at your own 
risk. If you are not the intended recipient, please notify the sender 
immediately by replying to this message and destroy all copies of this message 
and any attachments. The sender nor the company/group of companies he or she 
represents shall be liable for the proper and complete transmission of the 
information contained in this communication, or for any delay in its receipt.





[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

2015-02-20 Thread Damian Nadales
Hi Eli,

  [Damian Nadales]
  That's weird. Which buffer are you killing, the Org buffer, or the new 
  buffer
 that is created when pressing C-c ' inside the source block? Is the latter the
 one I cannot kill.

 There was no C-c ' in the recipe you posted.

[Damian Nadales]
No, it wasn't. Sorry for that.

I replied to Glenn Morris yesterday, mentioning these extra details.

 What is the full recipe to reproduce the problem, please?
[Damian Nadales]
So the recipe full recipe is:
 - launch emacs -Q
 - Create a buffer ``myorgfile.org``
 - Insert the following text:
   #+BEGIN_SRC C++

  #+END_SRC
- Position the cursor in the source code block (between the BEGIN and END 
directives)
- Press C-c ' (this will open a new buffer)
- Perform M-x c++-mode in the new buffer
- C-x k (kill the newly created buffer)
- You should see the error message now.

Let me know if there is anything else I could do.

Sorry for the vagueness in my first instructions.

Best regards,
Damian.

-- The information contained in this communication and any attachments is 
confidential and may be privileged, and is for the sole use of the intended 
recipient(s). Any unauthorized review, use, disclosure or distribution is 
prohibited. Unless explicitly stated otherwise in the body of this 
communication or the attachment thereto (if any), the information is provided 
on an AS-IS basis without any express or implied warranties or liabilities. To 
the extent you are relying on this information, you are doing so at your own 
risk. If you are not the intended recipient, please notify the sender 
immediately by replying to this message and destroy all copies of this message 
and any attachments. The sender nor the company/group of companies he or she 
represents shall be liable for the proper and complete transmission of the 
information contained in this communication, or for any delay in its receipt.





[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

2015-02-19 Thread Damian Nadales
 I cannot reproduce this.  I tried both Emacs 24.4 and the pretest of 24.5.  In
 both cases, Emacs asks me whether to kill a buffer that is modified, and once
 I answer YES, the buffer is killed.

[Damian Nadales]
That's weird. Which buffer are you killing, the Org buffer, or the new buffer 
that is created when pressing C-c ' inside the source block? Is the latter the 
one I cannot kill.


 Is it possible that you are using Org mode from the Org repository, not the
 one bundled with Emacs?
[Damian Nadales]
I've only installed packages through the emacs package manager, and Org mode 
was not one of them. The command ``org-version`` reports:

Org-mode version 8.2.10 (release_8.2.10 @ 
/home/dnadales/opt/share/emacs/24.4/lisp/org/)

I don't know if there is any other information I could give.

In any case thanks for your time.
-- The information contained in this communication and any attachments is 
confidential and may be privileged, and is for the sole use of the intended 
recipient(s). Any unauthorized review, use, disclosure or distribution is 
prohibited. Unless explicitly stated otherwise in the body of this 
communication or the attachment thereto (if any), the information is provided 
on an AS-IS basis without any express or implied warranties or liabilities. To 
the extent you are relying on this information, you are doing so at your own 
risk. If you are not the intended recipient, please notify the sender 
immediately by replying to this message and destroy all copies of this message 
and any attachments. The sender nor the company/group of companies he or she 
represents shall be liable for the proper and complete transmission of the 
information contained in this communication, or for any delay in its receipt.


[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

2015-02-18 Thread Damian Nadales
Hi Glenn,

 Damian Nadales wrote:


  -  Run emacs -Q
 
  -  Create an org-mode file (i.e. ``myorgfile.org``)
 
  -  Insert the following text:
 
  o   #+BEGIN_SRC C++
 
  #+END_SRC
 
  -  Edit the source block by placing the cursor inside the SRC block.
 
[Damian Nadales]
By the way, here editing should be done by placing the cursor in the org buffer 
``myorgfile.org``, and then pressing C-' to edit the source code in a different 
buffer. And this is the buffer that cannot be killed.

  -  Start C++ mode (c++-mode)
 
  -  Try to kill the buffer.

 Please do

 M-x toggle-debug-on-error

 repeat the problem, and post the resulting backtrace.
 (I can't reproduce it.)
[Damian Nadales]
This is what I got.

Debugger entered--Lisp error: (wrong-type-argument overlayp nil)
  delete-overlay(nil)
  #[nil \301!\207 [org-edit-src-overlay delete-overlay] 2]()
  kill-buffer(*Org Src myorgfile.org[ c++ ]*)
  call-interactively(kill-buffer nil nil)
  command-execute(kill-buffer)

Thanks for your help.
-- The information contained in this communication and any attachments is 
confidential and may be privileged, and is for the sole use of the intended 
recipient(s). Any unauthorized review, use, disclosure or distribution is 
prohibited. Unless explicitly stated otherwise in the body of this 
communication or the attachment thereto (if any), the information is provided 
on an AS-IS basis without any express or implied warranties or liabilities. To 
the extent you are relying on this information, you are doing so at your own 
risk. If you are not the intended recipient, please notify the sender 
immediately by replying to this message and destroy all copies of this message 
and any attachments. The sender nor the company/group of companies he or she 
represents shall be liable for the proper and complete transmission of the 
information contained in this communication, or for any delay in its receipt.