Re: [BUG] `org-html-head-include-scripts' default value should be `t' but it's nil instead [9.7-pre (release_9.6.20-1267-gb0c3c9 @ /home/nick/src/emacs/org/org-mode/lisp/)]

2024-03-21 Thread Nick Dokos
Ihor Radchenko writes: > Nick Dokos writes: > >> If you load `ox-html`, the default value of >> `org-html-head-include-scripts` is nil, despite the defcustom: >> >> (defcustom org-html-head-include-scripts t ... > > Are you sure? What I am seeing in lisp/ox-html.el is > > (defcustom

[bug] Smart quotes: confusion of apostrophe with second level quotes

2024-03-21 Thread Juan Manuel Macías
Hi, I don't know if this is a known issue, but I haven't been able to find any mention of it. I think this is partly because in English it can go perfectly unnoticed, since for English the values of secondary-closing and apostrophe are identical: (secondary-closing :utf-8 "’" :html "" :latex

Re: [BUG] `org-html-head-include-scripts' default value should be `t' but it's nil instead [9.7-pre (release_9.6.20-1267-gb0c3c9 @ /home/nick/src/emacs/org/org-mode/lisp/)]

2024-03-21 Thread Ihor Radchenko
Nick Dokos writes: > If you load `ox-html`, the default value of > `org-html-head-include-scripts` is nil, despite the defcustom: > > (defcustom org-html-head-include-scripts t ... Are you sure? What I am seeing in lisp/ox-html.el is (defcustom org-html-head-include-scripts nil "Non-nil

[BUG] `org-html-head-include-scripts' default value should be `t' but it's nil instead [9.7-pre (release_9.6.20-1267-gb0c3c9 @ /home/nick/src/emacs/org/org-mode/lisp/)]

2024-03-21 Thread Nick Dokos
If you load `ox-html`, the default value of `org-html-head-include-scripts` is nil, despite the defcustom: (defcustom org-html-head-include-scripts t ... The reason is that `org-expot-define-backend`, which is called

Re: [BUG] Improve error message "org-back-to-heading: Before first headline at position 1" [9.6.8 (release_9.6.8-3-g21171d @/usr/local/share/emacs/29.1.50/lisp/org/)]

2024-03-21 Thread Ihor Radchenko
[ Adding Org mailing list back to CC ] c.bu...@posteo.jp writes: > Am 21.03.2024 11:46 schrieb Ihor Radchenko: >> Are you saying that the above example will trigger an error on the >> latest main when you try to attach a file? > > No, only the version (29.something) I reported this bug. > >

[FR] Add customization for default answers to `org-attach-set/unset-directory' prompt (was: Org-attach risks)

2024-03-21 Thread Ihor Radchenko
[ Adding Org mailing list back to CC. Please use "Reply all" to keep the discussion public ] Kepa writes: > I don't know enough to upload a patch, I barely know what is a patch... No problem. Then, I will turn this discussion into a feature request. It may be eventually implemented by other

Re: [BUG] org-agenda-clock-cancel does not update agenda buffer [9.6.15 (release_9.6.15 @ /nix/store/5hl68vr85cagmwaycqy652r2g2isjcyq-emacs-29.2/share/emacs/29.2/lisp/org/)]

2024-03-21 Thread Ihor Radchenko
z...@bcc32.com writes: > After clocking into an entry (org-agenda-clock-in) from an agenda > buffer (such as org-agenda-list), the entry is highlighted with a face > (org-agenda-clocking). When the entry is no longer clocked in, e.g., > by clocking out or marking it DONE, the org-agenda-clocking

Re: Pending contents in org documents (Re: Asynchronous blocks for everything (was Re: ...))

2024-03-21 Thread Ihor Radchenko
Bruno Barbier writes: >> I feel that org-pending-penreg (org-pending-) is >> redundant. Maybe better use org-pending-region? > > PENREG is the name of the structure; the "org-pending" is the > mandatory library prefix; this mechanically gives the name. A PENDREG > object is not a "region" in

Re: [BUG] Improve error message "org-back-to-heading: Before first headline at position 1" [9.6.8 (release_9.6.8-3-g21171d @/usr/local/share/emacs/29.1.50/lisp/org/)]

2024-03-21 Thread Ihor Radchenko
c.bu...@posteo.jp writes: >> I believe that this problem have been fixed on main. > > Do you mean the message was improved or the message do not appear > anymore? Can you link please to the sources file where I can see the > message. Let's see if I understand it. :D The error message should

Re: [BUG] Improve error message "org-back-to-heading: Before first headline at position 1" [9.6.8 (release_9.6.8-3-g21171d @/usr/local/share/emacs/29.1.50/lisp/org/)]

2024-03-21 Thread c . buhtz
Dear Ihor, thanks for reply. Am 21.03.2024 11:02 schrieb Ihor Radchenko: "org-back-to-heading: Before first headline at position 1 in buffer..." I believe that this problem have been fixed on main. Do you mean the message was improved or the message do not appear anymore? Can you link

inline-special-block: export rules (was: `:export' attribute?: Re: Experimental public branch for inline special blocks)

2024-03-21 Thread Juan Manuel Macías
Max Nikulin writes: > I am afraid that :export will cause confusion with :exports for source > code blocks. Its name differs by just "s" but possible values have > nothing common. I agree. At the moment two alternative names come to mind: :backends or :export-rules > Another issue is more

Re: Pending contents in org documents (Re: Asynchronous blocks for everything (was Re: ...))

2024-03-21 Thread Bruno Barbier
Ihor Radchenko writes: Thanks for your review Ihor! > Bruno Barbier writes: > >> I rewrote the API, rename many things, moved the code around and >> sorted everything into heading/subheading sections. This is hopefully >> less confusing and a lot simpler; and the documentation hopefully >>

Re: [BUG] Improve error message "org-back-to-heading: Before first headline at position 1" [9.6.8 (release_9.6.8-3-g21171d @/usr/local/share/emacs/29.1.50/lisp/org/)]

2024-03-21 Thread Ihor Radchenko
c.bu...@posteo.jp writes: > This is not a support question about how to solve a problem or the error > message I do report here. It is a request to improve that error message > to help users understand the real problem and find a solution by their > own. > > I get the this error message in

[BUG] Improve error message "org-back-to-heading: Before first headline at position 1" [9.6.8 (release_9.6.8-3-g21171d @/usr/local/share/emacs/29.1.50/lisp/org/)]

2024-03-21 Thread c . buhtz
Hello, using the first time this Emacs in build bug report thing. But have to send the mail via copy & paste because the bug reporter didn't work out of the box. The "From" field is not valid. Modified it manually in the buffer. But didn't work. Emacs tried to use STARTTLS with posteo.de:25

Re: Error with org-persist

2024-03-21 Thread Ihor Radchenko
Al Oomens writes: > (file-writable-p "c:/Users/aloom/My Drive/home/.emacs.d/org-persist") - > returns "t" > ... >> Evaluating (file-writable-p "c:/Users/aloom/My Drive/home/.emacs.d/") >> returns "nil". The problem is that you do not seem to have write access to create files in