Re: [PATCH] org-manual.org: Update links to MathJax docs
Max Nikulin writes: > Let's fix at least the link. Old one gives 404 error. Thanks! > Scheme is not changed to https: since the site prefers http: > > curl -I https://docs.mathjax.org/ > HTTP/2 302 It is not erring on my side. Maybe they changed something since last year? -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: double digit list entries malformatted header
Rob Sargent writes: > Works on LibreOffice(7.3)/Ubuntu(22.04), not on Word(2016)/Windows10 I was able to export the attached file and open it without noticeable issues using LibreOffice. If LibreOffice can open the generated document just fine, it is likely the limitation of Microsoft Word not being able to open odt file properly. Given the proprietary nature of Microsoft Word, finding the reasons why Word cannot open the valid odt file is hard. I suggest opening the file using LibreOffice on Windows. If you cannot install LibreOffice on your Windows machine, try converting org file or the odt file to docx using Pandoc. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: double digit list entries malformatted header
On 8/20/22 05:54, Ihor Radchenko wrote: Rob Sargent writes: Emacs 27.2, Org 9.4.4, Windows 10 When I have a list of ** headings with more than nine entries on export to ODT the tenth and subsequent are broken: The first letter of the heading is fully to the right hand margin and the remainder is on the next line. There's no problem with latex/pdf nor htlm output. Could you please provide an example Org file to demonstrate the problem? Seehttps://orgmode.org/manual/Feedback.html Works on LibreOffice(7.3)/Ubuntu(22.04), not on Word(2016)/Windows10 t.org Description: Lotus Organizer
Re: Org donations page statement: explain where the donations are coming to? (was: Fwd: Re: Typo in info pages)
Ihor Radchenko writes: > ed...@openmail.cc writes: > >> On 2022-08-20 13:46, Ihor Radchenko wrote: >>> So, what I call "team" is equivalent to donations to the overall >>> development. These donations (note that it's not really much money) are >>> simply an extra motivation for Org committers. Org project has no real >>> expenses. >> >> Yep, I saw the amounts. I mean 1 € per week!... > > To be even more precise, the amounts in https://liberapay.com/org-mode > are mostly because we created the page recently. A more appropriate > number is in https://liberapay.com/bzg/, which was the donation page > that had been used since years back. I forgot PayPal and https://github.com/sponsors/bzg (They were alternative options until https://list.orgmode.org/871qzqg81c@gnu.org/)
Re: Bug? org-id-find not finding some IDs
Ihor Radchenko writes: > I suggest to bind org-id-track-globally to nil file-locally in that > backup file. Thanks for the suggestion. I tried it out, and it initially seemed to work, but eventually the backup file ended up in org-id-files. It seems like there is more than one way that files may be added to org-id-files, and not all will respect a locally-set org-id-track-globally. However, I found another solution: we can use write-region to append the entry to org-caldav-backup.org, without opening it. Then this avoids the problem in normal usage of org-caldav: org-caldav-backup.org won't end up in org-id-files, since it won't be open in Emacs. I've updated my PR to org-caldav accordingly. > If necessary, we may add an extra customization like > org-id-exclude-files to explicitly exclude files from ID tracking. I think this would be nice, but it isn't necessary for the time being, since I found another solution for org-caldav, as described above.
Org donations page statement: explain where the donations are coming to? (was: Fwd: Re: Typo in info pages)
ed...@openmail.cc writes: > On 2022-08-20 13:46, Ihor Radchenko wrote: >> So, what I call "team" is equivalent to donations to the overall >> development. These donations (note that it's not really much money) are >> simply an extra motivation for Org committers. Org project has no real >> expenses. > > Yep, I saw the amounts. I mean 1 € per week!... To be even more precise, the amounts in https://liberapay.com/org-mode are mostly because we created the page recently. A more appropriate number is in https://liberapay.com/bzg/, which was the donation page that had been used since years back. > I didn't want to disrespect you in any way. I am still glad that I made > the contribution, and I know that money is not the motivation for the > good development (I tried to be generous, nevertheless). However, may be > it would be wise to add that link > (https://list.orgmode.org/87iloyyd1y.fsf@localhost/) next to the > donations link so that people understand about the context beforehand (I > would have liked to read the thread). Also, I appreciate the implied > transparency when you sent me the link. (That is what I think that > people will like. It is also important to educate each other). > > In any case, it was just a recommendation, not a complaint :) . Cheers! I am CCing Bastien. Your suggestion sounds reasonable. In addition to the previously discussed JS disclaimer, we can explain that the donations are used as extra encouragement for significant Org contributors and link the ML discussion. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Fwd: Re: Typo in info pages
On 2022-08-20 13:46, Ihor Radchenko wrote: So, what I call "team" is equivalent to donations to the overall development. These donations (note that it's not really much money) are simply an extra motivation for Org committers. Org project has no real expenses. Yep, I saw the amounts. I mean 1 € per week!... I didn't want to disrespect you in any way. I am still glad that I made the contribution, and I know that money is not the motivation for the good development (I tried to be generous, nevertheless). However, may be it would be wise to add that link (https://list.orgmode.org/87iloyyd1y.fsf@localhost/) next to the donations link so that people understand about the context beforehand (I would have liked to read the thread). Also, I appreciate the implied transparency when you sent me the link. (That is what I think that people will like. It is also important to educate each other). In any case, it was just a recommendation, not a complaint :) . Cheers! - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!
Re: Fwd: Re: Typo in info pages
ed...@openmail.cc writes: > On 2022-08-20 07:12, Ihor Radchenko wrote: >> ed...@openmail.cc writes: >> --- snip 8< --- >> Note that https://liberapay.com/org-mode is a "team" page aiming to >> divide the donations across the interested Org contributors (see >> https://list.orgmode.org/87iloyyd1y.fsf@localhost/). However, >> cryptocurrencies are not supported by Liberapay. We cannot utilize >> Liberapay for this purpose. >> --- snip 8< --- > > I think that a disclaimer or note like that should be added to > Support Org development at https://liberapay.com/org-mode, > > Otherwise, it's misleading. My intention was to donate to the overall > development of Org, not just a "team". Could you please elaborate about what you mean by "overall development"? Maybe we have a misunderstanding here. Let ma clarify about our donation page: - Org repository is hosted on savannah as a GNU project. It's free. - Org webpage is hosted on a donated server space. It's also free. - Org development is done by volunteers. It's also free - nobody is expected to be paid for Org development beforehand. - For a long time, the donations were directed to the main Org maintainer (Bastien). AFAIU, it was because people wanted to donate, and we simply got a token donation target. - Recently, we made an alternative donation scheme where multiple Org contributors can share the donations. We have invited all the major contributors. Some accepted. Some plain did not want donations. Some are yet to reply. So, what I call "team" is equivalent to donations to the overall development. These donations (note that it's not really much money) are simply an extra motivation for Org committers. Org project has no real expenses. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Fwd: Re: Typo in info pages
On 2022-08-20 07:12, Ihor Radchenko wrote: ed...@openmail.cc writes: --- snip 8< --- Note that https://liberapay.com/org-mode is a "team" page aiming to divide the donations across the interested Org contributors (see https://list.orgmode.org/87iloyyd1y.fsf@localhost/). However, cryptocurrencies are not supported by Liberapay. We cannot utilize Liberapay for this purpose. --- snip 8< --- I think that a disclaimer or note like that should be added to Support Org development at https://liberapay.com/org-mode, Otherwise, it's misleading. My intention was to donate to the overall development of Org, not just a "team". This would ensure: https://list.orgmode.org/87iloyyd1y.fsf@localhost/ without creating confusion among donors on where to donate. - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!
Re: desktop-restore-eager doesn't seem to affect desktop-lazy-idle-delay
Oh, right, sorry. El 20/08/2022 a las 13:52, Ihor Radchenko escribió: Ypo writes: - Expected behavior: (desktop-restore-eager t) should “override” (desktop-lazy-idle-delay), making this variable equivalent to (desktop-lazy-idle-delay nil). Did you mean to send this to Emacs debbugs? This is Org mailing list.
Re: double digit list entries malformatted header
Rob Sargent writes: > Emacs 27.2, Org 9.4.4, Windows 10 > > When I have a list of ** headings with more than nine entries on export > to ODT the tenth and subsequent are broken: The first letter of the > heading is fully to the right hand margin and the remainder is on the > next line. There's no problem with latex/pdf nor htlm output. Could you please provide an example Org file to demonstrate the problem? See https://orgmode.org/manual/Feedback.html -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: desktop-restore-eager doesn't seem to affect desktop-lazy-idle-delay
Ypo writes: > - Expected behavior: > > (desktop-restore-eager t) should “override” (desktop-lazy-idle-delay), > making this variable equivalent to (desktop-lazy-idle-delay nil). Did you mean to send this to Emacs debbugs? This is Org mailing list. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Bug: [org-contrib][org-depend] function 'position' is not defined [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
Damien Couroussé writes: > I use org-depend, which produces the following error message : > > > ┌ > │ org-depend-trigger-todo: Symbol’s function definition is void: position > └ Fixed. Note that the changes are not currently reflected in non-GNU ELPA. You need to use the repository source at https://git.sr.ht/~bzg/org-contrib Also, be aware about org-contrib is barely maintained. This particular fix is very easy, but more involved issues will not be prioritized. See https://list.orgmode.org/87pmy89fqu@gnu.org/ and the readme in https://git.sr.ht/~bzg/org-contrib -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
double digit list entries malformatted header
Emacs 27.2, Org 9.4.4, Windows 10 When I have a list of ** headings with more than nine entries on export to ODT the tenth and subsequent are broken: The first letter of the heading is fully to the right hand margin and the remainder is on the next line. There's no problem with latex/pdf nor htlm output.
Bug: [org-contrib][org-depend] function 'position' is not defined [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
hello, I use org-depend, which produces the following error message : ┌ │ org-depend-trigger-todo: Symbol’s function definition is void: position └ I think that this is happening here: [[file:lisp/org-depend.el::(pos (position this-item items :key #'first))]] I can reproduce the problem with the 'advanced triggering example' as published here: https://orgmode.org/worg/org-contrib/org-depend.html#org858993c I could not find a suitable replacement for the function 'position' due to my limited mastering of elisp. Any help greatly appreciated! Your bug report will be posted to the Org mailing list. Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0) of 2021-03-28, modified by Debian Package: Org mode version 9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)
table alignment tags in Org export
Hello, Trying to export a table with alignment tags, e.g. #+caption: left, center and right aligned columns | | | | | a |b |c | | aa | | | In, for example, HTML or ODT output, the columns are aligned according to the tags in the first row. If exporting to Org (org-org-export-as-org), the tags disappear - i.e. the table is as-was, minus the first row. Is there a way to retain the alignment information when re-exporting to Org? cheers alex
desktop-restore-eager doesn't seem to affect desktop-lazy-idle-delay
Not sure if a bug: - My desktop is creating buffers lazily, with idle delay = 200 seconds. Variables: (desktop-lazy-idle-delay 200) (desktop-restore-eager t) - Expected behavior: (desktop-restore-eager t) should “override” (desktop-lazy-idle-delay), making this variable equivalent to (desktop-lazy-idle-delay nil).
Re: [Feature Request] Create an org-md-toplevel-hlevel variable to allow users to set the level of top level headings in markdown export
"Rohit Patnaik" writes: > Hello, > > I've been exporting several of my org-mode notes to markdown recently, and > I've been running into an issue where I've had to manually adjust the level > of the top level headings in my exported notes because the wiki system I'm > importing the notes to reserves h1 (i.e. #) for page titles, using h2s (i.e. > ##) for sections within the page itself. > > I noticed that ox-html.el has a org-html-toplevel-hlevel variable, which > allows the user to set the heading level of top-level headings within the > exported content. Would there be any problems with implementing a similar > variable (e.g. org-md-toplevel-hlevel) to allow the user to set the heading > level of top level headings within exported markdown content? Sounds reasonable. I do not see any issue with this approach. Just be careful to compute the level early before we decide the deeply-nested headline style (org-md-headline-style). > It looks like it would be a small change, and I'd be happy to implement it > myself, but I thought I'd run it by the list to see if there were any major > issues that might arise from making this change. This contribution will be welcome. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: table alignment tags in Org export
Alex Fenton writes: > Trying to export a table with alignment tags, e.g. > > > #+caption: left-, centre- and right aligned columns > | | | | > | a | b | c | > | aa | | | > > In, for example, HTML or ODT output, the columns are aligned according > to the tags in the first row. > > If exporting to Org (org-org-export-as-org), the tags disappear - i.e. > the table is as-was, minus the first row. Confirmed. > Is there a way to retain the alignment information when re-exporting to > Org? - either a function or some setting somewhere No. Currently, ox-org.el currently disregards table cell alignment and width. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [PATCH v2] ol-info: Define :insert-description function
Max Nikulin writes:
> On 19/08/2022 11:28, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>
>>> +(defun org-info--link-file-node (path)
>>> + "Extract file name and node from info link PATH.
>>> +
>>> +Return cons consisting of file name and node name or \"Top\" if node
>>> +part is not specified. Components may be separated by \":\" or by \"#\"."
>>
>> It looks like the docstring does not match what the function actually
>> returns.
>
> It returns a cons, doesn't it? Is it confusing that separator for
> components is related to the argument?
It is confusing that cons consist of _file name_ and node name.
However, the function may return non-file as car of the cons.
>>> + (if (not path)
>>> + '("dir" . "Top")
>>
>> "dir" is not a file. Also, it is not very clear what "dir" is referring
>> to. Maybe you can add a comment pointing to `org-info-other-documents'?
>
> Try M-x info RET when you do not have *info* buffer and you get "(dir)
> Top" node. It is the directory of info files. If you run "info" without
> argument in shell you will get the same.
Sure. I know this. But see the above. Not every person reading the Org
source is familiar with info conventions.
>>> +(string-match "\\`\\([^#:]*\\)\\(?:[#:]:?\\(.*\\)\\)?\\'" path)
>>> +(let* ((node (match-string 2 path))
>>> + ;; `string-trim' modifies match
>>
>> Here and is several other places, including docstrings, please make sure
>> that the sentences end with "." and are separated with " ".
>
> It was supposed to be a brief phrase rather than complete sentence.
What about other places like the docstring?
Or
+ ;; Unlike (info "dir"), "info dir" shell command opens "(coreutils)dir
invocation"
(missing ".")
probably some more places.
(Of course, this is minor, and I could do it myself; just pointed this
together with other more important comments)
>>> + (cons
>>> + ;; Fallback to "org" is an arbirtrary choice
>>> + ;; and added because "(dir)filename" does not work as "filename".
>>
>> Should this be documented? Or at least mentioned that the behaviour is
>> undefined. And if it is undefined you should not test it in the tests.
>
> The purpose of test is to check that it does not signal some obscure
> error. I am unsure how to handle corner cases, so I am open to
> suggestions. Some considerations
> - `org-info--link-file-node' may return nil when link path is incomplete
> or some value that may help to avoid error handling code paths in callers.
> - does not look like a valid link but it may be handled like
> shell "info" command without argument, so I chose "(dir)" node. Elisp
> (info) without arguments however may display existing buffer.
> - certainly should be handled as (info "(dir)")
> - is invalid. Maybe (info "elisp") should be used instead.
> - I am unsure in my choice to open (info "(org) Tables").
> Maybe it is better to treat it as "(dir) Tables" and so as "(dir) Top"
> node since "(dir) Top" is quite reasonable for with empty path.
I am not sure what would be the best here. The main point - whatever
fallback mechanism you choose, please document it in the docstring.
In general, I favour having a fallback more compared to not having any.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
Re: Suspected bug: '#+STARTUP: indent' messes up inlinetasks' tag alignment
alain.coch...@unistra.fr writes: > > Can you try the attached patch? > > The problem is solved if I use emacs 28.1 (thanks a lot), but not for > emacs 27.2... Applied onto main via ccca8549a. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=ccca8549a2fe3158ad41603eedc8ba427a240df5 I have tested the patch on emacs-27.2, and it works just fine. Can you please check again using the newest development version of Org? > PS: I have had only a very limited and ancient experience with > patches, so it was not immediate for me to try your patch. While > working on it, I noticed that the section of the manual > >* Feedback:: Bug reports, ideas, patches, etc. > > does not even contain the word 'patch'. So I was thinking it might be > a good idea to say a few words in that section about what patches are > and how to apply them. Applying patches is out of scope of the manual. Next time, you can just ask to provide an alternative way of testing. I can then just upload the patched version to an alternative repository. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
http: links in the manual
On 20/08/2022 12:51, Ihor Radchenko wrote: Note that we still have a number of http links in the manual. One may want to fix them. One may got no response trying to fix a link. Max Nikulin to emacs-orgmode. [PATCH] org-manual.org: Update links to MathJax docs. Sun, 3 Oct 2021 23:17:46 +0700. https://list.orgmode.org/sjcl3b$gsr$1...@ciao.gmane.io In the particular case of docs.mathjax.org I am unsure if mild preference of http: over https: is not a mistake in the server configuration. I do not mind "https:" there, any variant is better than the old broken link.
Re: Fwd: Re: Typo in info pages
ed...@openmail.cc writes: > On 2022-08-19 05:39, Ihor Radchenko wrote: >> Support Org development at https://liberapay.com/org-mode, > > This is great! You should add cryptocurrencies there :) . Cryptocurrencies are tricky. See https://list.orgmode.org/87mte8xdse.fsf@localhost/ Note that https://liberapay.com/org-mode is a "team" page aiming to divide the donations across the interested Org contributors (see https://list.orgmode.org/87iloyyd1y.fsf@localhost/). However, cryptocurrencies are not supported by Liberapay. We cannot utilize Liberapay for this purpose. The only option is individual Org contributors sharing their cryprowallets individually. This can be done inside Liberapay personal pages, but no single Org contributor accepting the donations have a cryptowallet. This may change in future if we add more people though. In the past discussions people suggested to use MyMonero (limited to Monero) and GNU Taler (not really usable yet) cryprowallets as the ones complaint with FSF ethics. However, it is unclear if MyMonery is going to be a practical option given the huge number of available kinds of crypto. To summarize, not every Org contributor is willing or legally able to use crypto. Also, it is unclear which cryptocurrency is the best to accept. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [BUG] Fix for inlinetask visibility cycling causes infinite loop for "degenerate" inlinetasks
Anders Johansson writes: >> I am unable to reproduce on main and on bugfix. >> What is your Org version (M-x org-version)? > > Sorry I didn’t bother to reproduce with emacs -Q. I stepped through with > edebug and thought the problem was quite clear that way. I have reproduced > with Emacs -q (+ loading org from git) now and the problem persists on my > side, using a sample file consisting of just a heading with one degenerate > inlinetask below, as posted before: Thanks for checking again! I forgot to load org-inlinetask when checking, which is why I did not observe the problem. Fixed on main now via a0b8b7303. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=a0b8b7303b9683fae4503c57ee8ae191cb89a297 Best, Ihor
Re: [PATCH v3] Show org file title in org-clock clocktable
Duy Nguyen writes: > Thanks for letting me know. The reason I chose that method is because the > org-macro-templates are not updated immediately after I change the title > and save the file. However, I think I found a solution using > org-macro-initialize-templates and org-macro-templates. Please see the > attached patch. Hope this is OK, otherwise please let me know how to > improve. Thanks for the update! Applied onto main via 2cc2d8f1f with amendments. I fixed on double space " " between sentences, removed autoload cookie (that function is not used outside org-clock), and altered the docstring making the first line a single sentence and clarifying about the return value a bit. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2cc2d8f1f6265d12c92b734931f2e3e417276b05 -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [BUG] org-insert-heading-respect-content doesn't always insert TODO heading [9.5.4 (release_9.5.4-17-g6e991f @ /usr/local/Cellar/emacs-plus@29/29.0.50/share/emacs/29.0.50/lisp/org/)]
Roman Rudakov writes: > Steps to reproduce: > 1. Create an org heading and set state to something but TODO or DONE > (for example PROGRESS). > 2. Call the function org-insert-todo-heading-respect-content > ... > I noticed that internally this function calls org-insert-todo-heading > and pass arguments in a wrong order: > > Actual function call: > > (org-insert-todo-heading force-state '(4)) > > Should be: > > (org-insert-todo-heading '(4)) force-state) Thanks for reporting and pinpointing the source of the bug! Fixed on main via a1af06d64. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=a1af06d643d662f8c04e7c59d10efc45108a9528 -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
