Re: [WISH] Allow to hide the '*Org Help*' in 'org-goto' [9.5.2 (release_9.5.2-13-gdd6486 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Rudolf Adamkovič writes: >> org-goto-location: Wrong type argument: stringp, nil > > Could we make it so that setting the 'org-goto-help' to 'nil' makes Org > not show the help window for those who do not need it? org-goto-help is a constant. It is not meant to be used to control showing or not showing the *Org Help* buffer. If you want to hide *Org Help* buffer, you can customise your display-buffer-alist: (add-to-list 'display-buffer-alist `(,(rx "*Org Help*") display-buffer-no-window (allow-no-window . t))) Best, Ihor
Open a footnote definition outside a narrowed subtree (workaround)
Hi all, When I am working on a narrowed subtree and want to open a footnote for editing (`C-c C-o': `org-open-at-point'), I get the message: "Definition is outside narrowed part of buffer". I don't know if there is a "standard" solution for that (aside from cloning the buffer and/or removing the restrictions)... I’ve written this simple and quick workaround, and then remapped `C-c C-o' so that: `C-u C-c C-o' my function `C-c C-o' `org-open-at-point' ┌ │ (defun my-org-open-fn-indirect-buffer () │ (interactive) │ (if (not (equal (org-element-type (org-element-context)) 'footnote-reference)) │ (error "Not in a footnote reference!") │ (let* ((el (org-element-context)) │(label (org-element-property :label el)) │(buf (buffer-name)) │(format (format "%s | Note %s" buf label))) │ (when (get-buffer format) │ (kill-buffer format)) │ (clone-indirect-buffer format t) │ (setq header-line-format (format "NOTE %s" label)) │ (widen) │ (org-open-at-point) │ (recenter 0 │ │ (defun my-org-open-at-point () │ (interactive) │ (if (equal current-prefix-arg nil) │ (org-open-at-point) │ (my-org-open-fn-indirect-buffer))) │ │ (with-eval-after-load 'org │ (define-key org-mode-map (kbd "C-c C-o") nil) │ (define-key org-mode-map (kbd "C-c C-o") 'my-org-open-at-point)) └ Best regards, Juan Manuel
Re: Open a footnote definition outside a narrowed subtree (workaround)
Hello, Juan Manuel Macías writes: > When I am working on a narrowed subtree and want to open a footnote for > editing (`C-c C-o': `org-open-at-point'), I get the message: "Definition > is outside narrowed part of buffer". I don't know if there is a > "standard" solution for that (aside from cloning the buffer and/or > removing the restrictions)... The "standard" solution is to use Regards, -- Nicolas Goaziou
Re: [FR][org-cite][oc-basic] Display Editor of Volume in Completion Table
Hello Nicolas, it works perfectly. Thank you very much! Regards, Paul On So, Feb 13 2022 at 22:29:25 +0100, Nicolas Goaziou wrote: Hello, psychosis writes: when executing org-cite-insert with the oc-basic processor, the “author”-field in the completion table is empty for edited volumes. Is it possible to set the “editor”-field as a fallback in case the “author”-field is empty, as is the case for edited volumes? Done in main branch. Please let me know if it works for you. Regards, -- Nicolas Goaziou
Re: Open a footnote definition outside a narrowed subtree (workaround)
Nicolas Goaziou writes: > The "standard" solution is to use Thanks fot the tip! org-edit-special > org-edit-footnote-reference: it's clearly explained in the docstring, and I've been cloning buffers manually all my life (facepalm). Sorry for the noise, naturally the "standard" solution is preferable to my workaround. Best regards, Juan Manuel
Re: More robust CSL-JSON date parsing in oc-basic
Hello,
David Lukeš writes:
> -(car (split-string date "-")))
> +(replace-regexp-in-string
> ".*?\\([0-9]\\{4\\}\\).*" "\\1" date))
> +
[...]
> Let me know which of these changes -- if any -- seem acceptable, and
> whether they qualify as tinychange, and I'll happily submit a proper
> patch :)
All changes sound good. Please use `rx' for the regexp matching the
year.
This is a tinychange. I think this can be applied to the bugfix branch.
Thanks!
Regards,
--
Nicolas Goaziou
Re: [PATCH] ox-latex.el: Add a `t' value for `:float' in tables and figures
Hello, Juan Manuel Macías writes: > I am attaching an updated version of the patch, which retrieves the > `t' value for `:float' in tables and figures. The necessary information in > the Manual is also updated. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [PATCH] etc/ORG-NEWS: Add news items about new features in texinfo exporter
Hello, Jonas Bernoulli writes: > --- > etc/ORG-NEWS | 19 +++ Applied. Thank you. Regards, -- Nicolas Goaziou
Prompt when resolving clocks [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. Hello, I have a little problem concerning org-clock. When resolving clocks, either because of a long idleness or because of dangling clocks, there is a prompt to ask the user if they want to keep idle time, substract it, etc... But when another event than the response occurs (typically, I come back to my computer, I don't see the prompt and I click somewhere), an exception "Non-character input event" is raised, and the prompt disappear, making it impossible to resolve the clock later. When googling the error message I saw that the problem might be due to the use of the function read-char when prompting the user, which is indeed used in the function that resolve clocks. Is there a solution to wait for the user to answer the prompt, like a classical yes-no prompt? Best regards, Romeo Emacs : 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 Package: Org mode version 9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)
Prompt when resolving clocks [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. Hello, I have a little problem concerning org-clock. When resolving clocks, either because of a long idleness or because of dangling clocks, there is a prompt to ask the user if they want to keep idle time, substract it, etc... But when another event than the response occurs (typically, I come back to my computer, I don't see the prompt and I click somewhere), an exception "Non-character input event" is raised, and the prompt disappear, making it impossible to resolve the clock later. When googling the error message I saw that the problem might be due to the use of the function read-char when prompting the user, which is indeed used in the function that resolve clocks. Is there a solution to wait for the user to answer the prompt, like a classical yes-no prompt? Best regards, Romeo Emacs : 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 Package: Org mode version 9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)
Re: [WISH] Allow to hide the '*Org Help*' in 'org-goto' [9.5.2 (release_9.5.2-13-gdd6486 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Ihor Radchenko writes: > If you want to hide *Org Help* buffer, you can customise your > display-buffer-alist: > > [...] It works and TIL! Thank you, Ihor. Rudy -- "Strange as it may sound, the power of mathematics rests on its evasion of all unnecessary thought and on its wonderful saving of mental operations." -- Ernst Mach, 1838-1916 Rudolf Adamkovič [he/him] Studenohorská 25 84103 Bratislava Slovakia
Re: profiling latency in large org-mode buffers (under both main & org-fold feature)
Ihor Radchenko writes: > Samuel Wales writes: > >> i have been dealing with latency also, often in undo-tree. this might >> be a dumb suggestion, but is it related to org file size? my files >> have not really grown /that/ much but maybe you could bisect one. as >> opposed to config. > > I am wondering if many people in the list experience latency issues. FYI: I experience high latency when typing near in-text citations, such as [cite:@ganz+2013]. It got so bad that I converted all my files to hard-wrapped lines. After I did that, the Org mode became usable again, but it still lags visibly when typing near a citation. Rudy -- "'Contrariwise,' continued Tweedledee, 'if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic.'" -- Lewis Carroll, Through the Looking Glass, 1871/1872 Rudolf Adamkovič [he/him] Studenohorská 25 84103 Bratislava Slovakia
Re: Footnote tooltips (an attempt)
I answer myself to comment a couple more things on this question of footnotes and tooltips. I think my approach is quite poor, and also when it comes to files with many notes, it takes a long time to create or update the list of tooltips. So I think I'll give up on' footnote tooltips. If what it is about is being able to see the content of a footnote quickly, I have written this other simpler function, which displays the content of a footnote at point, in the echo area. Since `' (`display-local-help') is not very useful in a footnote reference, I recycle the shortcut for my function, if the context is a footnote reference. I share it here, in case it is useful to someone. ┌ │ (defun my-org-footnote-show-content () │ "Displays the content of a footnote at point, in the echo area" │ (interactive) │ (if (not (equal (org-element-type (org-element-context)) 'footnote-reference)) │ (error "Not on a footnote reference!") │ (let* ((elt (org-element-context)) │ (label (org-element-property :label elt)) │ (def (org-with-wide-buffer │(org-footnote-goto-definition label) │(let* ((e (org-element-context)) │ (from (org-element-property :contents-begin e)) │ (to (org-element-property :contents-end e))) │ (buffer-substring-no-properties from to) │ (message def │ │ (defun mi-display-local-help () │ (interactive) │ (if (and (derived-mode-p 'org-mode) │ (equal (org-element-type (org-element-context)) 'footnote-reference)) │ (my-org-footnote-show-content) │ (call-interactively 'display-local-help))) │ │ (global-set-key (kbd "C-h .") 'mi-display-local-help) └ Best regards, Juan Manuel Juan Manuel Macías writes: Hi all, > > I think sometimes it would be nice to have tooltips in the footnote > references, so I can see the contents of each footnote definition, > especially when I'm in a narrowed subtree; so I've tried to write some > code. I have achieved a "semi-automatic" solution. It doesn't work bad > at all, but I'm not entirely convinced either. With a minor mode the > `org-activate-footnote-links' function is overridden, and tooltips content > for all footnotes in the document are added or updated after a couple of > actions when you finish writing or editing a footnote: > `org-edit-src-exit' and `org-mark-ring-goto'. And that's where the > automatic part ends. Beyond that, tooltips must be updated/added by > calling the `my-org-fn-make-tooltips' function. > > Here is a short video demo: https://cloud.disroot.org/s/a4gejYc6PSwNWHY > > I attach the code of my poor man's footnote tooltips. Of course, any > comment and/or feedback is appreciated. > > Best regards, > > Juan Manuel > >
Footnote tooltips (an attempt)
I love it! I am going to read your code, Juan Manuel, I won't understand anything but that function is very interesting for me, since it could be used too with internal links, I suppose. Thanks
[PATCH] Fix date in org-latex--format-spec
Hi all, This is my first time posting here. Sorry in advance if I did something wrong. I tried customizing org-latex-title-command with a "%D" placeholder but the LaTeX was not compiling since this placeholder was being replaced by the string ((latex-fragment (:value \today :begin 1 :end 7 :post-blank 0 :parent #0))) I could not find this in previous issues and the code in the main branch still reproduced this error. The problem seems to be a missing call to org-export-data in the function org-latex--format-spec. Perhaps it is not necessary but I'm attaching the one-line patch that fixed things for me. From ddeaa68f540173a27bc0fddd6f8957b5e6af7ffe Mon Sep 17 00:00:00 2001 From: "Lucas V. R" Date: Tue, 22 Feb 2022 14:46:45 -0300 Subject: [PATCH] ox-latex: date should not be a property list --- lisp/ox-latex.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el index 5dda9b3ab..b181cadca 100644 --- a/lisp/ox-latex.el +++ b/lisp/ox-latex.el @@ -1630,7 +1630,7 @@ INFO is a plist used as a communication channel." (?c . ,(plist-get info :creator)) (?l . ,language) (?L . ,(capitalize language)) - (?D . ,(org-export-get-date info) + (?D . ,(org-export-data (org-export-get-date info) info) (defun org-latex--insert-compiler (info) "Insert LaTeX_compiler info into the document. -- 2.35.1
[BUG] Prompted to submit (unsure what happened) [9.5.2 (9.5.2-g072523 @ /Users/apc/.emacs.d/straight/build/org/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
I was simply entering an entry to my main bib file. I received an error message
and was asked to submit this report.
Thanks,
Alejandro
Emacs : GNU Emacs 28.0.90 (build 1, x86_64-apple-darwin19.6.0, NS
appkit-1894.60 Version 10.15.7 (Build 19H1419))
of 2021-12-14
Package: Org mode version 9.5.2 (9.5.2-g072523 @
/Users/apc/.emacs.d/straight/build/org/)
current state:
==
(setq
org-archive-location "~/org/agenda/archives/%s_archive.org::datetree/"
org-pomodoro-format "🍅:%s"
org-roam-db-location "/Users/apc/.emacs.d/var/org/org-roam.db"
org-link-elisp-confirm-function 'yes-or-no-p
org-agenda-skip-deadline-prewarning-if-scheduled 2
org-cite-insert-processor 'citar
org-after-refile-insert-hook '(org-gcal--refile-post)
org-roam-db-gc-threshold 80
org-bibtex-headline-format-function #[257 "\300%1\236A\207" [:title] 3 "\n\n(fn
ENTRY)"]
org-log-done 'time
org-pomodoro-long-break-sound
"/Users/apc/.emacs.d/straight/build/org-pomodoro/resources/bell_multiple.wav"
org-roam-mode-hook '(my/read-mode-indicator)
org-roam-dailies-capture-templates '(("d" "default" entry "* %?" :if-new
(file+head "%<%Y-%m-%d>.org" "#+title:
%<%Y-%m-%d>"))
)
org-agenda-custom-commands '(("d" "Default (ignore @sched and @hold)"
((agenda ""
((org-agenda-span 'day)
(org-super-agenda-groups
'((:name none :time-grid t)
(:name "To do" :and
(:not (:tag ("@hold")) :not (:tag
("@sched"))) :discard
(:anything t))
)
)
)
)
)
)
("z" "Work: focused"
((agenda ""
((org-agenda-span 'day)
(org-agenda-files `(,(concat my/agenda-dir
"/work.org")))
(org-super-agenda-groups
'((:name "First and foremost" :and (:tag
("@today") :priority "A"))
(:name "The rest" :tag ("@today") :discard
(:anything t)))
)
)
)
)
)
("p" "Planning view"
((agenda ""
((org-agenda-span 'day)
(org-super-agenda-groups
'((:name "Up next" :and (:todo "NEXT" :not
(:scheduled past)))
(:name "New today" :and
(:not (:todo ("WAIT" "KILL")) :not (:tag
("@sched")) :scheduled
today)
:deadline today)
(:name "In progress" :todo "STRT")
(:name "Overdue" :and
(:not (:todo ("DONE" "KILL" "WAIT")) :not
(:tag ("@sched"))
:deadline past)
)
(:name "Backlog" :and
(:not (:todo ("STRT" "DONE" "KILL"
"WAIT")) :not
(:tag ("@sched")) :scheduled past)
:discard (:anything t))
)
)
)
)
(alltodo ""
((org-agenda-overriding-header "")
(org-super-agenda-groups
`((:name "Refile" :and
(:not (:todo ("DONE" "KILL" "WAIT")) :tag
("refile") :not
(:tag ("read" "gkry")))
)
(:name "Next available actions" :and
(:todo "NEXT" :scheduled future) :and
(:todo "NEXT" :deadline future))
(:name "Coming u
Re: Question Regarding Creating HTML Style Buttons With Org Mode
Hey Juan, Just wanted to let you know that this works beautifully! I wish I was as good at Elisp to make this in the first place, but this really helps since I wanted to have some minimum overhead for 2 separate websites to be able to just write in Org Mode but include ideas for buttons, with classes and ID values. This helps a ton, thanks so much as it totally worked! :) Sincerely, Sam On Sun, Feb 20, 2022, at 7:38 PM, Samuel Banya wrote: > Thanks for this, will try this for my Emacs config. > > On Sat, Feb 19, 2022, at 4:51 AM, Juan Manuel Macías wrote: >> Juan Manuel Macías writes: >> >> > If you want to pass the class or id 'manually' to each link, and thus >> > have more control, you can evaluate this other version, where the class >> > or id would be added at the end of the link description, after (for >> > example) "!style": >> >> PS: Sorry, this is the correct code: >> >> (org-link-set-parameters "button" >>:face '(:foreground "green4" :underline t) >>:follow (lambda (path) (browse-url path)) >>:export (lambda (path desc backend) >> (when (eq backend 'html) >>(let ((style (if (string-match "\\(!style\\)\\(.+\\)" desc) >> (match-string 2 desc) >>"")) >> (desc (replace-regexp-in-string "\\(!style .+\\)" "" desc))) >> (format ">formaction=\"%s\">%s" style >>path desc) >> >> >> Example: >> >> [[button:http://www.sambanya.com/artgallery.html][Art Gallery Page Link >> !style class="mybutton"]] >> >> == HTML ==> >> >> >> > formaction="http://www.sambanya.com/artgallery.html";>Art Gallery Page Link >> >> >> >> >
Re: Footnote tooltips (an attempt)
Ypo writes: > I love it! > I am going to read your code, Juan Manuel, I won't understand anything > but that function is very interesting for me, since it could be used > too with internal links, I suppose. Org links already have tooltips out of the box. You can also display the tooltip in the echo area by pressing (`display-local-help'). If you want to try the code from my first post, please replace the `my-org-fn-make-tooltips' function with this new version, which is much simpler and doesn't have time-consuming issues to create or update tooltips. (However, I find the function I put in my second post more useful (for my use case: I don't use the mouse very much). #+begin_src emacs-lisp (defun my-org-fn-make-tooltips () (interactive) (org-element-map (org-element-parse-buffer) 'footnote-reference (lambda (ref) (let* ((label (org-element-property :label ref)) (label-from (org-element-property :begin ref)) (label-to (org-element-property :end ref)) (def (org-with-wide-buffer (org-footnote-goto-definition label) (let* ((e (org-element-context)) (from (org-element-property :contents-begin e)) (to (org-element-property :contents-end e))) (buffer-substring-no-properties from to (tooltip def)) (add-text-properties label-from label-to `(help-echo ,tooltip nil nil)) #+end_src Best regards, Juan Manuel
Re: Question Regarding Creating HTML Style Buttons With Org Mode
Hi Samuel, Samuel Banya writes: > Hey Juan, > > Just wanted to let you know that this works beautifully! > > I wish I was as good at Elisp to make this in the first place, but > this really helps since I wanted to have some minimum overhead for 2 > separate websites to be able to just write in Org Mode but include > ideas for buttons, with classes and ID values. > > This helps a ton, thanks so much as it totally worked! :) You're welcome! I'm glad it works and is useful to you. Org links have great potential :-) Best regards, Juan Manuel
Re: profiling latency in large org-mode buffers (under both main & org-fold feature)
Yes, it definitely seems to be related tofile size, which makes me think
that some kind of buffer parsing is the cause of the problem. I'll replay
in more detail to Ihor, down below!
On Mon, Feb 21, 2022 at 5:22 PM Samuel Wales wrote:
> i have been dealing with latency also, often in undo-tree. this might
> be a dumb suggestion, but is it related to org file size? my files
> have not really grown /that/ much but maybe you could bisect one. as
> opposed to config.
>
> i am not saying that your org files are too big. just that maybe it
> could lead to insights.
>
>
> On 2/21/22, Matt Price wrote:
> > I'm trying to figure out what causes high latency while typing in large
> > org-mode files. The issue is very clearly a result of my large config
> > file, but I'm not sure how to track it down with any precision.
> >
> > My main literate config file is ~/.emacs.d/emacs-init.org, currently
> 15000
> > lines, 260 src blocks.
> > If I create a ~minimal.el~ config like this:
> >
> > (let* ((all-paths
> > '("/home/matt/src/org-mode/emacs/site-lisp/org")))
> > (dolist (p all-paths)
> > (add-to-list 'load-path p)))
> >
> > (require 'org)
> > (find-file "~/.emacs.d/emacs-init.org")
> >
> > then I do not notice any latency while typing. If I run the profiler
> while
> > using the minimal config, the profile looks about like this at a high
> > level:
> >
> > 1397 71% - command-execute
> > 740 37% - funcall-interactively
> > 718 36% - org-self-insert-command
> > 686 34%+ org-element--cache-after-change
> > 10 0%+ org-fold-core--fix-folded-region
> >3 0%+ blink-paren-post-self-insert-function
> >2 0%+ jit-lock-after-change
> >1 0%
> > org-fold-check-before-invisible-edit--text-properties
> >9 0% + previous-line
> >6 0% + minibuffer-complete
> >3 0% + org-return
> >3 0% + execute-extended-command
> > 657 33% - byte-code
> > 657 33% - read-extended-command
> > 64 3%- completing-read-default
> > 14 0% + redisplay_internal (C function)
> >1 0% + timer-event-handler
> > 371 18% - redisplay_internal (C function)
> > 251 12% + jit-lock-function
> > 90 4% + assq
> >7 0% + substitute-command-keys
> >3 0% + eval
> > 125 6% + timer-event-handler
> > 69 3% + ...
> >
> > --
> > However, if I instead use my fairly extensive main config, latency is
> high
> > enough that there's a noticeable delay while typing ordinary words. I see
> > this regardless of whether I build from main or from Ihor's org-fold
> > feature branch on github. The profiler overview here is pretty different
> --
> > redisplay_internal takes a much higher percentage of the CPU requirement:
> >
> > 3170 56% - redisplay_internal (C function)
> > 693 12% - substitute-command-keys
> > 417 7% + #
> > 59 1% + assq
> > 49 0% + org-in-subtree-not-table-p
> > 36 0% + tab-bar-make-keymap
> > 35 0%and
> > 24 0% + not
> > 16 0%org-at-table-p
> > 13 0% + jit-lock-function
> >8 0%keymap-canonicalize
> >7 0% + #
> >4 0% + funcall
> >4 0%display-graphic-p
> >3 0% + #
> >3 0%file-readable-p
> >3 0% + table--probe-cell
> >3 0%table--row-column-insertion-point-p
> > 1486 26% - command-execute
> > 1200 21% - byte-code
> > 1200 21% - read-extended-command
> > 1200 21%- completing-read-default
> > 1200 21% - apply
> > 1200 21% - vertico--advice
> > 475 8% + #
> >
> > --
> > I've almost never used the profiler and am not quite sure how I should
> > proceed to debug this. I realize I can comment out parts of the config
> one
> > at a time, but that is not so easy for me to do in my current setup, and
> I
> > suppose there are likely to be multiple contributing causes, which I may
> > not really notice except in the aggregate.
> >
> > If anyone has suggestions, I would love to hear them!
> >
> > Thanks,
> >
> > Matt
> >
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>
Re: profiling latency in large org-mode buffers (under both main & org-fold feature)
sorry everyone, I accidentally sent this to Kaushal this morning, and then took quite a while to get back to a computer after he let me know my mistake! On Tue, Feb 22, 2022 at 10:12 AM Matt Price wrote: > > On Tue, Feb 22, 2022 at 12:45 AM Kaushal Modi > wrote: > >> >> >> On Tue, Feb 22, 2022, 12:34 AM Ihor Radchenko wrote: >> >>> >>> I am wondering if many people in the list experience latency issues. >>> Maybe we can organise an online meeting (jitsi or BBB) and collect the >>> common causes/ do online interactive debugging? >>> >> >> +1 >> >> I have seen few people see this issue on the ox-hugo issue tracker: >> https://github.com/kaushalmodi/ox-hugo/discussions/551#discussioncomment-2104352 >> > > > I htink it's a great idea, Ihor! > > Meanwhile, I have a profile report. I had a little trouble getting the > slowness to return (of course) but, subjectively, it seemed to get worse > (subjectively slower, and the laptop fan started up b/c of high cpu usage) > when I created and entered a src block. Apologies for the long paste: > >45707 70% - redisplay_internal (C function) > 8468 13% - substitute-command-keys > 6111 9% - # > 943 1%- kill-buffer > 708 1% - replace-buffer-in-windows > 614 0% - unrecord-window-buffer > 515 0% - assq-delete-all > 142 0% assoc-delete-all >3 0% delete-char > 8060 12% - assq > 2598 4% - org-context > 15 0% org-inside-LaTeX-fragment-p > 12 0%- org-in-src-block-p > 12 0% - org-element-at-point >9 0% - org-element--cache-verify-element >9 0% org-element--parse-to >3 0%org-element--parse-to >8 0%- org-at-timestamp-p >8 0% org-in-regexp > 642 0% + tab-bar-make-keymap > 309 0% + and > 270 0% + org-in-subtree-not-table-p > 196 0% + not > 163 0% + jit-lock-function > 115 0% + org-entry-get > 96 0%keymap-canonicalize > 56 0%org-at-table-p > 52 0% + # > 48 0% + # > 43 0%table--row-column-insertion-point-p > 29 0%org-inside-LaTeX-fragment-p > 27 0% + menu-bar-positive-p > 26 0% + eval > 24 0%file-readable-p > 21 0% + funcall > 16 0% + imenu-update-menubar > 14 0% + vc-menu-map-filter > 13 0% + table--probe-cell > 12 0% + or > 11 0% + let > 11 0% + org-at-timestamp-p > 10 0% + flycheck-overlays-at >7 0%undo-tree-update-menu-bar >6 0% + require >6 0% + > emojify-update-visible-emojis-background-after-window-scroll >6 0%kill-this-buffer-enabled-p >4 0%mode-line-default-help-echo >3 0% + null > 9192 14% - ... > 9172 14%Automatic GC > 20 0% - kill-visual-line > 20 0% - kill-region > 20 0%- filter-buffer-substring > 20 0% - org-fold-core--buffer-substring-filter > 20 0% - buffer-substring--filter > 20 0% - # > 20 0%- apply > 20 0% - # F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_18> > 20 0% - # > 20 0% - apply > 20 0%- # > 20 0% - # > 20 0% - # > 20 0% - apply > 20 0%- # > 20 0% + delete-and-extract-region > 7847 12% - command-execute > 5749 8% - funcall-interactively > 2963 4% + org-self-insert-command > 2186 3% + org-cycle > 148 0% + corfu-insert > 146 0% + execute-extended-command > 121 0% + org-return > 32 0% + # > 26 0% + # > 24 0% + mwim-beginning > 19 0% + org-delete-backward-char > 19 0% + org-kill-line >9 0% + # >6 0% + file-notify-handle-event > 2095 3% + byte-code > 1359 2% + timer-event-handler > 375 0% + org-appear--post-cmd > 160 0% + corfu--post-command > 61 0% + org-fragtog--post-cmd > 14 0% + emojify-update-visible-emojis-background-after-command > 11 0% guide-key/close-guide-buffer >7 0% + flycheck-perform-deferred-syntax-check >7 0% + flycheck-maybe-display-error-at-point-soon >6 0% undo-auto--add-boundary >6 0% + corfu--auto-post-command >4 0% flycheck-error-list-update-source >
Re: [BUG] Prompted to submit (unsure what happened) [9.5.2 (9.5.2-g072523 @ /Users/apc/.emacs.d/straight/build/org/)]
Alejandro Pérez Carballo writes: > I was simply entering an entry to my main bib file. I received an error > message and was asked to submit this report. Thanks for the report! Do I understand correctly that you got: 1. An error message 2. A warning popup Did it happen when you were _not_ in Org buffer and you did not use minibuffer completion? Do you recall the error/warning text? Best, Ihor
Re: profiling latency in large org-mode buffers (under both main & org-fold feature)
Matt Price writes: >>20128 80% - redisplay_internal (C function) >> 7142 28% - assq >> 908 3% - org-context Note that org-context is an obsolete function. Do you directly call it in your config? Or do you use a third-party package calling org-context? Best, Ihor
Re: profiling latency in large org-mode buffers (under both main & org-fold feature)
Matt Price writes: > Yes, it definitely seems to be related tofile size, which makes me think > that some kind of buffer parsing is the cause of the problem. Parsing would show up in the profiler report in such scenario. It is not the case though. The problem might be invisible text (it would cause redisplay become slow), but 15k lines is relatively small - it should not cause redisplay issues according to my experience. Just to be sure, I would try to check performance in a completely unfolded buffer. Best, Ihor
