emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Samuel Banya" <sbanya@fastmail.com>
To: "Charles Berry" <emacs-orgmode@gnu.org>
Subject: Re: typescript from org src buffer -- tide, lsp
Date: Sat, 06 Nov 2021 11:29:36 -0400	[thread overview]
Message-ID: <a1058646-b56b-48b1-a5e3-f311af7cbdf1@www.fastmail.com> (raw)
In-Reply-To: <8735o97ejp.fsf@gmail.com>

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

Cool topic, but I haven't done it myself either as most explanations are pretty big-brained in the sense that its a little hard for a beginner to figure out sometimes.

However, the power of literate programming is super cool, so here's a few links I found that you can go through that might help you out:

Hope it helps, 


On Sat, Nov 6, 2021, at 6:33 AM, Tim Cross wrote:
> Greg Minshall <minshall@umich.edu> writes:
> > hi.
> >
> > i'm wondering if anyone programming in typescript might have run into,
> > and solved, this "problem", of tangling into a subdirectory, and tide
> > [1] not being able to resolve "relative" imports.
> >
> > i have a file in path /a/b/foo.org.  it includes various source blocks,
> > and they do things like `:tangle c/d/bar.ts`.  another source block,
> > tangled into in c/d/fubar.ts, say, does something like:
> > ----
> > import Bar from "./bar"
> > ----
> >
> > when i open an Org Src edit buffer from fubar.ts's source block, with
> > tide mode [1] enabled, i get a complaint
> > ----
> > Cannot find module './bar' or its corresponding type declarations. [2307]
> > ----
> > tide (or, really, iiuc, tsserver) appears to be, reasonably, looking for
> > /a/b/bar.ts, and not finding it.  but, i haven't been able to figure out
> > how to talk tide into looking elsewhere.
> >
> > i've done things like add "rootDirs" to `tsconfig.json`, to no avail.  i
> > haven't been able to get lsp-mode [2] to work for this scenario, either.
> >
> > anyway, in case anyone has done exactly that, i'm asking.
> >
> I've not tried to do this, but a complete shot in the dark....
> according to the org manual, you can set a :dir value in the source
> block header which will specify the working directory to be used i.e.
> the directory where the code will be evaluated. Perhaps setting that to
> the directory where the other block has tangled the output would work?
> See the Environment of a code block node under the working with source
> code node in the org manual for details.

[-- Attachment #2: Type: text/html, Size: 3734 bytes --]

  reply	other threads:[~2021-11-06 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  3:30 Greg Minshall
2021-11-06 10:33 ` Tim Cross
2021-11-06 15:29   ` Samuel Banya [this message]
2021-11-06 16:56   ` Greg Minshall

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=a1058646-b56b-48b1-a5e3-f311af7cbdf1@www.fastmail.com \
    --to=sbanya@fastmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: typescript from org src buffer -- tide, lsp' \


* 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:


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