> The selection of bibtex that talaria-bibtex supports is arbitrary, 
> small, and indicated by inscrutable errors so I suggest to not accept 
> this patch.
> 
> I may just inline the source of talaria-bibtex into the forester source 
> and then edit it heavily.
> 
> -Owen

I have gone an alternative route and written a python script which works 
quite well: https://github.com/olynch/bib2forester.

This python script also supports pulling directly from a doi, e.g.

> I've written a basic bibtex importer. It's not perfect, but I think that
> it's fine if the generated trees take a small amount of manual editing
> before they compile correctly; this still saves a lot of typing!

The selection of bibtex that talaria-bibtex supports is arbitrary, 
small, and indicated by inscrutable errors so I suggest to not accept 
this patch.

I may just inline the source of talaria-bibtex into the forester source 
and then edit it heavily.

-Owen

Hello all,

I've written a basic bibtex importer. It's not perfect, but I think that
it's fine if the generated trees take a small amount of manual editing
before they compile correctly; this still saves a lot of typing!

One notable limitation is that this only works with .bib files
containing precisely one entry. This is the format that the .bib files
generated by [pubs](https://github.com/pubs/pubs) have, so this is
extremely useful for me, but may be less useful for people who have .bib
files with many entries.

Any suggestions for how to design this better are more than welcome.
[message trimmed]

Hi Jon,

I was going to bug you to add documentation for the --template feature
for forester new, but then I thought it would be slightly more
convenient if I made a stab at it. I'm not sure what release this was
added in.

-Owen

---
 trees/jms-011P.tree | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
[message trimmed]

Yes of course, no problem! Thanks so much!

-Owen

On December 28, 2024 6:01:44 PM GMT, Kento Okura <kentookura@gmail.com> wrote:
>Hi Owen, I just tried to apply this patch, but it does not apply anymore
>on my dev branch. Do you mind if I just manually add these changes? The
>commit author will be me, I will properly attribute this work to you in
>the message. If not, may I ask you to send another patch that applies on
>this branch?
>
>https://git.sr.ht/~jonsterling/ocaml-forester/log/lsp-refactor-squashed
>
>Best, Kento

(note, this is a repeat because I forgot to put [PATCH] in the subject
line before!)

Hi Jon,

I've finally managed to figure out the right incantations to build
forester statically through nix.

Notes:

1. It doesn't work to simply build this with a statically-linked OCaml compiler;
in fact the OCaml compiler itself must be dynamically linked for ppx_deriving
to be supported.

Hi Jon,

This patch adds a very simple preview server to forester. It doesn't do
any fancy file-watching reloading; it simply rebuilds on "Enter", and
then you have to refresh the page manually. At topos and at SGAI we've
been using a python script for the same effect, but I thought it'd be
nice to have it integrated into the binary.

It is unfortunate that including dream more than doubles the binary size
of forester, but my understanding is that dream is going to be included
at some point anyways so this is not a huge deal.

This patch depends on the previous patch I sent in for static
[message trimmed]

Hi Jon,

I've finally managed to figure out the right incantations to build
forester statically through nix.

Notes:

1. It doesn't work to simply build this with a statically-linked OCaml compiler;
in fact the OCaml compiler itself must be dynamically linked for ppx_deriving
to be supported.
2. I've also managed to figure out how to not do the janky thing with applying
the patch to change the compiler options; instead I do that with a dune profile
now.
[message trimmed]

Hello,

I'm trying out the latest forester 5.0 prerelease, and when I run it on
any of my forests (the Safeguarded AI, Topos, or LocalCharts forests) I
get an error:

Fatal error: exception Unhandled asai effect/exception; use Reporter.run
Raised at Stdlib__Effect.Deep.try_with.(fun) in file "effect.ml", line 101, characters 47-54
Called from Eio_unix__Thread_pool.run in file "lib_eio/unix/thread_pool.ml", line 108, characters 8-13
Re-raised at Eio_unix__Thread_pool.run in file "lib_eio/unix/thread_pool.ml", line 113, characters 4-39
Called from Eio_linux__Sched.run.(fun) in file "lib_eio_linux/sched.ml", line 498, characters 22-90
Re-raised at Eio_linux__Sched.run in file "lib_eio_linux/sched.ml", line 509, characters 22-57
Called from Eio_linux__Sched.with_eventfd in file "lib_eio_linux/sched.ml", line 536, characters 8-18

(I apologize for the repeat email; I failed at correct email formatting before)

Hi all,

This is a small patch based on forester 4.3.1 which I imagine is hopelessly out
of date (especially with the datalog changes!), but I wanted to get some
feedback on the general idea, and I can re-implement it once the datalog version
stabilizes.

This adds a "forester transplant" command, with syntax "forester transplant
FOREST_TOML_FILE TAG OUTPUT_FILE". It outputs all of paths to the source code of
trees that either contain the tag TAG or are recursively transcluded in some
tree that contain the tag TAG.
[message trimmed]