From: Noboru Ota <email@example.com> To: firstname.lastname@example.org Subject: Introducing Org-transclusion Date: Sat, 30 Oct 2021 13:51:25 +0200 [thread overview] Message-ID: <email@example.com> (raw) Hi everyone, This is my first post to Org mailing list. I would like to introduce an add-on package I have been developing for about one year and ask for discussion / advice. The package is named "Org-transclusion", and is available on GitHub at https://github.com/nobiot/org-transclusion. Simply put, it lets you insert a copy of text content via a file link or ID link within an Org file. The GitHub repository contains links short video presentations and documentation in detail. Judging from feedback from users, it is used for academic writing such as PhD dissertation, technical writing with source code embedded as transclusions, and note taking. I am not a programmer by trade; I originally developed it to help me write a book. It's a very thin volume on a business topic, which has nothing to do with Emacs or Org mode. Is this type of add-on packages worth considering for inclusion into Org? I am asking this question without knowing the practice of how these things are considered in this mailing list; apologies if I am missing the context. The feedback I have received includes requests for me to put this discussion forward in this mailing list, so some people find it useful if Org-transclusion were part of Org. I am in the process of assigning the copyright to FSF (my email request has not been responded to, so I might need to do it again). I would be also fine to put Org-transclusion on GNU ELPA (or NonGNU ELPA) and see it to mature before this discussion can be had. Of course, I would also understand if there is an outright decision to not consider my request at this point in time. I will appreciate your comments and discussions. Thank you. Noboru
next reply other threads:[~2021-10-30 11:52 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-30 11:51 Noboru Ota [this message] 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 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 \ --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).