Org mode version 9.7-pre (9.7-pre-n/a-g356072 @ /home/dinko/.config/emacs/elpaca/builds/org/); table alignment broken when using links in cells

2024-02-28 Thread Kostadin Ninev
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 Your bug report will be posted to the Org mailing list.

emacs-orgmode@gnu.org Subject: Org mode version 9.7-pre (9.7-pre-n/a-g356072; org-table-to-lisp breaks table alignment when using links

2024-02-28 Thread Kostadin Ninev
After installing latest org from git, table alignment is broken for me in tables where some of the cells contain links for example: | a| b | |--+---| | [[c][c]] | d | Shows like this: | a| b | |--+---| | c | d | Unless I M-x org-toggle-link-display, tested

Re: [proof of concept] inline language blocks

2024-02-28 Thread Max Nikulin
Juan Manuel, I am not against optional arguments. The idea is to make the feature more flexible and convenient for domain-specific documents. I did not use square brackets in my example to concentrate on the use case of concise and clear markup. On 29/02/2024 06:42, Juan Manuel Macías

Things got very slow: profiler output

2024-02-28 Thread William Denton
I rebuilt Org and Emacs from the development trees and something is wrong, because some Org files I use regularly have become incredibly slow to use. I rarely use the profiler and don't know what to make of what it says, but I opened a file and ran it while I moved around and expanded and

Re: [proof of concept] inline language blocks

2024-02-28 Thread Juan Manuel Macías
Max Nikulin writes: > #+options: custom-object(:type la :latex_element foreignlanguage > :latex_pre "{latin}") mmm, I see it as not very flexible and perhaps too complicated for the user. My idea with the concept of inline-special-block is that it is like the inline version of its older

Re: Radio links work only in small numbers

2024-02-28 Thread Noboru Ota
gh). Do you have any indication on how many would be maximum? Thank you. --- [1]: You can also see the benchmark results in the file. https://git.sr.ht/~nobiot/org-radio-links-patch-20240228/tree/main/item/5000-terms.org – nobiot

Re: [PATCH] doc/org-manual.org (Checkboxes): move section 'Checkboxes' from 'TODO Items' to 'Plain Lists'

2024-02-28 Thread Matt
On Wed, 28 Feb 2024 13:17:54 +0100 Ihor Radchenko wrote --- > Matt m...@excalamus.com> writes: > > > I had responded in favor here: > > https://list.orgmode.org/18d4cf138a6.10fb9c6702382826.5023996590743168...@excalamus.com/ > > Did I miss something... Yes, it appears there's

Re: [PATCH] ob-tangle: Add flag to optionally remove files before writing

2024-02-28 Thread Olivier Lischer
Ihor Radchenko writes: > > Thanks for the update! > Unfortunately, your patch has unbalanced parenthesis and will not work. > I have modified your patch to make things work and to make it conform to > Elisp code conventions. I also removed spurious change in the existing > variable. > > See the

Re: [proof of concept] inline language blocks

2024-02-28 Thread Max Nikulin
On 28/02/2024 20:15, Juan Manuel Macías wrote: #+options: inline-special-block-aliases:(("latin" :lang "la" :color blue :prelatex "\\itshape " :html "style=\"font-style:italic;\"")) This is an example of Latin text: &_[@latin@]{lorem ipsum dolor sit amet}. It is more verbose than {lorem

Re: Radio links work only in small numbers

2024-02-28 Thread Ihor Radchenko
ttps://git.sr.ht/~nobiot/org-radio-links-patch-20240228/tree > > The two files, `500-terms.org` and `5000-terms.org`, contain 500 > and 5000 radio targets respectively. > > Both files have two H1 headlines "Definitions" and "Body text". Once >

Re: Radio links work only in small numbers

