[BUG] org-agenda generation missing some entries
After git bisect, I found the bad commit: #+begin_example 0ef88e2d9 * | bad @ org-agenda.el/org-agenda-get-scheduled: Use cache #+end_example after org-agenda generation, lot of entries not displayed. Then I found lot of errors in =*Messages*= buffer. #+begin_example Wrong type argument: stringp, (timestamp (:type active :raw-value "<2021-02-28 Sun>" :year-start 2021 :month-start 2 :day-start 28 :hour-start nil :minute-start nil :year-end 2021 :month-end 2 :day-end 28 :hour-end nil :minute-end nil :begin 7679 :end 7696 :post-blank 1)); Skipping entry Wrong type argument: stringp, (timestamp (:type active :raw-value "<2021-02-28 Sun>" :year-start 2021 :month-start 2 :day-start 28 :hour-start nil :minute-start nil :year-end 2021 :month-end 2 :day-end 28 :hour-end nil :minute-end nil :begin 11212 :end 11229 :post-blank 1)); Skipping entry Wrong type argument: stringp, (timestamp (:type active :raw-value "<2020-06-30 Tue>" :year-start 2020 :month-start 6 :day-start 30 :hour-start nil :minute-start nil :year-end 2020 :month-end 6 :day-end 30 :hour-end nil :minute-end nil :begin 13781 :end 13798 :post-blank 1)); Skipping entry .. #+end_example <#secure method=pgpmime mode=sign> -- [ stardiviner ] I try to make every word tell the meaning that I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Re: [BUG] org-agenda generation missing some entries
"Christopher M. Miles" writes: > After git bisect, I found the bad commit: > > #+begin_example > 0ef88e2d9 * | bad @ org-agenda.el/org-agenda-get-scheduled: Use cache > #+end_example > > after org-agenda generation, lot of entries not displayed. Then I found lot > of errors in =*Messages*= buffer. Can you provide a backtrace with debug-on-error set to t? Best, Ihor
Re: the tangled web of org-cite, selectrum, completing-read, ...
On Wednesday, 20 Oct 2021 at 14:43, Bruce D'Arcus wrote: > BTW, per the bibtex-actions README, there are a few other small > packages you want to install for the best experience. Agreed. I actually had all of these bar embark installed already. thank you, eric -- : Eric S Fraga via Emacs 28.0.60, Org release_9.5-149-g781080 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: [BUG] org-agenda generation missing some entries
I pushed tentative fix to main. Let me know if you keep seeing the error. Best, Ihor
Re: Clarify bug report requirements wrt mailing list subscription
On Wed, Oct 20, 2021 at 08:33:42PM -0300, Carlos Pita wrote: > I find the instructions about bug reporting in [1] lacking a heads-up > that subscription to the mailing list is a (soft?) prerequisite. It's > true that it links to [2] which states: > > You can subscribe to the list from this web page. If you are not a > member of the mailing list, your mail will be passed to the list > after a moderator has approved Subscription is not a prerequisite to sending your message to the mailing list. If you do not subscribe, your message will wait for moderation. There is no guarantee that your message will pass moderation quickly, it could be many days because we have only volunteer moderators. Once your address has passed moderation, if you aren't already a subscriber, you will be added to a list of authorized senders so you don't have to wait in moderation again. Either way it's true that the mailing list has some reasonable protections against spam. I'm sorry if that's caused you some frustration, but we're all just volunteers with limited time. I find the Org list policy to be very liberal. I am on other mailing lists where subscription is mandatory to send any message, and unauthorized senders are ignored completely. > but also it's true [3] states: > > The Org mailing list is a members only mailing list to prevent > spam. Membership is freely available and only requires that you > subscribe to the list and confirm your email address. > > Moreover, that it seemingly is a soft requirement implies that I'm not > getting any feedback for some time about the status of my report. Indeed. Spam protections can cause problems. However, what are your expectations regarding a response for a bug report? Specifically are you referring to the time until your report shows up on the list archive, or the issue itself is addressed? I agree we should try to effectively communicate what you should expect when posting a bug report the first time, and how quickly your report can reach the list. (ie: instantly if you subscribe, or expect delays in moderation) As to how fast the bug can be confirmed or addressed, there are no guarantees. > What do you think of: > > - Adding some brief mention to subscription in [1]. I've updated the Worg page, it should be pushed out soon. > - Resolve the apparent contradiction about subscription being a > prerequisite or not between [2] and [3]. I've updated [3] as well, pending next update. > [1] https://orgmode.org/worg/org-issues.html > > [2] https://orgmode.org/org.html#Feedback > > [3] https://orgmode.org/worg/org-mailing-list.html -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: org-persist - bug report
Colin Baxter writes: > > (setq org-element--cache-self-verify 'backtrace) > > (setq org-element--cache-self-verify-frequency 1) > > I set the above in my ~/.emacs > > > If a warning appears, backtrace could be helpful. If not, it > > should be something to do with org-element-cache-map. > > The max-specpdl-size error has happened again when I tried to add a note > to an agenda item. Emacs hung and had to be killed. The debugger buffer > was empty and the only other information given was the message: > > mapc: Lisp nesting exceeds `max-lisp-eval-depth' It indicates yet another possible problematic place. But I still need more information. I just pushed a change that can help with debugging this. If you update to current main and set `org-element--cache-interrupt-C-g' to t, you can press "C-g" 6 times (1 + org-element--cache-interrupt-C-g-max-count) to force-quit the "hang". When you encounter the hang again, please try to reproduce it after force quitting. If you figure out some way to reproduce, set `org-element--cache-diagnostics' to t just before reproducing (M-: (setq org-element--cache-diagnostics t) ). Then, post the contents added to your *Warnings* buffer. It will be very verbose and can hopefully help me figure out the problem. Best, Ihor
org-persist? error "Variable binding depth exceeds max-specpdl-size" (was: org-persist - bug report)
Max Nikulin writes: > Ihor, I have seen your instructions for more debug info, but I have not > tried them yet. In the meanwhile I have tracked my problem down to to > the following minimal file > > --- >8 --- > #+begin_example org >,* H > #+end_example > --- 8< --- > > M-x org-lint > > Debugger entered--Lisp error: (error "Variable binding depth exceeds > max-specpdl-size") > ... > org-filename-concat I cannot reproduce with your minimal example, but the error indicates some issue with persistent cache. Can you: 1. Go to cache directory (~/.cache/org-persist) 2. Open "index" file and find the record for your minimal file and find :persist-file property. That property is relative cache file path. 3. Attach the contents of the :persist-file Then, can you delete your cache folder and try to reproduce again? By the way, did your Emacs crash recently? > Another observation: > > C-c * on a line to make it a header causes the following warning: > > Warning (emacs): org-element--cache: Unregistered buffer modifications > detected. Resetting > The buffer is: example.org > Current command: nil I cannot reproduce this as well. The fact that "Current command: nil" is suspicious. Is "C-c *" bound to org-ctrl-c-star for you? Best, Ihor
Re: org-persist - bug report
On 21/10/2021 02:04, Colin Baxter wrote: The max-specpdl-size error has happened again when I tried to add a note to an agenda item. Emacs hung and had to be killed. The debugger buffer was empty and the only other information given was the message: mapc: Lisp nesting exceeds `max-lisp-eval-depth' Ihor, I have seen your instructions for more debug info, but I have not tried them yet. In the meanwhile I have tracked my problem down to to the following minimal file --- >8 --- #+begin_example org ,* H #+end_example --- 8< --- M-x org-lint Debugger entered--Lisp error: (error "Variable binding depth exceeds max-specpdl-size") ... org-filename-concat Actually I can not update another example block after editing it in a special buffer (C-c C-'). commit a149fdd5699b9279846fb11184529f8cf47b36b5 Author: Ihor Radchenko Date: Thu Oct 21 16:50:10 2021 +0800 Emacs 1.26.3 Another observation: C-c * on a line to make it a header causes the following warning: Warning (emacs): org-element--cache: Unregistered buffer modifications detected. Resetting The buffer is: example.org Current command: nil Feel free to response to another thread, there are several ones for problems with new cache.
[PATCH] oc-bibtex.el: add :follow property from oc-basic
Hello all,
I may be violating some coding convention but the attached patch re-uses
the org-cite-basic-goto function from the basic org-cite processor to
implement the follow directive for the bibtex processor. Seemed like an
obvious win...
Seems to work just fine for me. I do wonder: should I somehow declare
the function that is being used in oc-bibtex.el given that it is defined
in oc-basic.el? (my lack of elisp-foo showing here)
Thank you,
eric
--
: Eric S Fraga via Emacs 28.0.60, Org release_9.5-149-g781080
: Latest paper written in org: https://arxiv.org/abs/2106.05096
>From 297213bcff8f7f743ab0ce36f940d28385e6eb0f Mon Sep 17 00:00:00 2001
From: Eric S Fraga
Date: Thu, 21 Oct 2021 15:20:43 +0100
Subject: [PATCH] oc-bibtex.el: add :follow property from oc-basic
* oc-bibtex.el (org-cite-register-processor): Specify the function for
the follow directive as the function defined for the basic org-cite
processor.
---
lisp/oc-bibtex.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/oc-bibtex.el b/lisp/oc-bibtex.el
index 52dfa0fca..866c51c15 100644
--- a/lisp/oc-bibtex.el
+++ b/lisp/oc-bibtex.el
@@ -79,6 +79,7 @@ state, as a property list."
(org-cite-register-processor 'bibtex
:export-bibliography #'org-cite-bibtex-export-bibliography
:export-citation #'org-cite-bibtex-export-citation
+ :follow #'org-cite-basic-goto
:cite-styles
'((("nocite" "n"))
(("nil"
--
2.30.2
re-scanning bibliography for org-cite
Dear all, simple question: how can I get org-cite to rescan my bibliography (.bib) file when it changes? When I'm writing a paper, as I'm doing now, I add entries to my bibliography as I write but org-cite is not aware of any new entries. I have gone through the code but cannot see where the bib entries are actually read. (my bad) Thank you, eric -- : Eric S Fraga via Emacs 28.0.60, Org release_9.5-149-g781080 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: org-persist - bug report
> Max Nikulin writes: > On 21/10/2021 02:04, Colin Baxter wrote: >> >> The max-specpdl-size error has happened again when I tried to add >> a note to an agenda item. Emacs hung and had to be killed. The >> debugger buffer was empty and the only other information given >> was the message: >> >> mapc: Lisp nesting exceeds `max-lisp-eval-depth' > Ihor, I have seen your instructions for more debug info, but I > have not tried them yet. In the meanwhile I have tracked my > problem down to to the following minimal file > --- >8 --- > #+begin_example org ,* H #+end_example > --- 8< --- > M-x org-lint > Debugger entered--Lisp error: (error "Variable binding depth > exceeds max-specpdl-size") ... org-filename-concat I can reproduce that. Then emacs just hangs. I have the latest org-mode. Best wishes, Colin.
Re: [BUG] "args out of range" on link heading completion [9.5 (9.5-gd361c7 @ /Users/carlos/.emacs.d/straight/build/org/)]
Carlos, > > ps -- the org-version was > > : Org mode version 9.5 (9.5-gdc154f @ > > /home/minshall/.emacs.d/straight/build/org/) > What are these? Seemingly not git revisions. Can I checkout that > version somehow? If not, pass me your git revision and I will rerun my > recipe there. my belief (fwiw) is that the "9.5" is the major release, and the "dc154f" (after the "9.5-g") is the first 6 characters of the git commit i happened to be running). i see that Ihor has reproduced your problem. cheers, Greg
Re: org-capture broken?
Greg Minshall writes: > hi. with a recent org-mode (*), `org-capture` seems to crash with the > message: > > Variable binding depth exceeds max-specpdl-size > Looks like https://list.orgmode.org/87mtn2za37.fsf@localhost/T/#m1c8761c1b2aaee2642f71367054a5065f9bf92f0 Are you on Emacs 24? Can you try to run make before your emacs -Q -L...? Best, Ihor
Re: [PATCH] oc-bibtex.el: add :follow property from oc-basic
Hi Bruce, thank you for the quick response. On Thursday, 21 Oct 2021 at 11:27, Bruce D'Arcus wrote: > Maybe I'm missing something, but why is that necessary? It's highly likely that I am missing something (not a rare occurence ;-)) but, out of the box without explicitly specifying a follow function, the default behaviour is not well-defined? At least, C-c C-o doesn't work as I would expect. It seems a reasonable expectation to have a default that works out of the box? -- : Eric S Fraga via Emacs 28.0.60, Org release_9.5-149-g781080 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: [PATCH] oc-bibtex.el: add :follow property from oc-basic
On Thu, Oct 21, 2021 at 11:58 AM Eric S Fraga wrote: > > Hi Bruce, > > thank you for the quick response. > > On Thursday, 21 Oct 2021 at 11:27, Bruce D'Arcus wrote: > > Maybe I'm missing something, but why is that necessary? > > It's highly likely that I am missing something (not a rare occurence > ;-)) but, out of the box without explicitly specifying a follow > function, the default behaviour is not well-defined? At least, C-c C-o > doesn't work as I would expect. It seems a reasonable expectation to > have a default that works out of the box? Yes. But the default org-cite-follow-processor is "basic", so it should now work "out of the box". If for some reason it isn't, maybe there's an issue there? Just to be clear what I was meaning by the modularity, you could do this if you wanted: (setq org-cite-insert-processor 'oc-bibtex-actions org-cite-follow-processor 'basic org-cite-activate-processor 'org-ref-cite org-cite-export-processors '((latex bibtex))) Bruce
Re: re-scanning bibliography for org-cite
On Thursday, 21 Oct 2021 at 16:51, Uwe Brauer wrote: > Do you use > org-ref-insert-cite-link > org-ref-helm-insert-cite-link Neither. I use org-cite-insert. -- : Eric S Fraga via Emacs 28.0.60, Org release_9.5-149-g781080 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: org-persist - bug report
Ihor Radchenko writes: > ... There is no problem on Emacs 28, but I can see the error > using Emacs 26.3. I used the following command line from inside the Git > folder to run Emacs (debug.org is the provided minimal file): > > emacs -Q -L ./lisp -l org /tmp/debug.org > > Interestingly, the following does not produce error: > > emacs -Q -L ./lisp -l org -l org-lint /tmp/debug.org Another data point: If I compile Org before testing, the error disappears: make emacs -Q -L ./lisp -l org /tmp/debug.org Best, Ihor
Re: org-capture broken?
Greg Minshall writes: > hi. with a recent org-mode (*), `org-capture` seems to crash with the > message: > > Variable binding depth exceeds max-specpdl-size > > > this happens with (a suitably -L'd) `emacs -Q` > - M-x org-capture > - t > - then crashes Fixed on current main (5315773e8). Best, Ihor
Re: org-persist - bug report
On 21/10/2021 23:03, Ihor Radchenko wrote: It was malformed add-hook call. Fixed in 5315773e8. Thank you, Ihor. I do not see problems I have noticed today anymore.
Re: [PATCH] oc-bibtex.el: add :follow property from oc-basic
Just to say that I recompiled org and reloaded and following a citation now works "out of the box". Caveat: I haven't restarted Emacs (it's my window manager and hence there's significant inertia against exiting Emacs...) so I'll verify everything next time I restart (which could be some time...). Now back to writing my paper! Thanks again, eric PS - writing academic papers fully in org gets easier all the time. org-cite is the latest greatest addition! Thank you all. -- : Eric S Fraga via Emacs 28.0.60, Org release_9.5-163-g4eab5b : Latest paper written in org: https://arxiv.org/abs/2106.05096
how to indent (or refill) properties
Hi I have for example ** DONE G1:H1:G1: :PROPERTIES: :ID: G1 :User1:John :email1: j...@gmail.com :Start:<2021-02-16 mar> :End: <2021-05-24 lun> :STATUS: [ ] :ST1: [ ] :Sheet:H1 :Ex: E2 :Ex: E1 :END: But I would like them to be indented like this ** DONE G1:H1:G1: :PROPERTIES: :ID: G1 :User1:John :email1: j...@gmail.com :Start:<2021-02-16 mar> :End: <2021-05-24 lun> :STATUS: [ ] :ST1: [ ] :Sheet:H1 :Ex: E2 :Ex: E1 :END: Or similar. Is there any function I oversee, that I could use? Thanks Uwe Brauer
Re: [PATCH] oc-bibtex.el: add :follow property from oc-basic
On Thu, Oct 21, 2021 at 10:29 AM Eric S Fraga wrote: > > Hello all, > > I may be violating some coding convention but the attached patch re-uses > the org-cite-basic-goto function from the basic org-cite processor to > implement the follow directive for the bibtex processor. Seemed like an > obvious win... Maybe I'm missing something, but why is that necessary? Processors can be mixed and matched; it's all modular. So you can already use the basic follow processor with the bibtex export processor. Bruce
Re: [PATCH] oc-bibtex.el: add :follow property from oc-basic
On Thursday, 21 Oct 2021 at 12:18, Bruce D'Arcus wrote: > But the default org-cite-follow-processor is "basic", so it should now > work "out of the box". If for some reason it isn't, maybe there's an > issue there? Okay, I do have that variable set to basic so there must be something else wrong in my configuration. I know that C-c C-o was not jumping to my bib file but I don't know why. I will explore and report back. Ignore my patch! > Just to be clear what I was meaning by the modularity, you could do > this if you wanted: Yes, I think I understood this. I'm trying to keep my configuration as simple as possible, something that should be easy as all I want is simple bibtex citations in LaTeX export. thank you, eric -- : Eric S Fraga via Emacs 28.0.60, Org release_9.5-149-g781080 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: org-persist - bug report
> Ihor Radchenko writes: > It was malformed add-hook call. Fixed in 5315773e8. Great! I've pulled org-mode and I can confirm I no longer see my org-persist errors. Excellent. I'm looking at the vc-diff buffer and it's amazing that such a small omission has such a major effect. Best wishes, Colin.
Re: re-scanning bibliography for org-cite
>>> "ESF" == Eric S Fraga writes: > Dear all, > simple question: how can I get org-cite to rescan my bibliography > (.bib) file when it changes? When I'm writing a paper, as I'm doing > now, I add entries to my bibliography as I write but org-cite is not > aware of any new entries. > I have gone through the code but cannot see where the bib entries are > actually read. (my bad) Do you use org-ref-insert-cite-link Or org-ref-helm-insert-cite-link I use the latter in that case, if I finish an entry and update the bib file, then when I call the function again, it is updated, not sure about org-ref-insert-cite-link > Thank you, > eric smime.p7s Description: S/MIME cryptographic signature
Re: org-persist - bug report
Colin Baxter writes: > > M-x org-lint > > > Debugger entered--Lisp error: (error "Variable binding depth > > exceeds max-specpdl-size") ... org-filename-concat > > I can reproduce that. Then emacs just hangs. I have the latest org-mode. Thanks for another confirmation. I tried harder to reproduce and I managed to. There is no problem on Emacs 28, but I can see the error using Emacs 26.3. I used the following command line from inside the Git folder to run Emacs (debug.org is the provided minimal file): emacs -Q -L ./lisp -l org /tmp/debug.org Interestingly, the following does not produce error: emacs -Q -L ./lisp -l org -l org-lint /tmp/debug.org So, there is something strange about loading org-lint library. I tried to instrument org-lint, but M-x debug-on-entry org-lint M-x org-lint somehow did not trigger the debugger. I am confused here. Can someone knowledgeable about Emacs load mechanisms provide any clue about what may be happening? Best, Ihor
org-capture broken?
hi. with a recent org-mode (*), `org-capture` seems to crash with the message: Variable binding depth exceeds max-specpdl-size this happens with (a suitably -L'd) `emacs -Q` - M-x org-capture - t - then crashes after this crash, i seem to be unable to enter the debugger, etc. (`(setq debug-on-error t)`) doesn't work after this crash. my only recourse appears to be to exit emacs. stepping through the code, the last routine was`org-capture-fill-template`. stepping through this routine, it gets as far as `(org-mode))` in (i assume) (let ((org-inhibit-startup t)) and, in "that" routine, the (presumably) infinite recursion/loop happens. i'm loathe (intimidated) to follow the trail into the main code. i wonder if anyone might have any ideas? cheers, Greg (*) Org mode version 9.5 (9.5-ga149fd @ /home/minshall/.emacs.d/straight/build/org/)
Re: re-scanning bibliography for org-cite
On Thu, Oct 21, 2021 at 10:12 AM Eric S Fraga wrote: > > Dear all, > > simple question: how can I get org-cite to rescan my bibliography (.bib) > file when it changes? When I'm writing a paper, as I'm doing now, I add > entries to my bibliography as I write but org-cite is not aware of any > new entries. Do you mean for org-cite-insert? Which insert processor? If it's bibtex-actions, you have to configure the filenotify support mentioned on the README. I'm not sure how the oc-basic one handles this. Bruce
Re: org-persist - bug report
It was malformed add-hook call. Fixed in 5315773e8.
Re: how to indent (or refill) properties
Uwe Brauer writes: > But I would like them to be indented like this > > ** DONE G1:H1:G1: > :PROPERTIES: In Org 9.5, setting org-adapt-indentation to 'headline-data makes :DRAWERS: indented (setting it to t makes everything but headlines indented). If your drawers are already written and you want to mass-reindent them with e.g. C-x h TAB, either make sure point is not on a headline (or TAB will just cycle visibility) or tweak org-cycle-emulate-tab. Or use C-x h M-: (indent-for-tab-command). Not sure how to tell Org how wide indentation should be though.
Re: org-capture broken?
Ihor, > Fixed on current main (5315773e8). confirmed. thanks! from a previous e-mail (but, for my future reference): > Are you on Emacs 24? i'm on GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.27, cairo version 1.17.4) of 2021-03-26 > Can you try to run make before your emacs -Q -L...? make of org mode? (remote possibility: emacs?) cheers, Greg
Re: org-persist - bug report
Thanks. Worked for me
Lisp error: (void-function org-element-keyword-parser)
I've had something strange going on for days that I haven't been able to figure
out. With my usual set up, I can get things working except that any Org files
initially loaded up aren't recognized as Org, but if I run =M-x org-mode= it all
kicks in. There were also transient errors about avl-tree-something showing.
(Whether this is connected to the R problem I mentioned a few days ago, I don't
know, but this was worse so I'm trying to figure it out first.)
I spent a while trying it out with various methods that just confused me more
(and made me consider declaring init backruptcy), but eventually I got it down
to something that I think is reproducible but doesn't make sense to me.
I run Org from source and Emacs from source. I've kept both up to date and
remade them over the past few days as I've been working on this.
I used the minimal-org.el file from https://orgmode.org/org.html#Feedback .
I have a problem.org file that is just:
#+begin_src org
,#+TITLE: Problem?
,#+STARTUP: showall
#+end_src
These are both in /tmp/.
I run:
$ cd /usr/local/src/org-mode
$ git pull
$ git rev-parse HEAD
5315773e8a0838268592617174b221ec7bf1c87a
$ make autoloads
$ cd /tmp/
$ emacs -Q -l minimal-org.el
Emacs starts, I hit =C-x C-f problem.org= ... and I get this error
(also attached; I deleted a list of file modes to make it more readable):
Debugger entered--Lisp error: (void-function org-element-keyword-parser)
org-element-keyword-parser(39 (19))
org--collect-keywords-1(("SETUPFILE" "FILETAGS" "TAGS" "ARCHIVE" "CATEGORY"
"COLUMNS" "CONSTANTS" "LINK" "OPTIONS" "PRIORITIES" "PROPERTY" "SEQ_TODO"
"STARTUP" "TODO" "T YP_TODO") ("ARCHIVE" "CATEGORY" "COLUMNS" "PRIORITIES") nil
("/tmp/problem.org") nil)
org-collect-keywords(("FILETAGS" "TAGS" "ARCHIVE" "CATEGORY" "COLUMNS"
"CONSTANTS" "LINK" "OPTIONS" "PRIORITIES" "PROPERTY" "SEQ_TODO" "STARTUP" "TODO"
"TYP_TODO") ("ARC HIVE" "CATEGORY" "COLUMNS" "PRIORITIES"))
org-set-regexps-and-options()
org-mode()
set-auto-mode-0(org-mode nil)
set-auto-mode--apply-alist((("\\.gpg\\(~\\|\\.~[0-9]+~\\)?\\'" nil
epa-file) MUCH DELETED nil nil)
set-auto-mode()
normal-mode(t)
after-find-file(nil t)
find-file-noselect-1(# "/tmp/problem.org" nil nil
"/tmp/problem.org" (933773 2052))
find-file-noselect("/tmp/problem.org" nil nil t)
find-file("/tmp/problem.org" t)
funcall-interactively(find-file "/tmp/problem.org" t)
call-interactively(find-file nil nil)
command-execute(find-file)
I have no idea what's causing that. Is this reproducible? Does anyone know
what's going on? Surely if other people were seeing it they'd have reported it,
but if this isn't reproducible I don't know why.
Thanks for any help!
Bill
--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, CanadaDebugger entered--Lisp error: (void-function org-element-keyword-parser)
org-element-keyword-parser(39 (19))
org--collect-keywords-1(("SETUPFILE" "FILETAGS" "TAGS" "ARCHIVE" "CATEGORY"
"COLUMNS" "CONSTANTS" "LINK" "OPTIONS" "PRIORITIES" "PROPERTY" "SEQ_TODO"
"STARTUP" "TODO" "TYP_TODO") ("ARCHIVE" "CATEGORY" "COLUMNS" "PRIORITIES") nil
("/tmp/problem.org") nil)
org-collect-keywords(("FILETAGS" "TAGS" "ARCHIVE" "CATEGORY" "COLUMNS"
"CONSTANTS" "LINK" "OPTIONS" "PRIORITIES" "PROPERTY" "SEQ_TODO" "STARTUP"
"TODO" "TYP_TODO") ("ARCHIVE" "CATEGORY" "COLUMNS" "PRIORITIES"))
org-set-regexps-and-options()
org-mode()
set-auto-mode-0(org-mode nil)
set-auto-mode--apply-alist((("\\.gpg\\(~\\|\\.~[0-9]+~\\)?\\'" nil epa-file)
("\\.elc\\'" . elisp-byte-code-mode) ("\\.zst\\'" nil jka-compr) ("\\.dz\\'"
nil jka-compr) ("\\.xz\\'" nil jka-compr) ("\\.lzma\\'" nil jka-compr)
("\\.lz\\'" nil jka-compr) ("\\.g?z\\'" nil jka-compr) ("\\.bz2\\'" nil
jka-compr) ("\\.Z\\'" nil jka-compr) ("\\.vr[hi]?\\'" . vera-mode)
("\\(?:\\.\\(?:rbw?\\|ru\\|rake\\|thor\\|jbuilder\\|rabl\\|ge..." . ruby-mode)
("\\.re?st\\'" . rst-mode) ("\\.py[iw]?\\'" . python-mode) ("\\.m\\'" .
octave-maybe-mode) ("\\.less\\'" . less-css-mode) ("\\.scss\\'" . scss-mode)
("\\.awk\\'" . awk-mode) ("\\.\\(u?lpc\\|pike\\|pmod\\(\\.in\\)?\\)\\'" .
pike-mode) ("\\.idl\\'" . idl-mode) ("\\.java\\'" . java-mode) ("\\.m\\'" .
objc-mode) ("\\.ii\\'" . c++-mode) ("\\.i\\'" . c-mode) ("\\.lex\\'" . c-mode)
("\\.y\\(acc\\)?\\'" . c-mode) ("\\.h\\'" . c-or-c++-mode) ("\\.c\\'" . c-mode)
("\\.\\(CC?\\|HH?\\)\\'" . c++-mode) ("\\.[ch]\\(pp\\|xx\\|\\+\\+\\)\\'" .
c++-mode) ("\\.\\(cc\\|hh\\)\\'" . c++-mode) ("\\.\\(bat\\|cmd\\)\\'" .
bat-mode) ("\\.[sx]?html?\\(\\.[a-zA-Z_]+\\)?\\'" . mhtml-mode) ("\\.svgz?\\'"
. image-mode) ("\\.svgz?\\'" . xml-mode) ("\\.x[bp]m\\'" . image-mode)
("\\.x[bp]m\\'" . c-mode) ("\\.p[bpgn]m\\'" . image-mode) ("\\.tiff?\\'" .
image-mode) ("\\.gif\\'" . image-mode) ("\\.png\\'" . image-mode)
("\\.jpe?g\\'" . image-mode) ("\\.te?xt\\'" . text-mode) ("\\.[tT]e[xX]\\'" .
tex-mode)
Re: Lisp error: (void-function org-element-keyword-parser)
William Denton writes: > I've had something strange going on for days that I haven't been able to > figure > out. With my usual set up, I can get things working except that any Org > files > initially loaded up aren't recognized as Org, but if I run =M-x org-mode= it > all > kicks in. Can you try again with latest main (5315773e8)? Best, Ihor
Re: Shower thought: submit an IETF RFC to register Org as a MIME type
Hi, in https://list.orgmode.org/87tuuw3n15@nicolasgoaziou.fr/#t it's stated: > Org is standardized on lower case. Uppercase is used in the manual as > a poor man's bold, and supported for historical reasons. But C-c C-x p still inserts stuff like: :PROPERTIES: :ARCHIVE: ... :END: Maybe it should be updated or maybe I don't fully understand the convention, perhaps it's just for blocks? But then c-a-p is very lenient since it lists lower and upper case block variants even when I typed a lower case prefix, and upper case usually will go first in the list, hence promoting a seemingly bad practice. Can you clarify? Thank you in advance, Carlos
Re: Lisp error: (void-function org-element-keyword-parser)
William Denton writes: > $ git rev-parse HEAD > 5315773e8a0838268592617174b221ec7bf1c87a Sorry, I missed that you are already on the latest main. I cannot reproduce the problem using relatively recent Emacs master (commit ae9bfaa891c). A blind guess: Try to run make clean? Best, Ihor
Re: [BUG] org-agenda generation missing some entries
Ihor Radchenko writes: > "Christopher M. Miles" writes: > >> After git bisect, I found the bad commit: >> >> #+begin_example >> 0ef88e2d9 * | bad @ org-agenda.el/org-agenda-get-scheduled: Use cache >> #+end_example >> >> after org-agenda generation, lot of entries not displayed. Then I found lot >> of errors in =*Messages*= buffer. > > Can you provide a backtrace with debug-on-error set to t? > > Best, > Ihor It's same, there is no backtrace even I toggled debug-on-error to t. And I also tried you org-element-cache options: #+begin_src emacs-lisp (setq org-element--cache-self-verify 'backtrace) (setq org-element--cache-self-verify-frequency 1) (setq org-element--cache-diagnostics t) #+end_src This does not generate backtrace too. Now I tried your latest push. The errors gone. But org-agenda entries still missing. I checked *Messages* buffer, no error messages, including other error special buffers. no information. <#secure method=pgpmime mode=sign> -- [ stardiviner ] I try to make every word tell the meaning that I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Re: [BUG] org-agenda generation missing some entries
"Christopher M. Miles" writes: > Now I tried your latest push. The errors gone. But org-agenda entries still > missing. I checked > *Messages* buffer, no error messages, including other error special buffers. > no information. Agenda now uses a new algorithm to search entries. There may be a bug there. Can you provide a minimal org file with a heading that should be listed in agenda, but did not show up? Best, Ihor
Re: [BUG] "args out of range" on link heading completion [9.5 (9.5-gd361c7 @ /Users/carlos/.emacs.d/straight/build/org/)]
Hi Igor, I believe the problem is in: (defun pcomplete/org-mode/searchhead () ... ;; When completing a bracketed link, i.e., "[[*", argument ;; starts at the star, so remove this character. (substring pcomplete-stub 1 <-- trailing ]] not removed! Changing the last line to (substring pcomplete-stub 1 -2) fixes it in my example. I don't know if one is supposed to do [[*prefix]] or [[*prefix as is implied by the code, but better to support both, specially considering electric pairs, don't you think? Best regards, Carlos
