-
re:: the Git.Merge.base
-
{{[[TODO]]}} is [[re]] an [[anti-pattern]]? i.e. it becomes unclear if what you are "referring to" is from the content above, or some other page (if it's not a linked ref (of a page or a block) and just text) - you might start looking at the previous content but not find the thing that i meant to refer to, or even worse - could find something that is actually not the thing, and then get further confused. idk idk
-
re:: ((wiW41Si-y))
-
#[[(hidden) jOMmlCP4S]] / #[[(hidden) D1lY0CG5e]] for [[roam]] - would having a central place for settings, provided by the [[(hidden) AqlNqCYG6]]s / extensions, be useful?
-
something similar to [[vscode]] i suppose
-
thought about it because it'd likely save time / less http requests to do -- even if you have [[meta tags]], you don't need to 1. fetch your custom settings page, 2. fetch the linked references of the tags - you'd be ensured that 1. is always done & up-to-date (it's easier for roam if it itself tracks what's updated & when it is - just updates, otherwise caches)
-
but, maybe inconvenience if you're using some other languages for the [[(hidden) AqlNqCYG6]]s (if even possible?), and in general feels less [[wild west]]-like / less [[(hidden) NWcsO1fe0]]. will see.
-
-
-
{{[[TODO]]}} is [[re]] an [[anti-pattern]]? i.e. it becomes unclear if what you are "referring to" is from the content above, or some other page (if it's not a linked ref (of a page or a block) and just text) - you might start looking at the previous content but not find the thing that i meant to refer to, or even worse - could find something that is actually not the thing, and then get further confused. idk idk
-
-
re:: `publicRecursive` tag @ [[export-html-pages]]
-
maybe instead of `publicRecursive`, we need to make it a point that the purpose of this is to have everything in daily notes, and under that tag, blocks become public and end up in the page as a linked mention.
-
so that it'd be made clear that this is the purpose of it, and not a general `publicRecursive` meta-tag. then, we'd be able to very easily detect if something is a "page collector" or whatever better name we come up with, and then e.g. the coloring stuff becomes way more precise
-
{{[[TODO]]}} might even be useful for [[roam's multiplayer mode]] and the #[[(hidden) jOMmlCP4S]] of [["putting" things into multiple graphs]], or, rather, giving other, shared-graphs e.g. read access to some of your notes, if they're under that tag (while still being able to own them?)
-
-
re:: ((wiW41Si-y))
-
#[[(hidden) jOMmlCP4S]] / #[[(hidden) D1lY0CG5e]] for [[roam]] - would having a central place for settings, provided by the [[(hidden) AqlNqCYG6]]s / extensions, be useful?
-
something similar to [[vscode]] i suppose
-
thought about it because it'd likely save time / less http requests to do -- even if you have [[meta tags]], you don't need to 1. fetch your custom settings page, 2. fetch the linked references of the tags - you'd be ensured that 1. is always done & up-to-date (it's easier for roam if it itself tracks what's updated & when it is - just updates, otherwise caches)
-
but, maybe inconvenience if you're using some other languages for the [[(hidden) AqlNqCYG6]]s (if even possible?), and in general feels less [[wild west]]-like / less [[(hidden) NWcsO1fe0]]. will see.
-
-
-
{{[[TODO]]}} is [[re]] an [[anti-pattern]]? i.e. it becomes unclear if what you are "referring to" is from the content above, or some other page (if it's not a linked ref (of a page or a block) and just text) - you might start looking at the previous content but not find the thing that i meant to refer to, or even worse - could find something that is actually not the thing, and then get further confused. idk idk
-
-
-
-
-
re:: "no-code" - lol, ofc you'd have to code up the [[(hidden) AqlNqCYG6]]s, but then you can share them and use them and everything's directly in roam. fuuuuuuuck this is [[(hidden) -MiVLWUzx]]
-
(hidden) D1lY0CG5e:: {{[[TODO]]}} ideally you'd be able to [[self-host]] [[roam]] because at this point you'd be [[running critical infrastructure]]
-
{{[[TODO]]}} okay more [[(hidden) jOMmlCP4S]]s coming in from thinking about this:
-
-
re:: [[(hidden) _d7I12UTL]]
-
re:: [[creating jira issues / sub-tasks from roam's TODOs]]
-
(hidden) fciPnpZIh re::
-
re:: custom domain - ((UUaQUFGpI))
-
re:: coloring public blocks' lines
-
{{[[TODO]]}} another #[[(hidden) jOMmlCP4S]] -- instead of having every single line to recursively, why not follow in a $$45\degree$$ or whatever angle and highlight only the right-most lines?
-
{{[[TODO]]}} yet another #[[(hidden) jOMmlCP4S]] - being able to copy a link to a page, or rather - to a specific block which will end up in that page
-
use case e.g. - creating a git commit, and instead of inlining stuff that you already wrote down, instead linking to it.
-
extra stuff to work out though because depends on where you want the link to end up at -- the daily notes page, or within some page as a linked mention.
-
{{[[TODO]]}} would need to have a predefined base url for the notes in the [[roam-traverse-graph-settings]] page.
-
-
{{[[TODO]]}}
-
-
re:: ((crag_e60m))
-
haha i guess fair, but don't worry much - [[roam-traverse-graph]] is first and foremost a low-level utility/library that one can use to build tools such as [[export-html-pages]]. and if we take our own shot at it - it's how we want it to be, and if we have some [[unique]] (?) [[(hidden) jOMmlCP4S]]s & are able to explore them - the better it is for all!
-
-
{{[[TODO]]}} another #[[(hidden) jOMmlCP4S]] from the [[re]] attribute above - in the html, consider having previews of pages on hover.
-
re:: the `Exitable` stuff
-
wait, why not use `throw` and a regular `Error` - since it can be anything, we can give an object, and inside it - the process exit code, whether it's a success or a failure, the message (automatically stdout/stderr), etc.!
-
-
https://github.com/codeshiftcommunity/codeshiftcommunity/blob/main/packages/cli/bin/codeshift-cli.js#[[(hidden) WBl6TSRcS]]16-L22
-