emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Dominik Schrempf <dominik.schrempf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Emacs as an Org LSP server
Date: Tue, 15 Dec 2020 02:36:00 +0300	[thread overview]
Message-ID: <X9f24GGzzqNRJOnU@protected.rcdrun.com> (raw)
In-Reply-To: <87ft48f22r.fsf@gmail.com>

* Dominik Schrempf <dominik.schrempf@gmail.com> [2020-12-15 01:36]:
> I think this is an excellent idea. However, I am not familiar with the legal
> aspects mentioned by Jean.

I hope there will be no legal problems and that my statements will be
proven as wrong.

> So far I had good experiences with language servers.  On the other
> side, Org mode is Emacs specific, so this argument does not really
> apply. Do we want Org mode to stay Emacs specific? I don't know.

Org mode has many connections to Open Hyperdocument Template by Doug
Engelbart. The Augment system that has been demonstrated back in maybe
1968 fantastic features that Org mode does not support today in
2020. One of those features is collaboration.

To make Org mode non-software centric is good motion. As if we claim
it is plain text, then plain text may be implemented by other
editors. That boosts or opens first steps to more collaboration. I do
not see LSP server that as good collaboration method, but it can open
various editors to that.

What would be more collaborative is to extend the Org-LSP to read
information from Emacs instance and provide Org structure to its
clients. As Org is not just a programming language that one may do
with any editor, it is dependent on Emacs. There are some other
implementations of Org mode, but it is mostly dependent on Emacs.

Org-LSP implementation that could, at least optionally, read
structured data in a running Emacs instance, or read such data in an
Org file where server resides, then it could eventually provide to its
clients access to more features than commonly expected from LSP, such
as lists of tags, properties, timestamps, including capture templates,
and agenda features. Then if server would be really remote, users
could at least collaborate in the sense that they could work on
similar or same set of structured Org data. They could assign tasks to
same people or have same types of TODO keywords, common LaTeX and PDF
export decorations or other specific settings.



  reply	other threads:[~2020-12-14 23:37 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 15:05 Emacs as an Org LSP server TEC
2020-12-13 10:41 ` TEC
2020-12-13 11:05   ` Bill Burdick
2020-12-13 14:36   ` Jean Louis
2020-12-13 17:33     ` TEC
2020-12-13 20:23       ` Jean Louis
2020-12-14  0:54         ` Gerry Agbobada
2020-12-14  1:04           ` Tim Cross
2020-12-14  1:10         ` George Mauer
2020-12-14 11:41   ` Neil Jerram
2020-12-14 15:25     ` TEC
2020-12-14 15:46       ` Neil Jerram
2020-12-14 15:55         ` TEC
2020-12-14 17:02           ` Jean Louis
2020-12-14 17:08             ` TEC
2020-12-14 18:05               ` Russell Adams
2020-12-14 18:12                 ` TEC
2020-12-14 19:16                   ` Russell Adams
2020-12-14 20:18                     ` Jean Louis
2020-12-14 21:34                     ` Tim Cross
2020-12-14 20:20                 ` Tim Cross
2020-12-14 21:45                   ` Tom Gillespie
2020-12-14 18:39               ` LSP is Microsoft's patented protocol - " Jean Louis
2020-12-14 18:44                 ` TEC
2020-12-14 18:52                   ` Jean Louis
2020-12-15  5:47                     ` Richard Stallman
2020-12-15  5:50                       ` Jean Louis
2020-12-15  6:09                         ` Christopher Dimech
2020-12-15  6:25                           ` Jean Louis
2020-12-15  6:51                             ` Christopher Dimech
2020-12-16  5:38                           ` Richard Stallman
2020-12-14 17:27             ` Gerry Agbobada
2020-12-14 18:16               ` Jean Louis
2020-12-14 18:26                 ` TEC
2020-12-14 18:50                   ` Jean Louis
2020-12-14 19:41                   ` Russell Adams
2020-12-14 18:51                 ` Bastien
2020-12-15  8:51               ` Bill Burdick
2020-12-14 19:50             ` Tim Cross
2020-12-14 21:51               ` Jean Louis
2020-12-14 22:35                 ` Dominik Schrempf
2020-12-14 23:36                   ` Jean Louis [this message]
2020-12-14 17:22           ` Neil Jerram
2020-12-14 17:24             ` TEC
2020-12-14 17:57               ` Neil Jerram
2020-12-14 18:04                 ` TEC
2020-12-14 17:39             ` Russell Adams
2020-12-14 17:45               ` TEC
2020-12-16 11:49   ` Bastien

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 \
    --in-reply-to=X9f24GGzzqNRJOnU@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=dominik.schrempf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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
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

	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).