[BUG] org-agenda-list opens new frame with org-agenda-window-setup other-window and split-window-vertically [9.6 (release_9.6-49-g47d129 @ /home/data1/protected/Programming/Software/emacs/lisp/org/)]
When I set following: (setq org-agenda-window-setup 'other-window) with intention to get agenda in other window, together with following: (setq split-window-preferred-function 'split-window-vertically) then (org-agenda-list) is not going to show itself in other window but in new or other frame. Only when I leave following variable: (setq split-window-preferred-function 'split-window-sensibly) Then agenda would show in other window. Expected action is not that agenda shows in other frame but in other window no matter how split-window-preferred-function is set. What is happening may be seen on the video: https://gnu.support/images/tmp/2022-12-24/2022-12-24-10:43:52.ogv Emacs : GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.6, Xaw3d scroll bars) of 2022-12-22 Package: Org mode version 9.6 (release_9.6-49-g47d129 @ /home/data1/protected/Programming/Software/emacs/lisp/org/) -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/
CSV agenda export formats some day and month values as single digits
Version: Org mode version 9.6 (release_9.6-3-ga4d38e @ /usr/local/share/emacs/29.0.60/lisp/org/) CSV export for the agenda is formatting January 1, 2023 as "2023-1-1" and not "2023-01-01". The raw output is here: https://pastebin.com/raw/EyN1JbhP The last two lines both have "2023-1-1". This is incorrect because: Expression: (format-time-string "%04Y-%02m-%02d" (date-to-time "2023-1-1")) Result: "1999-12-31"
missing from the manual
Dear maintainers, The following commands are missing from the manual! org-forward-element org-backward-element These two should be mentioned in the manual in section 2.3 "Motion" I just found them via the *HELP* page for org mode (by accident). I thought nothing like them existed in org mode, so I had my own (less well crafted) commands. Peter
Re: Recommended way to work on main without upgrading Org?
Richard Kim writes: > Richard Kim writes: > >> Karthik Chikmagalur writes: >> >>> I can get it to work with emacs -Q as well, and this is good for testing, >>> thank you. >>> >>> But I'm looking for a way to retain the rest of my configuration and swap >>> out >>> Org as required. Otherwise I can't do any interactive development. Another >>> alternative is to set up a completely different init directory and run Emacs >>> with a chemacs2 profile or with the new --init-directory flag, but >>> considering >>> the complexity/size of my configuration this would be onerous. >> >> How about specifying org version of your choice on command line like this? >> >> emacs --eval "(add-to-list 'load-path \"/path/to/org\")" >> >> So long as you don't activate another org mode package within your >> start-up files, above should work I think. > > If you want to better control where your org path end up in load-path, > then you can use one of several hooks, e.g., following delays updating > load-path till almost the very end of emacs startup process > > emacs --eval "(add-hook 'emacs-startup-hook (lambda () (add-to-list > 'load-path \"/path/to/org\")) 100)" > > See [[info:elisp#Startup Summary]] for emacs startup details. An alternative is to use --init-directory with thin wrapper around your normal config, e.g., you can create arbitrary configuration which makes small tweaks to your normal configuration with something like the following: $ cat /tmp/e1/early-init.el (add-to-list 'load-path "/path/to/org") (setq user-emacs-directory "~/.emacs.d/") (load-library (expand-file-name "early-init.el" user-emacs-directory)) $ cat /tmp/e1/init.el (load-library (expand-file-name "init.el" user-emacs-directory)) $ emacs --init-directory /tmp/e1
Re: Recommended way to work on main without upgrading Org?
Richard Kim writes: > Karthik Chikmagalur writes: > >> I can get it to work with emacs -Q as well, and this is good for testing, >> thank you. >> >> But I'm looking for a way to retain the rest of my configuration and swap out >> Org as required. Otherwise I can't do any interactive development. Another >> alternative is to set up a completely different init directory and run Emacs >> with a chemacs2 profile or with the new --init-directory flag, but >> considering >> the complexity/size of my configuration this would be onerous. > > How about specifying org version of your choice on command line like this? > > emacs --eval "(add-to-list 'load-path \"/path/to/org\")" > > So long as you don't activate another org mode package within your > start-up files, above should work I think. If you want to better control where your org path end up in load-path, then you can use one of several hooks, e.g., following delays updating load-path till almost the very end of emacs startup process emacs --eval "(add-hook 'emacs-startup-hook (lambda () (add-to-list 'load-path \"/path/to/org\")) 100)" See [[info:elisp#Startup Summary]] for emacs startup details.
Re: Recommended way to work on main without upgrading Org?
Karthik Chikmagalur writes: > I can get it to work with emacs -Q as well, and this is good for testing, > thank you. > > But I'm looking for a way to retain the rest of my configuration and swap out > Org as required. Otherwise I can't do any interactive development. Another > alternative is to set up a completely different init directory and run Emacs > with a chemacs2 profile or with the new --init-directory flag, but considering > the complexity/size of my configuration this would be onerous. How about specifying org version of your choice on command line like this? emacs --eval "(add-to-list 'load-path \"/path/to/org\")" So long as you don't activate another org mode package within your start-up files, above should work I think.
Re: org-persist files in /tmp
On Fri, Dec 23, 2022 at 09:12:52PM +0700, Max Nikulin wrote: [...] > If you demonstrate that e.g., when working with encrypted files, their > sensitive content leaks to the cache then it will raise the severity of the > issue. Of course, the always appreciated option is to provide a patch that > consistently makes org-persist optional. Understood that hint, and you are, of course, right :-) Cheers -- t signature.asc Description: PGP signature
Re: Table refresh very slow
On 23/12/2022 14:34, Vikas Rawal wrote: Org mode version 9.6 (release_9.6-126-gf731d4 I have noticed a new problem: tables take a long time to refresh if I change the structure Is this a known problem? Your version should include the fix 76a725317 2022-12-10 08:45:54 +0300 Ihor Radchenko: orgtbl-to-generic: Improve performance mentioned in Ihor Radchenko to emacs-orgmode… Re: bash code block runs slow on org 9.6. Sat, 10 Dec 2022 05:53:44 +. https://list.orgmode.org/87edt7st1z.fsf@localhost Perhaps CPU profile may shed some light on the problem, e.g. if it is related to more accurate width calculations.
Re: org-persist files in /tmp
On 23/12/2022 13:35, to...@tuxteam.de wrote: On Thu, Dec 22, 2022 at 11:07:52PM +0700, Max Nikulin wrote: Another idea is to avoid caching of parse result for small files. I haven't been following along very closely, but seeing the involved complexities, I'd appreciate a knob to disable caching altogether. Ihor wrote that org-persist usage is not limited to org-element cache. Another case is referenced remote files. Perhaps e.g. LaTeX preview still uses old approach for generated image, but it is rather close case. I do not mind to have a setting that disables org-persist, but it requires some amount of work. Its priority unlikely will be high. If you demonstrate that e.g., when working with encrypted files, their sensitive content leaks to the cache then it will raise the severity of the issue. Of course, the always appreciated option is to provide a patch that consistently makes org-persist optional.
