Re: bug#68687: [PATCH] Use text/org media type

2024-01-25 Thread Eli Zaretskii
> Cc: 68...@debbugs.gnu.org, Max Nikulin , > emacs-orgmode@gnu.org > From: Ihor Radchenko > Date: Thu, 25 Jan 2024 23:43:14 + > > However, AFAIU, text/org will fall into "standards tree" in IANA media > type specification, which means that it MUST be registered, as described > in

Re: bug#68687: [PATCH] Use text/org media type

2024-01-25 Thread Eli Zaretskii
> Cc: emacs-orgmode@gnu.org > From: Stefan Kangas > Date: Thu, 25 Jan 2024 15:10:27 -0800 > > Max Nikulin writes: > > > Hi, > > > > I suggest to make the media type used for Org mode files consistent with > > the one used by XDG https://gitlab.freedesktop.org/xdg/shared-mime-info > > Currently

bug#52587: bug#59141: 28.1.90; Face :extend when all the line but trailing \n is invisible

2024-01-25 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: 59...@debbugs.gnu.org > Date: Thu, 25 Jan 2024 22:53:45 + > > Kévin Le Gouguec writes: > > >> I do not see anything wrong on the Org side. > >> Maybe Emacs should not apply :extent t attribute to the newline when the > >> text in fontified line is hidden? > > >

Re: Inconsistent handling of multi-line properties

2024-01-25 Thread Jack Kamm
Ihor Radchenko writes: > Thanks! > You can replace Maintainer: line in ox-icalendar.el with your name. Done. > Sure. > I checked my records and found one outstanding issue related to > ox-icalendar - > https://list.orgmode.org/orgmode/20211230225919.1a660...@hsu-hh.de/ > > The patch proposed

On org-syntax and IANA MIME type registration

2024-01-25 Thread Timothy
Hi All, With the recent mention of the text/org mime type, and registering it as an IANA in-tree MIME type in particular, I’d like to draw attention to this part of : > When review is required, a change request may be denied if it renders

Re: bug#68687: [PATCH] Use text/org media type

2024-01-25 Thread Ihor Radchenko
Stefan Kangas writes: >> I suggest to make the media type used for Org mode files consistent with >> the one used by XDG https://gitlab.freedesktop.org/xdg/shared-mime-info >> Currently Emacs has text/x-org, however "x-" prefix is not recommended >> by IANA any more, see

Re: bug#68687: [PATCH] Use text/org media type

2024-01-25 Thread Stefan Kangas
Max Nikulin writes: > Hi, > > I suggest to make the media type used for Org mode files consistent with > the one used by XDG https://gitlab.freedesktop.org/xdg/shared-mime-info > Currently Emacs has text/x-org, however "x-" prefix is not recommended > by IANA any more, see

Re: [PATCH] Add buffer-local setting to request specific ESS process/session name (was: [PATCH] Set Python shell in Org edit buffer)

2024-01-25 Thread Ihor Radchenko
"Sparapani, Rodney" writes: > This last remark below can’t possibly be true. Because I did not intend to > trigger > a release, ESS 24.01.0 was not initially tagged. However, after I received > that email > from ELPA, it was a fait accompli. So I fixed some cosmetic issues and > tagged it

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

2024-01-25 Thread Ihor Radchenko
Sławomir Grochowski writes: > I propose to move the section "Checkboxes". > From "5 TODO Items -> 5.6 Checkboxes" > To: "2 Document Structure -> 2.6 Plain Lists -> 2.6.1 Checkboxes" > > Because checkbox can only exist in a plain list, as a plain list feature. > So the section should be under

Re: [BUG] beamer export

2024-01-25 Thread Leo Butler
On Wed, Jan 24 2024, Ihor Radchenko wrote: > Leo Butler writes: > >> I think the documentation and example needs to be corrected. I have >> attached a patch. > > Thanks! Applied. > https://git.sr.ht/~bzg/worg/commit/aedea59f Attached is a second patch to de-lint the ox-beamer tutorial. Leo

Re: [BUG] conda doesn't work in ob-shell sessions

2024-01-25 Thread Ihor Radchenko
Matt writes: > > What about the attached second version of the patch? > > I spent way too long trying to test it but I'm not sure I applied the patch > correctly. > > I did the following, then realized that the patch I applied undid > changes (I assume) from a previous patch and so it must

