CosmicHorror
CosmicHorror
We should respect some of the basic properties for image caching (with an easy way to clear the cache), so that we can avoid repeating a bunch of image calls...
Having been working with the interpreter more it's clear that the current design is pretty painful to work with in almost every way. It currently works by doing a pass...
Clicking a file link like ```md [COPYING](COPYING) ``` will cause `inlyne` to panic Relevant crash report ```toml name = "inlyne" operating_system = "Arch Linux Rolling Release [64-bit]" crate_version = "0.4.1"...
See https://github.com/trimental/inlyne/issues/97#issuecomment-1540796548 @nicoburns Spinning this off into it's own issues since it seems distinct Reference image ![image](https://user-images.githubusercontent.com/1007307/237203944-a5ab5b9f-b90f-4e0b-85f2-a8dca8280910.png) It looks like we _do_ set the background color based on the theme....
![image](https://github.com/Inlyne-Project/inlyne/assets/30302768/99fd7e47-4a95-404e-a998-661bf90a8bec) From the README you can see that the header looks right aligned with the text flowing over the second line even though it should be center aligned
in my case not only fonts, even images appear with wrong contrast and different colors than should be: ![1694176554](https://github.com/trimental/inlyne/assets/6182099/6457c757-9de0-4930-8415-78ab0158e505) ![1694176810](https://github.com/trimental/inlyne/assets/6182099/d1feba97-d2f9-4cb9-bd2f-977b971c3d2f) Above is inlyne, below is normal image opened with firefox...
Currently toggles back on footnote support, but should fix #135 before this is ready to merge
It would be cool if the file watcher registered paths for local image files used in the markdown document, so that reloading works when changing the local image This needs...
`` and `` seem to be one of the more common elements that we are missing support for (so they render as regular text instead). It would be good to...