From: Noboru Ota <email@example.com> To: Ihor Radchenko <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Introducing Org-transclusion Date: Wed, 10 Nov 2021 22:09:22 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <87zgqed6to.fsf@localhost> Ihor Radchenko <email@example.com> writes: > Try to open the attached file and run M-x org-transclusion-add-all Thank you. I see. Not even org-transclusion-add-all but a single add function takes a bit of time. If I may ask some questions and for some advice: 1. I see it as an issue rather of recursive transclusions (transclusions inside a transclusion) than of overlay. Do you agree? 2. If it is a recursion, I would like to somehow avoid it altogether by "skipping it" before going into a loop. I thought I had done part of it; apparently, it's not enough. Do you have some suggestions how other programs might deal with this type of issues? I feel that many pieces of software have done so... 3. If it is an overlay issue, do you have suggestions what sort of methods are available within Emacs? 4. This file does not seem realistic for me as a user who use Emacs for writing -- but I see this sort of testing can be useful for avoiding potential issues. How important do you think it is to tackle this type of "hypothetical" issues as a package developer? It's a question of priority for me. I do not feel that I have sufficient knowledge and skill set to tackle it right now; if the priority is not so high, I think I would leave it (for now, but this "for now" would be for a long time). If priority is high, I would need to ask for some help with even framing the problem so that we can somehow tackle it. Thank you. Noboru
next prev parent reply other threads:[~2021-11-10 21:10 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-30 11:51 Noboru Ota 2021-10-30 12:31 ` Juan Manuel Macías 2021-11-01 9:17 ` Noboru Ota 2021-10-30 13:59 ` Ihor Radchenko 2021-11-01 9:11 ` Noboru Ota 2021-11-01 13:24 ` Ihor Radchenko 2021-11-06 10:43 ` Noboru Ota 2021-11-08 15:07 ` Ihor Radchenko 2021-11-10 21:09 ` Noboru Ota [this message] 2021-11-14 8:22 ` Ihor Radchenko 2021-11-14 9:35 ` Ihor Radchenko 2021-11-01 20:07 ` Thomas Paulsen 2021-11-01 21:01 ` Noboru Ota 2021-11-02 5:17 ` Timothy 2021-11-05 19:53 ` Noboru Ota 2021-11-05 21:56 ` Tim Cross 2021-11-05 23:20 ` Timothy 2021-11-06 10:14 ` Noboru Ota 2021-11-06 10:22 ` Tim Cross 2021-11-06 11:49 ` Noboru Ota 2021-11-05 17:11 ` Uwe Brauer 2021-11-05 19:24 ` Noboru Ota 2021-11-05 20:15 ` Uwe Brauer 2021-11-05 23:02 ` Noboru Ota 2021-11-06 14:01 ` Uwe Brauer 2021-11-06 14:25 ` Ihor Radchenko 2021-11-06 14:54 ` Noboru Ota 2021-11-06 15:49 ` Uwe Brauer 2021-11-07 7:34 ` Ihor Radchenko 2021-11-07 8:07 ` Uwe Brauer 2021-11-07 8:30 ` Ihor Radchenko 2021-11-07 13:25 ` Uwe Brauer 2021-11-07 13:41 ` Ihor Radchenko 2021-11-07 13:56 ` Uwe Brauer 2021-11-05 19:59 ` Noboru Ota 2021-11-05 20:13 ` Uwe Brauer
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Introducing Org-transclusion' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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).