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

> From: Richard Stallman > Cc: e...@gnu.org, maniku...@gmail.com, 68...@debbugs.gnu.org, > emacs-orgmode@gnu.org, stefankan...@gmail.com > Date: Thu, 01 Feb 2024 22:40:06 -0500 > > > It may or may not depending on user customization `mm-inline-media-tests'. > > Just like with

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

Max Nikulin writes: > On 01/02/2024 03:00, Stefan Kangas wrote: >> Max Nikulin writes: >>> +++ b/lisp/net/mailcap.el >>> @@ -989,7 +989,8 @@ (defvar mailcap-mime-extensions >>> (".jpe" . "image/jpeg") >>> (".jpeg" . "image/jpeg") >>> (".webp" . "image/webp") >>> -

[BUG] Newlines after links are fontified with the org-link face after an incremental search

Hello everyone, I've noticed a potential regression in the way that org-mode fontifies links in the latest git main branch version of org-mode. When the user conducts an incremental search that matches a link that runs to the end of the line, for some reason the =org-link= face is extended to

Re: bug#68687: Org mode code evaluation

On 02/02/2024 10:38, Richard Stallman wrote: > I did not imply that Org mode is safe. I directly said that there are > security issues and that they are known. Could you plesae post a pointer to a desciption of them? I would strongly prefer to move discussion of Org security to a

Re: Should org-link-parser add type "file" when link has no "file:" prefix?

February 1, 2024 at 4:23 AM, "Ihor Radchenko" wrote: > > jos...@ushin.org writes: > > > > > > > > > > > What we can do then is pass an extra argument to :follow function - > > > > > the > > > > > > > > link object. That way, :follow function can get all the information > > > it > > >

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

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > It may or may not depending on user customization `mm-inline-media-tests'. >

Re: bug#68687: Org mode code evaluation (was: bug#68687: [PATCH] Use text/org media type)

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > I did not imply that Org mode is safe. I directly said that there are >

Re: org-icalendar export problems

I got org updated, following Ihor's instructions: Org mode version 9.7-pre (release_N/A-N/A-afc529 @ ./org-9.7pre0.20240130.161905/) If I were able to fulfill a good process to export from agenda to icalendar, maybe we could share an easy process, useful for a lot of users that miss a good

[BUG] org-insert-heading changed behavior with Emacs 29.2 [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.2/lisp/org/)]

Hi All, I recently upgraded to Emacs 29.2 (from 29.1) and observed that `org-insert-heading-respect-content' has changed behavior with regard to how it handles blank lines at the end of the entry at which the command was called. Consider the following document (with "|" representing point):

Re: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)

Am Donnerstag, dem 01. Februar 2024 schrieb Juan Manuel Macías: > How about using dedicated keywords? Something like: > > #+FN_AUTHOR: footnote text > #+FN_TITLE: footnote text For reference -- I do not know if this prompted the discussion here -- just a few days ago I asked about footnotes in

Re: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)

Ihor Radchenko writes: > Max Nikulin writes: > >> On 26/01/2024 19:53, Ihor Radchenko wrote: >>> So, I am leaning towards reverting that commit - that will allow things >>> like >>> >>> #+TITLE: This is a test title[fn::This is test] >> >> I hope, document metadata will be generated with

Re: [PATCH v2] org-id: allow using parent's existing id in links to headlines

On Thu, 1 Feb 2024, at 12:13 PM, Ihor Radchenko wrote: > The patch does not apply onto the latest main. May you please update it? I have rebased onto the latest main. It changes quickly! (there were no conflicts during the rebase, which I'd have thought would mean the patches shouldn't be a

Re: RFI: LaTeX - AUTO for \usepackage{inputenc}

Yes, indeed... Thx for pointing out /PA On Thu, 1 Feb 2024 at 17:31, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > some days ago I sent a proof-of-concept for customising the coding for > the > > inputenc package. Before continuing with this, I'd like to know what > other

Re: RFI: LaTeX - AUTO for \usepackage{inputenc}

Pedro Andres Aranda Gutierrez writes: > some days ago I sent a proof-of-concept for customising the coding for the > inputenc package. Before continuing with this, I'd like to know what other > people think and/or need. Did you mean fontenc? -- Ihor Radchenko // yantar92, Org mode

Re: [PATCH] doc/org-manual.org: Checkboxes, add checkbox states examples

Matt writes: > > In fact, Checkboxes section of the manual was previously under Document > > structure. This was changed in release_4.45. > > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6a9c670d > > I checked the mailing list around that time for any issues that might

Re: [PATCH] doc/org-manual.org: Checkboxes, add checkbox states examples

Sławomir Grochowski writes: > I noticed in my patch that I moved the description ("The ‘[2/4]’ and > ‘[1/3]’ in") of an example. > And it should be just below the example. > > So I'm sending a fixup! patch to fix this. > It's my first fixup! patch so I hope this is the right procedure ;)

Re: Suggested manual changes - section 7.2 Special Properties

Tommy Kelly writes: > It’s here: > https://www.reddit.com/r/orgmode/s/3viPfF78Lr > > In a nutshell, I was trying to understand how to have one of the columns in > column mode be the creation date of each headline. I thought that because I > almost always insert a clock entry when I create (using

Re: Suggested manual changes - section 7.2 Special Properties

Tommy Kelly writes: > After figuring out, with help on Reddit (ht: Adam), some nuances > affecting timestamps, column > mode, and the Special Properties TIMESTAMP, and TIMESTAMP_IA, I think > the following > modifications to section 7.2 (Special Properties) of the manual would > be worthwhile. >

Re: [BUG] beamer export

Leo Butler writes: > The docstring of `org-latex-classes' says: > > The HEADER-STRING is the header that will be inserted into the > LaTeX file. It should contain the \documentclass macro, and > anything else that is needed for this setup. > > From that, I

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/build/org/)]

