> Jarmo Hurri writes:
> 3. Copy ditaa.jar from previous version of org. Works in the short
> run, but I do not think we want to advocate this: "We took
> ditaa.jar out of org, so you will want to download an earlier
> version of org to make ditaa work."
Not true. I use Org m
After today's pull of org-mode I get the warning that org-persist cannot
read its index. This is an entirely new warning (as of today) and I
assume is the result of the recent commits in org-persist.
Please, can this be corrected. The warning is irritating, especially so
since I do not use org-p
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> After today's pull of org-mode I get the warning that org-persist
>> cannot read its index. This is an entirely new warning (as of
>> today) and I assume is the result of
>>>>> Ihor Radchenko writes:
r> Colin Baxter ๐บ writes:
>> Thank you. I cloned org-mode afresh and got the same warning
>> during 'make' - I presume that too is now fixed.
r> The warning should never appear now. I removed it com
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> I may not have understood things fully, but it seems that the
>> org-persist directory is set only by the
>> org-persist-path. Unfortunately, the resulting org-persist
>> dir
> Ihor Radchenko writes:
> Alastair Burt writes:
>> Hi there,
>>
>> I couldn't find an issue-tracking system for org-mode as they
>> have for projects on github. So I'm emailing you directly.
> Thanks! The bug reporting for Org mode is by email. You can send
> e
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> >> I just upgraded my org-mode to the latest version in >>
>> git. Whenever I visited a certain org file, my Emacs became >>
>> unusable. Any attempt to use M-x (execu
>>>>> 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
> 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 wish
Hello,
Assuming such a question make sense, how do I manually reset org-persist
for all org buffers? It's not clear to me if doing M-x
org-element-cache-reset is sufficient.
Thanks.
Best wishes,
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> Hello,
>>
>> Assuming such a question make sense, how do I manually reset
>> org-persist for all org buffers? It's not clear to me if doing
>> M-x org-ele
Hello,
Whenever I archive a DONE item via 'C-c C-x C-a' I get the warning:
Warning (emacs): org-element--cache: Unregistered buffer modifications
detected. Resetting.
The archiving is successful, but I keep getting the warning and
therefore wonder if there is some org-persist or cache setting th
>>>>> Colin Baxter ๐บ writes:
> Hello, Whenever I archive a DONE item via 'C-c C-x C-a' I get the
> warning:
> Warning (emacs): org-element--cache: Unregistered buffer
> modifications detected. Resetting.
> The archiving is succes
Hi Thor,
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> > Hello, Whenever I archive a DONE item via 'C-c C-x C-a' I get
>> the > warning:
>>
>> > Warning (emacs): org-element--cache: U
Hi Ihor,
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> I'm running Org mode version 9.5 (release_9.5-178-gcf8906) on
>> emacs-28.0.60. Unfortunately, I could not apply your patch
>> ('patch would not apply') using
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> Ok, I now applied your patch and remade org-mode. Unfortunately,
>> I don't see any change. I still get the warning on all the
>> archive commands: org-agenda-archive-default,
I have now discovered what is causing the org-persist warnings. It is
because my org-agenda files have local variables present. If I remove
the local variables, the warnings disappear.
Best wishes,
Colin.
Hi Ihor,
My ECM is as follows. I'm using GNU-Linux and emacs-28.0.60.
1. Delete any existing org-persist directory.
2. mkdir ~/a
3. emacs -Q
4. Evaluate path to latest org-mode. I enter
(add-to-list 'load-path (expand-file-name "~/path/to/git/org-mode/lisp"))
in the scratch buffer and do C-
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> Hi Ihor,
>>
>> My ECM is as follows. I'm using GNU-Linux and emacs-28.0.60.
> Thanks! I was able to reproduce on my system. Should be fixed on
> main via 9f87b1cc
> Michael Maurer writes:
> Subject line says it all, I upgraded to 9.5 two days ago and
> everything seemed to work, but today I fire up the PC and C-c . no
> longer is bound to anything. I guess I could custom-bind it in my
> config, but I'm more interested in why it's happen
Hello,
I have this
#+begin_src elisp
&%%(org-diary :deadline* :timestamp :scheduled*)
#+end_src
at line 9 in my main diary file ~/.emacs.d/diary/main. It worked well up
until recently (a week or so, I think). Now I get the following warning:
--8<---cut here---start--
>>>>> Eric S Fraga writes:
> On Wednesday, 3 Nov 2021 at 06:43, Colin Baxter ๐บ wrote:
>> I have this
>>
>> #+begin_src elisp &%%(org-diary :deadline* :timestamp
>> :scheduled*) #+end_src
> I cannot help you directly b
> Eric S Fraga writes:
> On Thursday, 4 Nov 2021 at 18:21, Michael Maurer wrote:
>> Oh. I assumed
>>
>> #+begin_src elisp &%%(org-diary :deadline* :timestamp
>> :scheduled*) #+end_src
>>
>> is an org-babel code block.
> Yes but I think that was just for the
> Denis Maier writes:
> Are you already on org 9.5? Looks like your still using the "old"
> org-ref links.
> The following mwe might get you started:
> %%
> #+title: Citation tests #+cite_export: csl
> #+bibliogra
>>>>> Eric S Fraga writes:
> On Wednesday, 24 Nov 2021 at 09:59, Colin Baxter ๐บ wrote:
>> Where is citeproc.el? I'm using Org mode version 9.5.1
>> (release_9.5.1-194-gd82936) and I don't see it.
> It's a separate Emacs pa
> Richard Lawrence writes:
> Hi Org community, Some questions for those of you on Emacs 27 and
> 28:
> Does M-j in an org-mode buffer do what you expect? Does it throw
> an error? What function is M-j bound to in Org?
> Backstory:
> I have long been on Emacs 26.3
> Richard Lawrence writes:
> Tim Cross writes:
>> I'm running Emacs 28 and cannot reproduce the issue you observe.
> Hmm, the plot thickens!
>> Running emacs -Q I find M-j is bound to
>>
>> M-j runs the command default-indent-new-line (found in
>> global-map),
Hello Jeff
You clock table works for me, including your missing rate of 150. I
attach a screen shot.
By the way, you have a ":inherit-props t" which is not on the #+BEGIN:
clocktable line. I assume that has been corrupted in the email
formatting.
Best wishes
Hello,
I find the differences between the variables
(1) org-clocktable-defaults
(2) org-agenda-clockreport-parameter-plist
hard to understand.
Ok, (1) seems reasonably clear. It's described in `info' (there's no
doc-string). The variable (2) confuses me. According to its doc string
(there's no
>>>>> Jeff Trull writes:
> Confirmed, after updating org it now works! Thanks for your help.
> On Tue, Nov 30, 2021 at 1:07 AM Colin Baxter ๐บ wrote:
>> Hello Jeff
>>
>> You clock table works for me, including your missing rat
Hello,
I have
#+begin_src emacs-lisp
(setq org-element-use-cache nil)
(setq org-element-cache-persistent nil)
#+end_src
Yet when editing by hand a time string in a today habit I get the
warning:
--8<---cut here---start->8---
Warning (org-element-cache): or
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> I do not have an org-persist cache present. So I wonder where is
>> the cache that I am supposedly corrupting.
> That warning is shown when org-element--parse-to throws an error
Hello Michael,
> Michael Eliachevitch writes:
> Hello, I found a potential bug in org which I can reproduce with a
> minimal configuration.
> I added some org-capture templates purely for clocking into tasks
> via the capture-menu. These capture templates are for things I
Hello Michael,
> Michael Eliachevitch writes:
> Hello Colin,
>> This is amazing. I have run into exactly the same problem. I was
>> wondering whether to report it!
>>
>> Oh, and I can reproduce the bug with your ECM.
> Glad that I'm not alone. When you say you ran i
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> If you get no response on this org-mode list, perhaps re-submit
>> it as a normal emacs bug (M-x report-emacs-bug ).
> That's not a good idea. org-mode related staff is just forw
Hello,
A TODO item scheduled for a future date ordinarily does not appear in
today's agenda. However, this is not the case if the TODO has a note
dated today in its log drawer. The TODO item is now visible in today's
agenda, even though it's scheduled for the future. If this isn't a bug
then how c
d org-agenda-log-mode-items?
Well, this is embarrassing. On a newly launched emacs, I cannot now
reproduce what I originally saw. I am sorry for forgetting to try the
obvious things before posting!
> On 12/17/21, Colin Baxter ๐บ wrote:
>> Hello,
>>
>> A TODO item
There appears to be confusion between "org-journal-new-entry" and
"org-goto". My ME is:
1. emacs -Q (I used emacs-29.0.50)
2. M-x load-library
3. /path/to/org-journal.el
4. C-h c
5. C-c C-j
6. "C-c C-j runs the command org-journal-new-entry"
7. Create an org file (say "test.org") from C-x C-
Thank you for the reply.
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> There appears to be confusion between "org-journal-new-entry" and
>> "org-goto". My ME is:
>>
>> 1. emacs -Q (I used emacs-29.0
I've changed the kbd for org-journal-new-entry to "C-c j". Simpler too.
Thanks.
Best wishes, Colin -
> Nathaniel Nicandro writes:
> Hello all,
> I'm the maintainer of the emacs-jupyter project
> (https://github.com/nnicandro/emacs-jupyter) which essentially
> integrates Jupyter kernels (https://jupyter.org) with Org mode
> source blocks.
jupyter.org in using cloudflare
> Rudolf Adamkoviฤ writes:
> If I remember well, Org decided to suggest with lowercase keywords
> (and use uppercase keywords in the manual, for some reason).
> Then, we should change "org-babel-results-keyword" from "RESULTS"
> to "results".
Change it for yourself. Please do
> Timothy writes:
> Hi Gyro,
>> Consider Emersonโs quote:
>>
>> โA foolish consistency is the hobgoblin of little minds, adored
>> by little statesmen and philosophers and divines. With
>> consistency a great soul has simply nothing to do.โ
> I think applying a
>>>>> Ihor Radchenko writes:
> Colin Baxter ๐บ writes:
>> What is the point of changing a default? Users can change to
>> whatever they like, but a default is a default - i.e. remains
>> fixed. Why a particular default arose belongs to peculi
> Rudolf Adamkoviฤ writes:
> Ihor Radchenko writes:
>> So, unless there is overwhelming support for changing uppercase
>> defaults into lowercase and a thorough patch, I am inclined
>> towards preserving the existing behaviour.
> The results so far:
> - For inconsis
> Sรฉbastien Miquel writes:
> Hi, With respect to readability, I only mean to point out that the
> $โฆ$ syntax is one less character, and that the \(\) characters are
> quite overloaded.
Indeed. Compare something like
$g=\lim_{\delta m\to 0}(\delta F/\delta m)$
with
\(g=\lim_{\d
> Juan Manuel Macรญas writes:
> Colin Baxter writes:
>> Ah, LaTeX3 - whatever happened to that?
> If you're a LaTeX user, you're already using LaTeX3 to a very high
> extent, even if you don't see it. The current idea is not to
> replace LaTeX2e with LaTeX3 as a new versio
47 matches
Mail list logo
