emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jorge P. de Morais Neto <jorge+list@disr.it>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-export-with-broken-links not respected for (org-icalendar-combine-agenda-files t) [9.6.9 ( @ /home/jorge/.config/emacs/elpa/org-9.6.9/)]
Date: Thu, 14 Sep 2023 10:14:26 -0300	[thread overview]
Message-ID: <87cyykaoct.fsf@disr.it> (raw)
In-Reply-To: <87r0n6jwld.fsf@localhost>

Hi!  I reply below:

Em [2023-09-10 dom 07:50:22+0000], Ihor Radchenko escreveu:

> One possible way to fix the confusion could be adding a new
> `org-export-async-preserve-global-state' variable.  When non-nil, we
> will transfer global state in addition to the buffer-locals.  But I
> would like to hear other opinions first, if there are any.

In the meantime, or *in addition* to other changes, we could ameliorate
the problem with documentation.  Probably mention the potentially
confusing behavior in the Org manual, and maybe also in the docstring of
`org-icalendar-combine-agenda-files' and other functions that invoke
async export.


- I am Brazilian.  I hope my English is correct and I welcome feedback.
- Free Software Supporter: https://www.fsf.org/free-software-supporter
- https://www.fsf.org/ "Free Software Foundation: working together for free software"
- Many people hate injustice but few check the facts; this causes more
  injustice.  Ask me about <https://stallmansupport.org>

  reply	other threads:[~2023-09-14 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 21:45 [BUG] org-export-with-broken-links not respected for (org-icalendar-combine-agenda-files t) [9.6.9 ( @ /home/jorge/.config/emacs/elpa/org-9.6.9/)] Jorge P. de Morais Neto
2023-09-10  7:50 ` Ihor Radchenko
2023-09-14 13:14   ` Jorge P. de Morais Neto [this message]
2023-09-15  9:13     ` Ihor Radchenko
2023-09-15 10:23       ` Jorge P. de Morais Neto
2023-09-15 10:36         ` Ihor Radchenko
2023-10-22  9:22           ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cyykaoct.fsf@disr.it \
    --to=jorge+list@disr.it \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).