emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TEC <tecosaur@gmail.com>
To: Ivan Yonchovski <yyoncho@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Announcement] lsp-mode integration with org-mode
Date: Mon, 08 Jun 2020 21:53:47 +0800	[thread overview]
Message-ID: <873675k6eg.fsf@gmail.com> (raw)
In-Reply-To: <875zc1iyll.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]

Ivan Yonchovski <yyoncho@gmail.com> writes: 
>> That sounds great! Just to check, in the demo you have :tangle 
>> "demo2.cpp", this would also work with :tangle yes, yes? 
> lsp-mode will need actual file path to work. I am not sure what 
> "yes" will mean in this context.

This is fairly simple, it means inherit the file name, and apply 
the relevant extension. For example a python block in demo.org 
with :tangle yes exports to demo.py.
>> One question --- does this also work in the minibuffers? At the 
>> moment I have a hack in my config 
>> (https://tecosaur.github.io/emacs-config/config.html#lsp-support-src) 
>> to provide this functionality, but it doesn't use the context 
>> of the entire file, which would be a nice improvement. 
> Can you give me an example of that usecase? Generally, we have 
> introduced "virtual-buffer" abstraction so technically we could 
> implement running language server over anything. E. g. one could 
> select random text block and run a language server over it. 

This is what pops up when you call org-edit-special (C-c '). It's 
nice because it changes the major mode, and has better font-lock 
Hopefully that helps,


[-- Attachment #2.1: Type: text/html, Size: 1585 bytes --]

  reply	other threads:[~2020-06-08 13:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 19:20 [Announcement] lsp-mode integration with org-mode Ivan Yonchovski
2020-06-08  9:54 ` TEC
2020-06-08 11:30   ` Ivan Yonchovski
2020-06-08 13:53     ` TEC [this message]
2020-06-08 14:20       ` Ivan Yonchovski
2020-06-09  1:08 ` stardiviner
2020-09-03 10:09   ` 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:

  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=873675k6eg.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yyoncho@gmail.com \


* 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


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