From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: Org mode and Emacs Date: Sun, 12 Jun 2022 13:28:01 +1000 Message-ID: <87o7yywn1m.fsf@gmail.com> References: <87h74ztshe.fsf@gmx.de> <871qw31ois.fsf@yahoo.com> <8735gj4ceo.fsf@gnu.org> <87ee038ipt.fsf@gmx.de> <87o7z61v59.fsf@gmail.com> <87bkv527p5.fsf@gmail.com> <835yld93w7.fsf@gnu.org> <877d5t0yrn.fsf@gmail.com> <87r140yuof.fsf@gmail.com> <875yl9e7zm.fsf@gmail.com> <87y1y2irhn.fsf@yahoo.com> <87wndmaaow.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12752"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.27; emacs 28.1.50 Cc: Ihor Radchenko , Po Lu , Richard Stallman , monnier@iro.umontreal.ca, acm@muc.de, emacs-devel@gnu.org To: David Masterson Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 12 05:59:13 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o0Ekr-0003Cs-B4 for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 05:59:13 +0200 Original-Received: from localhost ([::1]:47318 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0Ekp-0006J5-LX for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Jun 2022 23:59:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44416) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0Ejo-0005QJ-4D for emacs-devel@gnu.org; Sat, 11 Jun 2022 23:58:08 -0400 Original-Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]:33614) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o0Ejl-0005yz-Fi; Sat, 11 Jun 2022 23:58:07 -0400 Original-Received: by mail-pl1-x62e.google.com with SMTP id f9so2477960plg.0; Sat, 11 Jun 2022 20:58:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:cc:subject:date:in-reply-to :message-id:mime-version; bh=ftI8qwDxuWD1pmM9O5K0mrjy28CiGYcYvoNMXMB/c2E=; b=pCLqPE/96WdxjuzCqLJ/xpd7yg5sOWBup27W9Be1Iixl5Q01mTCktz+d9LdxfD8RfP RRhx+FIB37DnfYp8fnXtnU8NHWJ5iYjqGwOI9GbxUOwCV9oYPUcG8JkK61LmNAjhSTMm tnYKkko3Gi0aCt7FYIAzYidy5qjWRitkxrHCnf6RARcUYpJHZAKm1aZxPPs5s6RqL+qt NaVg/RmMNjtXCpRuzD44Ley98i/YOjfgbEK+/2WYAcxAbKAVrvqmXuEjszXKxtdn3fDi 0h1X3GI6hLA17A26sjgPorxdz82X72dU/P+CaGXyomn8QK85WKqs61ZOV1fhPh4oN4Nb S+uQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:cc:subject:date :in-reply-to:message-id:mime-version; bh=ftI8qwDxuWD1pmM9O5K0mrjy28CiGYcYvoNMXMB/c2E=; b=V3Yc5wCJKU5Vzbr1jUPLLohuzSM3Y+FjrvsE8ZJNf+XGsK+MB7gPy1KmOwLsZyEAsd bqsadNAnWZ10pd9V1Y7rxt9hWag/rgzPMYwHaqltGPRdCfSywtAtjiq0OconIiaUjetF OHEzMZto79elk4JpkRq8GuprDmSEOfGJTiK9xrI4fYjQwcdJzHgfsYCQc4TiLhdiQP1+ S+0saXAMM5DB+Dy03EzMRvyrhL52unKfdxSVtf/d/MkC0XUlNWQ0vtffconJJaFILmZy Xwe2uFM9NtmonA1cmlyOTE7EPi5FqUOuVzlIW02XW+ipqOxheqKJoRqbKcXm7njz0asw CdIg== X-Gm-Message-State: AOAM533H+fyNVrxCuojEyzLVi534wvbFwhVmo0gnx68/IsMpeTuTIzl/ yLu9TB6sj9HtWuXzvgaG3O/nC3lYcQklcQ== X-Google-Smtp-Source: ABdhPJw7ZtMxEdmZkSC1wLZfpdyCPVafhYvjDHqzAY3ObWsFNEHqjjS606BXL0+bvW5oj5GCwZ1O1g== X-Received: by 2002:a17:90b:4b47:b0:1e8:9529:27c6 with SMTP id mi7-20020a17090b4b4700b001e8952927c6mr8162084pjb.178.1655006283594; Sat, 11 Jun 2022 20:58:03 -0700 (PDT) Original-Received: from dingbat (2001-44b8-31f2-bb00-63fa-329c-dbc6-d47e.static.ipv6.internode.on.net. [2001:44b8:31f2:bb00:63fa:329c:dbc6:d47e]) by smtp.gmail.com with ESMTPSA id pg8-20020a17090b1e0800b001e28e80a8d6sm2227571pjb.38.2022.06.11.20.58.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 11 Jun 2022 20:58:03 -0700 (PDT) In-reply-to: Received-SPF: pass client-ip=2607:f8b0:4864:20::62e; envelope-from=theophilusx@gmail.com; helo=mail-pl1-x62e.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291060 Archived-At: David Masterson writes: > Ihor Radchenko writes: > >> Po Lu writes: >> >>> Texinfo also comes with the added benefit of not requiring Emacs to edit >>> or to translate into other formats. >> >> You can edit Org files outside Emacs. Say, in vim. >> The point about exporting to other formats is valid. >> >> This last point also raises a question. Can Elisp interpreter and >> libraries be factored out of Emacs to create a way to execute Elisp >> programs without installing all the interactive parts of Emacs? > > Isn't Tim Cross(?) working on something like that -- ie. a parser for > the Org language. Once we have a solid parser, we can build a standard > (set of?) backend(s) for much of Orgmode. No. Ihor is the one working on the parser. I think Ihor's question about isolating the Elisp interpreter is about options to make org mode work outside of Emacs. There are frequent questions to the org list about making org available to other editors/environments. However, the big problem is that much of the really powerful featurs of org mode are intrinsically tied to elisp functionality - for exmaple all the babel and backend export support. While it is possible to write a parser in any language which would enable basic org markup/formatting, that does not solve the problem of executable blocks, babel/noweb and interaction with back end exporters etc. This would be one example of where something like an elisp LSP module would be useful. However, the idea of an elisp LSP module was discouraged by a couple of people on this list over concerns that such a module would enable non-free platforms to take advantage of elisp - a fear which I think is overstated and which I think one person referred to as "Jumping at shadows" The overall conclusion was that such a module would be considerable amount of work. Some suggested you could use emacsclient to create something which could be used in such a manner. However, I suspect that if you go to the effort of installing and configuring emacs, you would just use emacs.