2024-02-28 Thread nobiot
iot/org-radio-links-patch-20240228/tree The two files, `500-terms.org` and `5000-terms.org`, contain 500 and 5000 radio targets respectively. Both files have two H1 headlines "Definitions" and "Body text". Once you open the file, call `M-x org-update-radio-targ

Re: [proof of concept] inline language blocks

2024-02-28 Thread Juan Manuel Macías
Max Nikulin writes: > Juan Manuel your ":fr{}" and similar objects is a domain-specific > language that is quite different from a generic element proposed by > Samuel. Do you think it makes sense to modify your inline special > block patch to allow creation of concise DSL? > > Juan Manuel Macías.

Re: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number

2024-02-28 Thread Ihor Radchenko
Bastien Guerry writes: > Ihor Radchenko writes: > >> Bastien, may you please check FSF records? > > Done, and confirmed things are in order. Welcome! Recorded. https://git.sr.ht/~bzg/worg/commit/4760468a -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number

2024-02-28 Thread Bastien Guerry
Ihor Radchenko writes: > Bastien, may you please check FSF records? Done, and confirmed things are in order. Welcome! -- Bastien Guerry

Re: [PATCH] doc/org-manual.org (Checkboxes): move section 'Checkboxes' from 'TODO Items' to 'Plain Lists'

2024-02-28 Thread Ihor Radchenko
Matt writes: > I had responded in favor here: > https://list.orgmode.org/18d4cf138a6.10fb9c6702382826.5023996590743168...@excalamus.com/ Did I miss something, or did you not provided arguments /why/ the section should be moved? I need to understand what kind of improvement it would provide to

Re: org-mode: example blocks are no longer syntax highlighted in emacs

2024-02-28 Thread Ihor Radchenko
Max Nikulin writes: >>> After upgrading to emacs 29.2 and org 9.7, my example blocks are no longer >>> syntax highlighted in emacs. >> >> Yet, there is no reason to remote it. >> I recovered example block fontification on main. > > At least some people are against the feature: > >

Re: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number

2024-02-28 Thread Ihor Radchenko
Tim Ruffing writes: > On Tue, 2024-02-27 at 12:49 +, Ihor Radchenko wrote: >> However, your total contributions are now at the limit we can legally >> accept without FSF copyright assignment. >> Would you consider doing copyright paperwork as described in >>

Re: [PATCH] org-babel-demarcate-block: split using element API

2024-02-28 Thread Ihor Radchenko
gerard.vermeu...@posteo.net writes: >> You may wrap `org-indent-block' into `condition-case' to catch >> user-errors. > > The caveat is not a real constraint, since Org has limited support for > source block editing in an Org mode buffer when an > `org-babel-edit-prep:' function signals an

Re: [PATCH] ob-tangle: Add flag to optionally remove files before writing

2024-02-28 Thread Ihor Radchenko
[ Moving the discussion back to public in Org mailing list ] Olivier Lischer writes: > I hope that this time I have changed the patch the way you wanted it. > If anything is still wrong, I am happy to improve it. Thanks for the update! Unfortunately, your patch has unbalanced parenthesis and

Re: Provide sane default for the @direntry

2024-02-28 Thread Ihor Radchenko
Stefan Monnier writes: > When exporting to Texinfo, the patch below makes it easier to generate > a good `@direntry` by using sane defaults. > For most files, you'll just need > > #+TEXINFO_DIR_CATEGORY: {my-category} > > I believe it also makes it a bit harder to shoot oneself in the foot

Re: [proof of concept] inline language blocks

2024-02-28 Thread Max Nikulin
On 22/02/2024 06:02, Juan Manuel Macías wrote: Samuel Wales writes: :fr{some text in French} being expressed as $[lang :fr "bonjour"] To expand a little more... Another problem I see in your example is nesting. In my proposal, the blocks can be nested: :fr{text in French and :it{text in

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

2024-02-28 Thread Bruno Barbier
Hi Matt, Matt writes: > On Sat, 24 Feb 2024 17:42:54 +0100 Bruno Barbier > > > I'll publish a branch soon; it will be a major rewrite of my current > > proposal. It should be less confusing and, I hope, address some of your > > comments. > > > > Thanks again for your questions

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

2024-02-28 Thread Bruno Barbier
Hi, Bruno Barbier writes: > Hi Matt, [...] >> Since this thread is dedicated to blocking, let me share my thoughts on that >> subject. > > I guess I should start a new thread then :) I finally got a new version. I've renamed the proposed feature "pending contents", that is, some contents