korgster, 2 months ago

@Coyote push through

Coyote, 2 months ago

Trying... anyone on github gitlab or alt CVS?

(uber baller would leave a url for repository in comments)

Coyote, 2 months ago

@korgster I can waste shit-tons of time theming.... rather than coding... ADHD..

Coyote, 2 months ago

@korgster

Coyote, 2 months ago

@korgster

Coyote, 2 months ago

@korgster https://br.ifunny.co/picture/you-are-here-paying-taxes-to-pedophiles-TBDpT9rO9

Humpleupagus, 2 months ago

I spent all day coding in typst and then coding vim syntax for typst...different colors for different heading levels, line comments, block comments, etc. You should try it for documents. It takes variables which makes drafting shit easy...

" and then #your_client called #my_client an asshole"

And it will pump out a table of contents based on the headings with level indention with just a few lines of code. It also bookmarks the pdf. Pretty sweet.

Coyote, 2 months ago

@Humpleupagus you got git? We could repo, I ain't got squat, but lot of pdf2md shit and hopes and dreams of "latex to letterhead" from my md with more scripting,,, ? I have to figure out where to cvs, I no have cloud...

Humpleupagus, 2 months ago

Typst is way more intuitive than latex.

https://github.com/typst/typst

https://typst.app/docs/tutorial/

Coyote, 2 months ago

@Humpleupagus I feel sick now, I was looking for "tiny" .md to latex "legal pleadng" template with bluebook, and I walked inot a international party of coke head java script or something? Ok... learning curve u-turn... hang on a sec...

Coyote, 2 months ago

@Humpleupagus Oh, I have to learn this, this could be the bridge to an automated plead idea I was toying with maybe working.

Humpleupagus, 2 months ago

It's seriously cool, and you can script in it if you're up to it.

The only thing I wish it had was a way to import portions of a document like it was set out inline instead of their import and include approach. (Neither of which pull in variables in a friendly way, though it can be done).

It's workable, but it can be cumbersome for what could be simple if it allowed sed like injection at compile time by first producing a temp file.

You'll see what I mean when you start using import and include functions.

Humpleupagus, 2 months ago

Now that I'm talking out loud, maybe I'll just make a script to do that at compile time.

Coyote, 2 months ago

@Humpleupagus Code

#!/bin/dash
source $problem
echo $solution

Sometimes, scripts work...

Humpleupagus, 2 months ago

Cp typ file to temp
Grep some custom markup with line number
While read line ...
Sed something something (pull text and inject it at the corresponding line in the temp file)
Typst compile temp file

Coyote, 2 months ago

@Humpleupagus I'm probably useless, but I could try to help if you got a plan.. Cause... When it comes together...

Coyote, 2 months ago

@Humpleupagus you got a .vimrc (aka .config/nvim for lua cool kids) on git(lab/hub) with IDE tweaks for this rust-typst thing I could merge?

Humpleupagus, 2 months ago

I don't, but there's this one. It's ok, but only has one color for all headings.

I'm sure it can be edited though.

https://github.com/kaarmu/typst.vim

Also ... you're going to need to export two environmental variables TYPST_ROOT and TYPST_FONT_PATH.

typst will use the root set as a relative path. If you want it absolutely, just set it to root.

Humpleupagus, 2 months ago

I'm going to try to do a pleading now that they added a simple way to stroke tables and grids.

I think it can be done, but will require pdftk. I don't think typst can do the line numbering and text in one document. So I'm going to make pleading paper, then draft the body, and use pdftk to stamp the body onto the paper.

Oh.... I made a stupid simple bates numbering template. I use the same technique. Only instead on one background, I used the counting function and page breaks (which is easy to do in vim. 1000+ page breaks, no problem) to produce the bates numbers, and then I use pdftk to merge them with the documents.