From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id 2N/5NLNVJ2PADgEAbAwnHQ (envelope-from ) for ; Sun, 18 Sep 2022 19:30:27 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id mLvlNLNVJ2MOZgEAauVa8A (envelope-from ) for ; Sun, 18 Sep 2022 19:30:27 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 3AA32D49B for ; Sun, 18 Sep 2022 19:30:27 +0200 (CEST) Received: from localhost ([::1]:54944 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oZy7e-00062y-F8 for larch@yhetil.org; Sun, 18 Sep 2022 13:30:26 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37416) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZy6v-00061c-49; Sun, 18 Sep 2022 13:29:41 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:57162) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZy6u-0004V4-Rc; Sun, 18 Sep 2022 13:29:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:Subject:To:From:in-reply-to: references; bh=c8WdQ+pYa3TWNB9Tr+420wTGxcHU8/NQjKFXSkrpQIs=; b=fXYKrSJd+oLmbD vtVH73xakoxa92FDaSIPeyBoK9JoxBuN/v4cr2M5cv2smxd+dPgqfNfNPrPLDWzmHapHoYlrLHbi1 1ovIlqTy/BvJxoF9tnj+Mfo5lAkvrwBRuYrSTFooH65pv9dbx3yff9O21JXY0bbyJ46QtjgrDY8K/ U5Dlxhmk4EQpe27TSfmUhpdkzahV7EtYWsp6Ug5PhmdCuyNfDq+tzJ8RuiqVTbg6Fyou2KJc3n5c/ 8u5CCEz+yItFqw8pAlCv7y4UFlr8aeUZCPo1QIu2pjzU+6Pn/5hSeXxSC2fVeGcwlfQSdzoTPQ1Ms IU+pVpd2VA989Nr3ipVA==; Received: from bras-base-toroon473mw-grc-20-174-89-30-44.dsl.bell.ca ([174.89.30.44]:60392 helo=langa) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZy6u-0001Dm-Aa; Sun, 18 Sep 2022 13:29:40 -0400 From: Amin Bandali To: emacsconf-discuss@gnu.org, emacs-devel@gnu.org, emacs-orgmode@gnu.org, emacs-tangents@gnu.org Cc: emacsconf-org@gnu.org Subject: [ANN] EmacsConf 2022 Second Call for Participation (extended until Sep 30) Date: Sun, 18 Sep 2022 13:29:38 -0400 Message-ID: <87wna0wpz1.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: emacsconf-discuss@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1663522227; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=c8WdQ+pYa3TWNB9Tr+420wTGxcHU8/NQjKFXSkrpQIs=; b=o/8WkNQ/e37OeHEj741KKTff8983OIWbhQdT83PN3VDNGnDiXCN/60TEpj8V331UGel1HP lA+EtNEFYjX22RnEPOG3I6FM3jZA2rQUiRQQ1wRrt4ejlW7oMXxt5Mmt91/47X44sHn9h2 4/9aN8od7X0UkFulXpMqfeKshGqRgpJCg1ncKZ5ZkItAkwjIJvM5XL/jgXyWUjVPnleTV3 mEc588TTU062oIcPu3ivfNXiQEcD1MSPJ1SB5UcjgCZvToVKK6EVlhrGi5c/JfXVRZ20+O daVKDm0mznhprqOxodenv82tzJV5YgCgrMO/44aBHLlltf9Jv70m7uFaI2uXcg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1663522227; a=rsa-sha256; cv=none; b=QVxIa8d0V9o7wZWG8qmw1axdXVS0HfKA0b+4LrwuDlJtDV81Ff/XM2mXb8D02xTaJYIMeb i7tOxY0hDXHDQYMuRoZAt1lkELhTyiCu+P7PC7LC/tnkagjz/CcURLjwzQcbZ+wvWEjBff t6bTnnCaVsmRBu2Jwv4JHzyTIeGrgIgloDsex9GmdVzM1fhSBp3DXkIGskFaNC+fzGN8rn pZ8+Pf02j6Y6BxSEA3e78sC+EC51MDPKkUvaqRAq/RBJQiLNVVUYbzwd7kZZRRqRR5xEAU SNyV6Z8Xnnwhr/jHhA+aQTD3iuZ99c1+mrdq4uSirwiQA3uhgMPqDPJ6YAnYuQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=fXYKrSJd; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -5.04 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=fXYKrSJd; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 3AA32D49B X-Spam-Score: -5.04 X-Migadu-Scanner: scn1.migadu.com X-TUID: 491rlYsiz5Om --=-=-= Content-Type: text/plain Dear fellow Emacsians, This is the second and final Call for Participation for EmacsConf 2022 now extended until September 30, and the conference itself planned for December 3 and 4 (Sat-Sun). Please see the CFP below for details on how to send in your proposal(s), or chat with us about them and about other ways of participating and volunteering around EmacsConf via our main IRC channel #emacsconf on the Libera.Chat network. If you're considering submitting a proposal but think the remaining time may not be enough, please reach out to me off-list as soon as possible so we could work something out. I'll close this portion of the email with a thank you to all of the folks who have submitted session proposals or expressed interest in volunteering with EmacsConf. We look forward to reading and reviewing all of your messages and proposals, and getting back to you about them and about the next steps soon. :-) Best, amin P.S. please direct any replies to this post either to myself or to the emacsconf-discuss list, so as to help avoid generating extra off-topic chatter in the other lists cc'd on this message. Thank you. ___________________ EmacsConf 2022 Online Conference ___________________ December 3 and 4, 2022 Table of Contents _________________ 1. Call for Participation 2. Important dates 3. Talk formats 4. Preparing and submitting your proposal 5. Getting involved 6. Commitment to freedom 1 Call for Participation ======================== [EmacsConf 2022] will be a virtual conference on *December 3 and 4, 2022 (Sat-Sun)*. If you'd like to present at the conference, please [submit your proposal] by *September 30, 2022*. EmacsConf 2022 is about the joy of [Emacs] and Emacs Lisp. Come share your experiments and adventures with the Emacs text editor / operating system / way of life! We welcome speakers of *all backgrounds* and *all levels of experience*, including newcomers giving their first talk. What have you found exciting about Emacs lately? What do you wish someone had told you when you were starting out? What part of your workflow might inspire someone to get into Emacs or go deeper? A great way to get started with writing a proposal is to start by exploring the programs from previous years: [2021], [2020], [2019], [2015], [2013]. You might also find some neat ideas on the [ideas] page. Feel free to add yours there too! If you're still not sure, come by our IRC channel `#emacsconf' on `irc.libera.chat' and say hi. You can join the chat using [your favourite IRC client], or by visiting [chat.emacsconf.org] in your web browser. All kinds of people use Emacs for all kinds of things. We'd love it if EmacsConf 2022 could highlight interesting perspectives and reflect the diversity of our community. If you know someone who might have a good idea for a talk, please reach out to them and encourage them to submit a proposal. Many people (especially from underrepresented groups such as women, people of colour, non-developers, etc.) might not consider themselves proficient enough to share their thoughts. If you let them know that you value their knowledge and experiences, and maybe even suggest something that you think others would like to hear about, they may realize that they do have something worth sharing and that we would love to hear from them. [EmacsConf 2022] [submit your proposal] [Emacs] [2021] [2020] [2019] [2015] [2013] [ideas] [your favourite IRC client] [chat.emacsconf.org] 2 Important dates ================= For EmacsConf 2022, we are planning for 9am to 5pm Toronto/EST (2pm-10pm UTC) on December 3 and 4. Depending on people's availability, it might be two half-days. CFP opens July 17, 2022 CFP closes September 30, 2022 Speaker notifications October 15, 2022 Schedule published October 31, 2022 EmacsConf 2022! December 3 and 4, 2022 If you are not available during the conference itself but you have a neat idea that you'd like to share, please propose it anyway! You can always handle questions after the conference, and we might even be able to coordinate with other Emacs meetups for regional events (if you're an Emacs meetup organizer and would like to make this happen let's [get in touch]!). Please note that although we will try our best to stick to the above dates in the coming months, given the current state of the world, we may have to move things around a bit in case of unforeseen events. Thank you for your patience and understanding. [get in touch] 3 Talk formats ============== We'd like EmacsConf 2022 to inspire lots of different people to explore lots of different things in Emacs. We hope to put together a stream of quick ideas followed by lots of conversation over IRC and/or Q&A sessions, with occasional deep dives into topics that many people might find interesting or useful. As you think about your talk/session, consider what you can share in: - *Up to 10 minutes total:* What is the core idea? What do you want people to do or remember? You can show just enough to get people interested and then point them to where they can learn more afterwards. You can answer questions over IRC, the pad, or the wiki, and there's no limit to how long that conversation can go. - *Up to 20 minutes total:* How would you flesh out some of the points from your 5-10 minute presentation? How can you show the pieces working together? - *Up to 40 minutes total:* What would benefit from a deep dive? How do you keep it engaging? When writing your proposal, please write an outline of what you plan to talk about if you have 5-10 minutes. If you'd like to propose a longer talk, outline what you might include if you had more time to present (up to 40 minutes, including Q&A). Here's an example for a potentially 40-minute talk: - 5-10 minutes: quick demo of the abc package working together with xyz package. - 20 minutes: same as above, with some customization options to accommodate a different workflow. - 40 minutes: all of the above, including modifying the behaviour of the package in order to add something new. This flexibility would help us in devising the conference schedule so that as many people as possible could get a chance to present their ideas, while still allowing for featuring longer deep dive talks. Other session formats such as tutorials, workshops, and hangouts are welcome as well, in case you would find those other formats preferable to a traditional talk format. If you're interested in these or other session types, please let us know [publicly] or [privately]. We'll be happy to work something out with you. [publicly] [privately] 4 Preparing and submitting your proposal ======================================== We're aware that it can be challenging and intimidating to prepare and submit a proposal to a conference, and we want to help make it less so. Come say hi to us on our IRC channel `#emacsconf' on `irc.libera.chat', and we'd be happy to try and answer any questions or concerns you may have about writing your proposal or submitting it. We'd also love to receive suggestions on how we can best help you and other prospective speakers interested in giving a talk at EmacsConf. Once you're ready to submit your proposal, the [submit] page has the instructions on how to submit your talk. The submissions will then be reviewed by a selection committee (please [let us know] if you would like to help review submissions as part of this committee). If your talk is approved, we'd love it if you could help us make sure the conference runs smoothly. After we email you with the time allotted for your talk, we'll ask you to - prepare a prerecording of your talk, or record it with our help if that'd be easier for you; and - schedule a short tech-check if you'd like to be able to answer questions in a live session. Don't forget to subscribe to our main mailing list, [emacsconf-discuss], for discussion and announcements about the EmacsConf conference. If you'd like to propose something other than a talk, like restreaming the conference, you can also use this CFP to share your ideas with us. We look forward to your ideas and submissions! [submit] [let us know] [emacsconf-discuss] 5 Getting involved ================== If you would like to help with the conference (planning the sessions, reviewing proposals, helping with infrastructure, making sessions more accessible, editing video transcripts, etc.), see our [planning] page and come say hi to us at `#emacsconf' on `irc.libera.chat'. Importantly, as EmacsConf continues to grow and receive increasingly more talk/session proposal submissions each year, we have thought about adding multiple parallel tracks during the conference days to accommodate the large number of sessions. However, we're currently a very small team and we would need your help to do it! If you're interested in helping stream a parallel EmacsConf track and have a reliable internet connection with decent speed and bandwidth, please [get in touch] with us so we can help get you set up for streaming. We'd also likely need more volunteers still for each track, for example a host for that track to announce the next talk (this can also be done by the streamer if the streamer is interested and able to) and another volunteer to help check in speakers of upcoming live sessions. If you are interested and able to help with any of the above, please reach out to us; we'd love to have your help! In addition to the [emacsconf-discuss] list, feel free to subscribe to [emacsconf-org] as well, for discussions related to organizing the conference by the EmacsConf organizers and volunteers. We'd really appreciate your help in making EmacsConf 2022 the best one so far! [planning] [get in touch] [emacsconf-discuss] [emacsconf-org] 6 Commitment to freedom ======================= We remain fully committed to freedom, and we will continue using our infrastructure and streaming setup consisting entirely of [free software], much like previous EmacsConf conferences. Articles and documentation about the EmacsConf infrastructure are still underway, and will be announced on the emacsconf-discuss list when available. If you are curious about the EmacsConf infrastructure or are interested in working on it, please join our `#emacsconf-infra' channel on `irc.libera.chat' and say hi! [free software] --=-=-= Content-Type: text/x-org Content-Disposition: attachment; filename=emacsconf-2022-cfp.org Content-Description: EmacsConf 2022 Call for Participation #+title: EmacsConf 2022 #+subtitle: Online Conference #+date: December 3 and 4, 2022 #+options: author:nil * Call for Participation [[https://emacsconf.org/2022/][EmacsConf 2022]] will be a virtual conference on *December 3 and 4, 2022 (Sat-Sun)*. If you'd like to present at the conference, please [[https://emacsconf.org/2022/cfp/][submit your proposal]] by *September 30, 2022*. EmacsConf 2022 is about the joy of [[https://www.gnu.org/software/emacs/][Emacs]] and Emacs Lisp. Come share your experiments and adventures with the Emacs text editor / operating system / way of life! We welcome speakers of *all backgrounds* and *all levels of experience*, including newcomers giving their first talk. What have you found exciting about Emacs lately? What do you wish someone had told you when you were starting out? What part of your workflow might inspire someone to get into Emacs or go deeper? A great way to get started with writing a proposal is to start by exploring the programs from previous years: [[https://emacsconf.org/2021/schedule/][2021]], [[https://emacsconf.org/2020/schedule/][2020]], [[https://emacsconf.org/2019/schedule/][2019]], [[https://emacsconf.org/2015/schedule/][2015]], [[https://emacsconf.org/2013/#program][2013]]. You might also find some neat ideas on the [[https://emacsconf.org/2022/ideas/][ideas]] page. Feel free to add yours there too! If you're still not sure, come by our IRC channel =#emacsconf= on =irc.libera.chat= and say hi. You can join the chat using [[ircs://irc.libera.chat:6697/emacsconf][your favourite IRC client]], or by visiting [[https://chat.emacsconf.org][chat.emacsconf.org]] in your web browser. All kinds of people use Emacs for all kinds of things. We'd love it if EmacsConf 2022 could highlight interesting perspectives and reflect the diversity of our community. If you know someone who might have a good idea for a talk, please reach out to them and encourage them to submit a proposal. Many people (especially from underrepresented groups such as women, people of colour, non-developers, etc.) might not consider themselves proficient enough to share their thoughts. If you let them know that you value their knowledge and experiences, and maybe even suggest something that you think others would like to hear about, they may realize that they do have something worth sharing and that we would love to hear from them. * Important dates For EmacsConf 2022, we are planning for 9am to 5pm Toronto/EST (2pm-10pm UTC) on December 3 and 4. Depending on people's availability, it might be two half-days. | CFP opens | July 17, 2022 | | CFP closes | September 30, 2022 | | Speaker notifications | October 15, 2022 | | Schedule published | October 31, 2022 | | EmacsConf 2022! | December 3 and 4, 2022 | If you are not available during the conference itself but you have a neat idea that you'd like to share, please propose it anyway! You can always handle questions after the conference, and we might even be able to coordinate with other Emacs meetups for regional events (if you're an Emacs meetup organizer and would like to make this happen let's [[https://emacsconf.org/contact/][get in touch]]!). Please note that although we will try our best to stick to the above dates in the coming months, given the current state of the world, we may have to move things around a bit in case of unforeseen events. Thank you for your patience and understanding. #+md: * Talk formats We'd like EmacsConf 2022 to inspire lots of different people to explore lots of different things in Emacs. We hope to put together a stream of quick ideas followed by lots of conversation over IRC and/or Q&A sessions, with occasional deep dives into topics that many people might find interesting or useful. As you think about your talk, consider what you can share in: - *Up to 10 minutes total:* What is the core idea? What do you want people to do or remember? You can show just enough to get people interested and then point them to where they can learn more afterwards. You can answer questions over IRC, the pad, or the wiki, and there's no limit to how long that conversation can go. - *Up to 20 minutes total:* How would you flesh out some of the points from your 5-10 minute presentation? How can you show the pieces working together? - *Up to 40 minutes total:* What would benefit from a deep dive? How do you keep it engaging? When writing your proposal, please write an outline of what you plan to talk about if you have 5-10 minutes. If you'd like to propose a longer talk, outline what you might include if you had more time to present (up to 40 minutes, including Q&A). Here's an example for a potentially 40-minute talk: - 5-10 minutes: quick demo of the abc package working together with xyz package. - 20 minutes: same as above, with some customization options to accommodate a different workflow. - 40 minutes: all of the above, including modifying the behaviour of the package in order to add something new. This flexibility would help us in devising the conference schedule so that as many people as possible could get a chance to present their ideas, while still allowing for featuring longer deep dive talks. Other session formats such as tutorials, workshops, and hangouts are welcome as well, in case you would find those other formats preferable to a traditional talk format. If you're interested in these or other session types, please let us know [[https://lists.gnu.org/mailman/listinfo/emacsconf-org][publicly]] or [[https://lists.gnu.org/mailman/listinfo/emacsconf-org-private][privately]]. We'll be happy to work something out with you. * Preparing and submitting your proposal We're aware that it can be challenging and intimidating to prepare and submit a proposal to a conference, and we want to help make it less so. Come say hi to us on our IRC channel =#emacsconf= on =irc.libera.chat=, and we'd be happy to try and answer any questions or concerns you may have about writing your proposal or submitting it. We'd also love to receive suggestions on how we can best help you and other prospective speakers interested in giving a talk at EmacsConf. Once you're ready to submit your proposal, the [[https://emacsconf.org/2022/submit/][submit]] page has the instructions on how to submit your talk. The submissions will then be reviewed by a selection committee (please [[https://emacsconf.org/contact/][let us know]] if you would like to help review submissions as part of this committee). If your talk is approved, we'd love it if you could help us make sure the conference runs smoothly. After we email you with the time allotted for your talk, we'll ask you to - prepare a prerecording of your talk, or record it with our help if that'd be easier for you; and - schedule a short tech-check if you'd like to be able to answer questions in a live session. Don't forget to subscribe to our main mailing list, [[https://lists.gnu.org/mailman/listinfo/emacsconf-discuss][emacsconf-discuss]], for discussion and announcements about the EmacsConf conference. If you'd like to propose something other than a talk, like restreaming the conference, you can also use this CFP to share your ideas with us. We look forward to your ideas and submissions! * Getting involved If you would like to help with the conference (planning the sessions, reviewing proposals, helping with infrastructure, making sessions more accessible, editing video transcripts, etc.), see our [[https://emacsconf.org/2022/planning/][planning]] page and come say hi to us at =#emacsconf= on =irc.libera.chat=. Importantly, as EmacsConf continues to grow and receive increasingly more talk/session proposal submissions each year, we have thought about adding multiple parallel tracks during the conference days to accommodate the large number of sessions. However, we're currently a very small team and we would need your help to do it! If you're interested in helping stream a parallel EmacsConf track and have a reliable internet connection with decent speed and bandwidth, please [[https://emacsconf.org/contact/][get in touch]] with us so we can help get you set up for streaming. We'd also likely need more volunteers still for each track, for example a host for that track to announce the next talk (this can also be done by the streamer if the streamer is interested and able to) and another volunteer to help check in speakers of upcoming live sessions. If you are interested and able to help with any of the above, please reach out to us; we'd love to have your help! In addition to the [[https://lists.gnu.org/mailman/listinfo/emacsconf-discuss][emacsconf-discuss]] list, feel free to subscribe to [[https://lists.gnu.org/mailman/listinfo/emacsconf-org][emacsconf-org]] as well, for discussions related to organizing the conference by the EmacsConf organizers and volunteers. We'd really appreciate your help in making EmacsConf 2022 the best one so far! * Commitment to freedom We remain fully committed to freedom, and we will continue using our infrastructure and streaming setup consisting entirely of [[https://www.gnu.org/philosophy/free-sw.html][free software]], much like previous EmacsConf conferences. Articles and documentation about the EmacsConf infrastructure are still underway, and will be announced on the emacsconf-discuss list when available. If you are curious about the EmacsConf infrastructure or are interested in working on it, please join our =#emacsconf-infra= channel on =irc.libera.chat= and say hi! * COMMENT Copyright & License Copyright (c) 2020 Amin Bandali, Sacha Chua, David Bremner Copyright (c) 2021 Amin Bandali, Sacha Chua, Leo Vivier, Sebastian Crane Copyright (c) 2022 Amin Bandali The EmacsConf 2022 Call for Participation is part of the EmacsConf wiki, and is dual-licensed under the terms of the Creative Commons Attribution-ShareAlike 4.0 International Public License; and the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. A copy of these two licenses is available on the EmacsConf wiki, in the [[https://emacsconf.org/COPYING.CC-BY-SA][COPYING.CC-BY-SA]] and [[https://emacsconf.org/COPYING.GPL][COPYING.GPL]] files. * COMMENT How to export this file :noexport: As of the time of writing this document (Org mode version 9.3.7), the Org links library (=ol.el=) does not yet recognize =ircs= link types, and will throw an error if you try to export a file containing them, such as this file. To work around that, you can use something along the lines of the Emacs Lisp code below, by either adding it to your init file, or by putting the point in the code block and hitting =C-c C-v e= (that is, hold Ctrl, then hit c followed by v, then release Ctrl, and hit e) to evaluate the code, working around the issue only for the current session. #+begin_src emacs-lisp :results silent (org-link-set-parameters "ircs" :export (lambda (link description format) "Export an ircs link. See `org-link-parameters' for details about LINK, DESCRIPTION and FORMAT." (let ((desc (or description link))) (pcase format (`html (format "%s" link desc)) (`md (format "[%s](ircs:%s)" desc link)) (_ nil))))) #+end_src --=-=-=--