I wished for the same thing but using Forester as a literate
programming environment for Lean 4, and more.

The idea discussed in https://todo.sr.ht/~jonsterling/forester/87 was
trying to do it based on that forester outputs XML, so a post-process
can achieve the same purpose (by presenting both the source and an id
in xml, and a post-process can render from the source to an asset with
the id, be it an image or even an html to embed. But with [the future
of Forester’s XML
format](https://www.forester-notes.org/jms-0127.xml), this might not
be the way to go any more.

It's nice to see some initial discussions on plugins that take the
approach of preprocessing. For now, one can't even do preprocessing

> I'd appreciate an actual example of where something 'goes wrong' cc ~utensil

Sorry I'm busy lately and I don't check the devel mailing list
regularly, and only found this patch randomly. There are no
notifications like Github issues and patches are not convenient to
test like Github forks.

My forest https://github.com/utensil/forest have a series of notes on
category theory https://utensil.github.io/forest/tt-0001.xml , and
they were affected by the switch to dvilualatex, which has the
problems of

> my tikz-pictures are cropped correctly (with no margin on all directions), but not my tikzcds (with a lot margin on top and right)

Sorry, I assumed that this might affect others too, but it turns out
to be a CI specific issue caused by dune cache. Different ways to pin
didn't fix the issue, but pruning cache did.

Regards,

Utensil Song

Hi all,

I've been using `opam pin` to catch up with forester's development at
the time of my choosing, it looks like this:

```bash
opam pin add forester
git+https://git.sr.ht/~jonsterling/ocaml-forester#56de06afe952d752c1a13fdcd8bb56c5fef9956f
--yes
opam install forester --yes
```

It worked well so far, except for some sourcehut downtime when I
really wanted to publish.

Hi Jon and all,

For the issue raised by OP, it's indeed better to recognize the
deprecated syntax and prompt accordingly, instead of dropping the user
to a mysterious internal error.

I would also like to take this opportunity to voice out about wishing
to keep the ability to re-title (thus re-purpose) a note in different
contexts, which seems principally vital to me for a Zettelkasten notes
system. That said, I completely understand that it might be
unnecessarily complicated for supporting this in the coming hyper
media change, and I can embrace this change, but I still wish to seed
its return in the future.

I have encountered an issue similar in nature, and this was reported
as part of #82 here:
https://todo.sr.ht/~jonsterling/forester/82#event-382182 .

My solution was to use an environment variable `TEXINPUTS` to tell
LaTeX to also search for LaTeX files, it looks like this in a shell
script (assuming I put my .tex, .sty etc. in `tex` directory alongside
the directory `trees`, you can use `assets` instead ):

```bash
export TEXINPUTS=.:$PROJECT_ROOT/tex/:
```

where $PROJECT_ROOT is the absolute path to the project root, which

I'm using a solution based on a simple Python script[1] I wrote. So I
can simply add entries to a bib file, then the script will generate
the corresponding reference trees. It handles most of the entries
well, and it preserves manual correction [2].I have another shell
script[3] which would watch the bib file, once it's changed, the trees
will be generated [4].

I'm not satisfied that it depends on Python, which might be an extra
dependency for some, but it was the fastest way to save my time on
copying pasting into reference trees as I frequently add bib entries
(to record the good papers I read). Sorry that I have so many things
on my plate that I haven't found time to simplify it for reuse.

[1]: https://github.com/utensil/forest/blob/d2e9f717c49aa1034781a6327ae0beb9c2c84ee0/split_bib.py

Thanks for the updates in the release notes!

I have a new issue regarding the previous shared query snippets. It
turns out to return more results than I expected, particularly, the
"unstable" trees that are introduced by `\subtree`, they should be
ruled out by the query as they have parents thus are not lost. Reading
https://www.jonmsterling.com/jms-00WS.xml, there seems to be no
built-in relation symbols for these unstable trees, whose signature
would be having a `<fr:parent>` in its XML, but this is not detectable
from the query language. In theory, this is also a type of relation,
not transclusion, but parent ship.

Wonder if there could be some support towards this direction.

Hi Nick,

Here are my 2 cents:

1. Jon's forest use a solution based on `\meta`, e.g.
`\meta{source}{Definition 2.2, \citek{jung-moshier-vickers-2008}}`
which would render as gray texts under the title, rendered:
https://www.jonmsterling.com/jms-00A8.xml .
2. `\ref` is actually mostly used for cross-referencing inside an
article, and gives a result that's like the LaTeX package `cleveref`,
e.g. lemma jms-10A8, but not great for bibliography, Jon's forester
has a solution for bibliography which is also shown in the previous
example, the macro is

Thanks for bringing this up, I had the same confusion. Thanks to Jon's
explanation, I managed to use the new query language to do something I
wanted to do for a long time: querying all potentially lost notes
(i.e. that are not transcluded by any root notes, and not marked as
draft (because I have queries by topic for drafts) ):

```
\scope{
  \open\query
  \open\rel
  \def\query/root{
    \union{\tag{root}}{\tag{notes}}
  }
  \def\query/root/transcluded{