Re: New try at multi-lingual export to latex/pdf using pdflatex and babel

2024-01-25 Thread Pedro A. Aranda
Hi I've been reading a bit. What I propose is an alternative way to handle all the tricky parts of font and character handling with fontspec in lualatex and xetex. This package restricts the use of the ams* packages to pdflatex, because fontenc handles that internally and produces package

Re: [BUG] beamer export

2024-01-25 Thread Leo Butler
On Wed, Jan 24 2024, Ihor Radchenko wrote: > Leo Butler writes: > 1. ox-latex export bug for src blocks containing direct LaTeX when org-latex-src-block-backend is set to its default 'verbatim value >>> >>> This appears to be Beamer-specific problem with verbatim environments: >>>

Re: [PATCH] Add buffer-local setting to request specific ESS process/session name (was: [PATCH] Set Python shell in Org edit buffer)

2024-01-25 Thread Sparapani, Rodney
Hi Idor: I have never had much success with either MELPA or ELPA. Something about my TLS setup that I have not figured how to fix. But, I did receive an email that we are available at ELPA too (however, I can’t test the veracity of that myself). See the ESS-help thread here….

Re: [PATCH] Add buffer-local setting to request specific ESS process/session name (was: [PATCH] Set Python shell in Org edit buffer)

2024-01-25 Thread Sparapani, Rodney
Hi Idor: This last remark below can’t possibly be true. Because I did not intend to trigger a release, ESS 24.01.0 was not initially tagged. However, after I received that email from ELPA, it was a fait accompli. So I fixed some cosmetic issues and tagged it post-haste, i.e., ELPA’s

Re: [PATCH] Add buffer-local setting to request specific ESS process/session name (was: [PATCH] Set Python shell in Org edit buffer)

2024-01-25 Thread Ihor Radchenko
"Sparapani, Rodney" writes: > I have never had much success with either MELPA or ELPA. Something about > my TLS setup that I have not figured how to fix. But, I did receive an email > that > we are available at ELPA too (however, I can’t test the veracity of that > myself). > See the

Re: New try at multi-lingual export to latex/pdf using pdflatex and babel

2024-01-25 Thread Ihor Radchenko
"Pedro A. Aranda" writes: > As stated, this was only a PoC. If you find it useful, I would give it a > go in the free window. I understand. My question is to clarify how useful it is. Because I am not deeply familiar with how fontenc works for non-English languages, it is hard to judge how

Re: Inconsistent handling of multi-line properties

2024-01-25 Thread Ihor Radchenko
Jack Kamm writes: >>> 3. Change ox-icalendar to consider :LOCATION+ properties and merge them >>>during export. >> >> I went with this approach. >> See the attached tentative patch. > > Thanks Ihor -- this is a nice improvement for ox-icalendar. > > My only suggestion would be to add this

Re: [PATCH] Add buffer-local setting to request specific ESS process/session name (was: [PATCH] Set Python shell in Org edit buffer)

2024-01-25 Thread Ihor Radchenko
Martin Maechler writes: > > Thank you! May I know which version of ESS will have this > > commit? > > The Melpa version that was just released, does. Noted. I did not know that ESS is distributed via MELPA. I am wondering why not ELPA/non-GNU ELPA - ELPA is built-in and users can

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

2024-01-25 Thread Sławomir Grochowski
Dear All, Dear All, I propose to move the section "Checkboxes". >From "5 TODO Items -> 5.6 Checkboxes" To: "2 Document Structure -> 2.6 Plain Lists -> 2.6.1 Checkboxes" Because checkbox can only exist in a plain list, as a plain list feature. So the section should be under 'Plain Lists' heading

[BUG] ox-latex produces broken references to src code listings without caption (was: [BUG] org-lint tells to move #+name to wrong place in results block)

2024-01-25 Thread Ihor Radchenko
gerard.vermeu...@posteo.net writes: > I have found that CAPTION keywords in the "name-result-example" in the > manual are essential to produce correct links. It should not be essential. What you demonstrated is two bugs in Org mode. > In case the relevant blocks have e.g. ":exports both", Org