Re: Multiple versions of Org in load-path problem

David Masterson writes: > I went so far as to add the following to early-init.el: > > (if (featurep 'org) (load-feature 'org)) > (add-to-list 'load-path (expand-file-name "~/.emacs.d/elpa/org-9.6") > (load-library "org") > > The load-library still fails with the org-assert-version error.

Re: Multiple versions of Org in load-path problem

David Masterson writes: > David Masterson writes: > >> Ihor Radchenko writes: >> >>> David Masterson writes: >>> Is there a proper way to do this? Do I really have to delete the built-in 9.3 version (by hand or package-delete?) or will that mess up something else? I saw

Re: Multiple versions of Org in load-path problem

David Masterson writes: > Ihor Radchenko writes: > >> David Masterson writes: >> >>> Is there a proper way to do this? Do I really have to delete the >>> built-in 9.3 version (by hand or package-delete?) or will that mess up >>> something else? I saw mention of 'unload-feature' which is new

Re: Multiple versions of Org in load-path problem

Ihor Radchenko writes: > David Masterson writes: > >> Is there a proper way to do this? Do I really have to delete the >> built-in 9.3 version (by hand or package-delete?) or will that mess up >> something else? I saw mention of 'unload-feature' which is new to me -- >> would that be safe to

Re: [BUG] ob-R.el: extra empty data.frame columns generated from plain lists after recent change [9.6 (release_9.6-3-ga4d38e @ /usr/share/emacs/30.0.50/lisp/org/)]

Hello, Many thanks to you all for your feedback. >From 1ad16ffb9, I have restored the expected output in R. that is. #+NAME: example-list - simple - not - nested - list #+BEGIN_SRC R :var x=example-list x #+END_SRC #+RESULTS: | simple | | list | On Wednesday, 7 Dec 2022 at 12:16,

Re: Proposal: folding stacked `#+header:' lines in src blocks

h...@heagren.com writes: First question: what do people think of this, do people support this as an idea? I would use this feature. My stack typically includes headers, a name, and a caption. It would be nice to fold them all out of sight. All the best, Tom -- Thomas S. Dye

Re: [BUG] Shift-up/down move the cursor to end of timestamp

It works now, thanks! On Wed, 7 Dec 2022 at 10:53, Ihor Radchenko wrote: > Daniel Clemente writes: > > > Using a file with just one header: > > > > * something > > :CLOCK: > > CLOCK: [2022-12-01 Thu 17:15]--[2022-12-01 Thu 17:30] => 0:15 > > :END: > > > > If I put the cursor on the end

Re: Clocking in is pretty slow in version 9.6 when the item has a large

> On Dec 7, 2022, at 10:36 AM, Ihor Radchenko wrote: > > Sorry, I meant (setq org-element--cache-self-verify nil). > In any case, the time is back to previous, which should be good enough > considering that no optimizations have been made to the clock table > calculation. I just realized my

Re: [BUG] ob-R: session evaluation returns empty ouputs with Org 9.6 [9.6 ( @ /home/fsantos/.emacs.d/elpa/org-9.6/)]

Hello Malcolm, On Wednesday, 7 Dec 2022 at 17:50, Cook, Malcolm wrote: > > Byte-compiling and reloading ob-R.el worked. Glad that you could solve it. From 08433d9b0, I added a test to make sure we are not surprised again. Best regards, Jeremie

Re: Clocking in is pretty slow in version 9.6 when the item has a large

Mark Barton writes: >> On Dec 7, 2022, at 3:53 AM, Ihor Radchenko wrote: >> >> What about setting org-element--cache-self-verify to nil? > > (setq org-element--cache-self-verify-frequency nil) > Update clocktable > Wrong type argument: number-or-marker-p, nil > > Try again but use zero instead

Re: Clocking in is pretty slow in version 9.6 when the item has a large

> On Dec 7, 2022, at 3:53 AM, Ihor Radchenko wrote: > > What about setting org-element--cache-self-verify to nil? (setq org-element--cache-self-verify-frequency nil) Update clocktable Wrong type argument: number-or-marker-p, nil Try again but use zero instead of nil... (setq

Prevent files with excluded FILETAGS from being exported

Hello, Currently when trying to export an org file with FILETAGS set to "noexport" (or any value in `org-export-exclude-tags') the file is still exported with the title and top level text. I propose that be changed so files with FILETAGS in `org-export-exclude-tags' are completely skipped by

[BUG] generated ":comment link" when tangling babel src blocks are not complete (or buggy)

When I tangle code "C-c C-v t" of this org-mode file: #+title: Demo #+property: header-args:sh :tangle example.sh :comments link * Part A ** source #+begin_src sh echo "Part A" #+end_src * Part B ** source

RE: [BUG] ob-R: session evaluation returns empty ouputs with Org 9.6 [9.6 ( @ /home/fsantos/.emacs.d/elpa/org-9.6/)]

>"Cook, Malcolm" writes: > >> I tried applying just the change in >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=456462741 to >> released Org 9.6 and find that when using `:session *R*` the #+RESULTS are >> still empty, but when running without

Re: Syntax question: What is BORDER in 4.17. Text Markup?

Nick Dokos writes: > The problem is that these things are configurable, so the above is onlyu > true by default. But you can redefine `org-emphasis-regexp-components` in > ways that would make the above untrue: hence the more abstract description. They are no longer configurable: ;; This used

Re: Syntax question: What is BORDER in 4.17. Text Markup?

Jens Lechtenboerger writes: > Actually, what about this? Get rid of both, BORDER and BODY, and > specify CONTENTS as follows: > “Either a string (when MARKER represents code or verbatim) or a > series of objects from the standard set, not spanning more than > three lines. In any case,

Re: TBLFM trying to create an infinite number of lines

> Thank you both for reporting! Thank you for fixing! --  [Julien Palard](https://mdk.fr)

Re: [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el

On 07/12/2022 18:43, Ihor Radchenko wrote: That said, I find David Masterson's suggestion promising: (if (and (featurep 'org) (< org-version 9.6)) `version<'? Mixed install may be still a problem in the case of bug fix ("patch" component of the version) release.

Re: TBLFM trying to create an infinite number of lines

Bruno Barbier writes: > Same here with 9.6-pre (release_9.5.5-1096-gf83e45). > > Like with: > > | | > #+TBLFM: $1='(eval "\n") > > IIUC, the command "echo 42" outputs a newline, newlines are not allowed > as in cell values. Thank you both for reporting! Fixed on bugfix.

Re: Two problems with export to Google calendar

On 07/12/2022 19:56, Ihor Radchenko wrote: Neil Jerram: X-WR-TIMEZONE:BST which I think was intended to mean British Summer Time; but Google interpreted it as Bangladesh Standard Time. As a result, my events from Org are shown at the wrong time in Google calendar. By default, ox-icalendar

Re: Multiple versions of Org in load-path problem

David Masterson writes: > Is there a proper way to do this? Do I really have to delete the > built-in 9.3 version (by hand or package-delete?) or will that mess up > something else? I saw mention of 'unload-feature' which is new to me -- > would that be safe to use? In theory, Emacs should

Re: Flyspell causes severe slowdown when manipulating footnotes

aroz...@gmail.com writes: > I just upgraded to Org 9.6 and I've noticed that having flyspell-mode > turned on causes very large slowdowns when adding or deleting footnotes in > an org file with lots of footnotes (e.g., more than 200, which is common > for the academic articles that I use org

Re: [BUG] Org-mode 9.6 parallel build issue [9.6 (N/A @ /usr/share/emacs/site-lisp/org-mode/)]

Maciej Barć writes: >> Could you please provide a more clear recipe to reproduce, if possible? > > There are logs in the bug report on the Gentoo Bugzilla, > from the bug I had already mentioned: > https://884243.bugs.gentoo.org/attachment.cgi?id=839581 > and from the one occurring with the

Re: Two problems with export to Google calendar

Neil Jerram writes: > Firstly, when I last exported during late summer, org generated an > .ics file with > > X-WR-TIMEZONE:BST > > which I think was intended to mean British Summer Time; but Google > interpreted it as Bangladesh Standard Time. As a result, my events > from Org are shown at the

Re: [BUG] Not all time/date strings are recognized as time in org-make-tags-matcher [9.6 (9.6-gd500b4 @ /home/hubisan/.emacs.default/straight/build/org/)]

Daniel Hubmann writes: > After updating to Org 9.6 this match in the agenda > 'SCHEDULED<"<+2d>"+SCHEDULED<>"' shows all scheduled items event if they > are far more in the future than 2 days. > > Tracked this down to a commit (e022a0cea11a0e784ba20ac478a033da7fb1bb7f) > that changed the regular

RE: [BUG] ob-R: session evaluation returns empty ouputs with Org 9.6 [9.6 ( @ /home/fsantos/.emacs.d/elpa/org-9.6/)]

"Cook, Malcolm" writes: > I tried applying just the change in > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=456462741 to > released Org 9.6 and find that when using `:session *R*` the #+RESULTS are > still empty, but when running without :session the results are provided.

Re: [BUG] ob-R.el: extra empty data.frame columns generated from plain lists after recent change [9.6 (release_9.6-3-ga4d38e @ /usr/share/emacs/30.0.50/lisp/org/)]

Jeremie Juste writes: > Many thanks for the insights. I confess that I have never transferred > list from org to R before. I've always use tables and as far as I > understand they works fine in 9.6. > > So assuming this list > > #+name: alist > - first item > - second item > - third item > -

Re: Clocking in is pretty slow in version 9.6 when the item has a large

Mark Barton writes: > FYI here is how reducing that number helped with my clocktable updates in the > order I tested each value. > *** org-element--cache-self-verify-frequency 0.01 > update takes 1:18 (minutes : seconds) > *** org-element--cache-self-verify-frequency 0.005 > update takes 0:48

Re: Two problems with export to Google calendar

On Wed, 7 Dec 2022 at 11:30, Neil Jerram wrote: > > Firstly, when I last exported during late summer, org generated an > .ics file with > > X-WR-TIMEZONE:BST > > which I think was intended to mean British Summer Time; but Google > interpreted it as Bangladesh Standard Time. As a result, my

Re: [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el

Bastien writes: > That said, do you have any idea how to fix the bug people encounter > when installing Org from ELPA and being bitten by "invalid-function > org-assert-version"? I just asked Emacs devs as it does not look like we do anything wrong here. It is probably Emacs package.el doing

Two problems with export to Google calendar

Firstly, when I last exported during late summer, org generated an .ics file with X-WR-TIMEZONE:BST which I think was intended to mean British Summer Time; but Google interpreted it as Bangladesh Standard Time. As a result, my events from Org are shown at the wrong time in Google calendar.

Proposal: folding stacked `#+header:' lines in src blocks

Sometimes I deal with large blocks (generally src blocks) with a lot of header arguments. To deal with this, I stack them up in `#+header:' lines. Real example from a file I have: , | #+header: :results (if (org-export-derived-backend-p org-export-current-backend 'latex) "latex" "file raw")

Re: [BUG] Org 9.6 Inactive timestamp search no longer works as expected.

Kyle Meyer writes: > On 12/03/22 13:44:33 -0500, Carlo Tambuatco wrote: >> Simple inactive timestamp search for recent completed tasks used to return >> as expected. ie: >> >> +TIMESTAMP_IA>=“”+TIMESTAMP_IA<“” >> >> would return all tasks that I completed today. (Had an inactive timestamp >>

Re: [BUG] (org-babel-result-to-file) adds the relative path even if attachment link is generated [9.6 (release_9.6-3-ga4d38e @ /usr/share/emacs/30.0.50/lisp/org/)]

Johan Tolö writes: > With org 9.6 I am having an issue where the following generates a > result with an attachment link that includes the original path to > the file. I expect the link to be relative to the attachment > directory. > > * Test > :PROPERTIES: > :DIR: build > :END: > >

Re: [BUG] Shift-up/down move the cursor to end of timestamp

Daniel Clemente writes: > Using a file with just one header: > > * something > :CLOCK: > CLOCK: [2022-12-01 Thu 17:15]--[2022-12-01 Thu 17:30] => 0:15 > :END: > > If I put the cursor on the end timestamp (on the 3 of 17:30) and press > shift+up or shift-down, the timestamp is correctly

Re: [BUG] Shift-up/down move the cursor to end of timestamp

Daniel Clemente writes: > Using a file with just one header: > > * something > :CLOCK: > CLOCK: [2022-12-01 Thu 17:15]--[2022-12-01 Thu 17:30] => 0:15 > :END: > > If I put the cursor on the end timestamp (on the 3 of 17:30) and press > shift+up or shift-down, the timestamp is correctly

Re: Syntax question: What is BORDER in 4.17. Text Markup?

On Wed, Dec 07, 2022 at 11:29:29AM +0100, Jens Lechtenboerger wrote: > On 2022-12-07, Timothy wrote: [...] > > This seems like an improvement to me, implemented in 56338725e61 :) > > Many thanks, Timothy! Seconded :) -- t signature.asc Description: PGP signature

Re: Syntax question: What is BORDER in 4.17. Text Markup?

On 2022-12-07, Timothy wrote: > Hi Jens, > >> Actually, what about this? Get rid of both, BORDER and BODY, and >> specify CONTENTS as follows: >> “Either a string (when MARKER represents code or verbatim) or a >> series of objects from the standard set, not spanning more than >> three lines. In

Re: Syntax question: What is BORDER in 4.17. Text Markup?

Hi Jens, > Actually, what about this? Get rid of both, BORDER and BODY, and > specify CONTENTS as follows: > “Either a string (when MARKER represents code or verbatim) or a > series of objects from the standard set, not spanning more than > three lines. In any case, CONTENTS must neither begin