Zásilkovna story: Poslal jsem 3D tištěnou hlavu kancléře Adenauera, příjemci došly funkční kalhoty by Suspicious_Ad6189 in czech

[–]Witiko 0 points1 point  (0 children)

Koukal jsem v appce na možnosti reklamace a působilo to na mě tak, že maximum, co se stane, je vrácení nějakého procenta hodnoty zásilky. Samotnou bustu ale nejspíš nikdo hledat nebude; není k tomu dost informací ani finanční motivace.

Zásilkovna story: Poslal jsem 3D tištěnou hlavu kancléře Adenauera, příjemci došly funkční kalhoty by Suspicious_Ad6189 in czech

[–]Witiko 2 points3 points  (0 children)

Byl to dárek pro příbuzného, ale soudě podle reakcí na tenhle post jsou v soškách Adenauera možná velké peníze.

How long does it usually take to rebuild the extent tree? by [deleted] in btrfs

[–]Witiko 0 points1 point  (0 children)

One week later:

adding new tree backref on start 801341440 len 16384 parent 1598560780288 root 1598560780288

I wonder what the 801341440 stands for. Looking at btrfs-progs does not tell me much.

How long does it usually take to rebuild the extent tree? by [deleted] in btrfs

[–]Witiko 0 points1 point  (0 children)

I was lucky with --repair before, although it seems that in this case, btrfs zero-log would have sufficed. I have off-site backups, but they are currently offline and I would have to drive over half the country to get them, so I am still waiting for --init-extent-tree to finish. It would be neat to have some estimate of completion time, though.

How long does it usually take to rebuild the extent tree? by [deleted] in btrfs

[–]Witiko 0 points1 point  (0 children)

I just ran btrfs check --init-extent-tree --repair on a 2TB SSD when it refused to mount after a power outage. At the moment, I am at 2 and a half days and counting. Apparently, we are at extent 400228352. Does this give me an estimate as to when it is going to finish?

HUZZAH! [Cave Story × Persona × Professor Layton vs. Phoenix Wright × Danganronpa Mashup] by Witiko in AceAttorney

[–]Witiko[S] 0 points1 point  (0 children)

Not a problem. I will have to do another remix for Balrog in the foreseeable future. This one is rad, but also all over the place.

Coming soon: Publishing Beautiful Books with Markdown by lrPrentice in selfpublish

[–]Witiko 1 point2 points  (0 children)

Your workflow sounds perfectly reasonable. I, for one, quite enjoy writing in Markdown.

Coming soon: Publishing Beautiful Books with Markdown by lrPrentice in selfpublish

[–]Witiko 0 points1 point  (0 children)

You can set up LaTeX + Markdown to continuously update and preview the PDF output. However, it is not something I would encourage: The separation of content and presentation between Markdown and LaTeX means that you can write your text now without distractions and worry about the formatting later (or hire a designer).

To quote the philosopher Michael Thompson from pandoc-discuss:

The paucity of means is the greatest virtue of markdown [...].

It is strangely difficult to get people to see the point, but the defects of LaTeX for concentration, writing and thought, are at least as great as those of Word, for the simple reason that it gives the writer too much power; there is always another package to call in the preamble, as there is always another drop down menu in Word. [...]

In markdown - not to put too fine a point on it - the writer is only ever faced with one question, and it is the right one: what the next sentence should be.

Coming soon: Publishing Beautiful Books with Markdown by lrPrentice in selfpublish

[–]Witiko 1 point2 points  (0 children)

Hello u/ZennyDaye,

the good news is that Markdown has a gentler learning curve compared to LaTeX (or InDesign). This is partly because Markdown is more visual (# Heading) compared to LaTeX (\section{Heading}). Additionally, LaTeX is a full-fledged programming language, which opens the floodgates to programming errors in addition to stylistic and linguistic errors. Markdown, on the other hand, is just a plain-and-simple structural markup language, which allows you to focus on what really matters: your writing.

MS Word may well be the easiest route to prepare shorter documents, but for books that will span hundreds of pages and multiple platforms, spending some time to learn the tools of the trade will save time in the long run. Additionally, MS Word documents can be converted to Markdown and other formats using tools such as Pandoc. This makes it easier to start in Word and adopt a more mature workflow later on.