Hi Ihor, Ihor Radchenko writes: > > This is most likely something about my current system setup - I can > reproduce with other Org mode and Emacs versions. But I have no clue > what is the cause. I'm getting the same as you with your MWE. The tag, used by ob-comint async, is:

[DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) (was: [BUG] Footnotes in section titles)

Max Nikulin writes: > On 26/01/2024 19:53, Ihor Radchenko wrote: >> So, I am leaning towards reverting that commit - that will allow things >> like >> >> #+TITLE: This is a test title[fn::This is test] > > I hope, document metadata will be generated with stripped footnotes. This is a good

Re: Should org-link-parser add type "file" when link has no "file:" prefix?

jos...@ushin.org writes: >> > > What we can do then is pass an extra argument to :follow function - the >> > > link object. That way, :follow function can get all the information it >> > > needs. >> > > >> > >> > I like this idea! Would this change break existing :follow functions >> >

Re: [PATCH v2] doc/org-manual.org (Summary): Clarify the Org markup is human-readable

Ihor Radchenko writes: > Thanks for the comments! > I am attaching the next iteration of the patch. Applied, onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=788af5675 -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [PATCH v2] org-id: allow using parent's existing id in links to headlines

The patch does not apply onto the latest main. May you please update it?

[BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

This is a followup for another bug report https://orgmode.org/list/87plxg95u4@gmail.com Using the MWE from that report I am seeing a different bug and it is not very clear for me what is causing it. 1. When I create /tmp/bug.org with the following contents: #+begin_src python :dir

Re: Async Python src block behavior with :dir header property

Jack Kamm writes: >> Confirmed. > > Does the attached patch fix the issue? > > It seems the problem is with async sessions generally (not just > ob-python), and happens because `org-babel-comint-async-filter' does not > set `default-directory' before calling `org-babel-insert-result', unlike >

Re: [PATCH] Silently remove lockfiles from org-agenda-files

Joseph Turner writes: >> I feel slightly reluctant about this patch: >> ... > > Yes, I think you're right. Thanks for your caution :) Closing. Canceled. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at

Re: [PATCH] lisp/ox-latex.el: improve org-latex-toc-command docstring

gerard.vermeu...@posteo.net writes: > I have read the docstring of `org-latex-toc-command' too literally > to discover that specifying anything else than "toc:nil" works. > ... > The attached patch contains a proposal for improvement. > Subject: [PATCH] lisp/ox-latex.el: improve

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

On 01/02/2024 03:00, Stefan Kangas wrote: Max Nikulin writes: +++ b/lisp/net/mailcap.el @@ -989,7 +989,8 @@ (defvar mailcap-mime-extensions (".jpe" . "image/jpeg") (".jpeg" . "image/jpeg") (".webp" . "image/webp") -(".org" . "text/x-org")) +;; May be overridden

Re: Async Python src block behavior with :dir header property

Jack Kamm writes: > > Does the attached patch fix the issue? > I briefly tested it here and it works. Thanks for taking a look into it. -- Nasser Alkmim +43 677 6408 9171