this post was submitted on 11 Jul 2024
703 points (98.9% liked)
linuxmemes
21291 readers
980 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
Its always bothered me that a language meant to get rid of formatting there seems to be a lot of fucking formatting. There's no way to change the way things look outside of explicit formatting (like themes). It's basically all formatting.
And it's a fucking mess. How in the fuck do I make titles? What about subtitles? Why is there no paragraph spacing? What's the point of \title if it's completely indistinguishable from other text?
I want a markdown editor that supports math LaTeX and a ton of plugins. Markdown is dead simple for a reason.
I see a lot of strange takes around here, and honestly cannot understand where you are coming from. Like really: I've written several 100+ page documents with everything from basic tables, figures and equations, to various custom-formatted environments and programmatically generated sections, and I've never encountered even a third of these formatting issues people are talking about.
You literally just \documentclass[whatever]{my doc type}, \usepackage{stuff} and fire away. To be honest, I've seen some absolutely horrifying preambles and unnecessary style sheets, and feel the need to ask: How are you people making latex so hard?
I've used LyX with good results, it's a GUI that abstracts away many of the complexities of latex.
I believe Joplin has latex math support, check it out.
Your editor shoul show you \title as another colour
And subtitle would be \large after title line
It is all formatting rules. But eliminates formatting the body text.
At least you know output will be same, not like MS Word
Oh thank goodness, body text is notoriously the hardest thing to format in a document
If you had seen some of the Word documents I have, you would not joke about that. People can really f-up text bodies.
Example: one guy wanted to keep two paragraphs together. He did not know about the necessary formatting option, but he knew that chapter titles did what he wanted. So he made the first paragraph a title and just reset font, size, etc to resemble a normal text. F-ed up quite some things...
Okay now what would happen if you made him use LaTeX?
I don't know if that person would have the intellectual capacity to actually understand the very concept of TeX: Writing a source and compiling it into a document. That idea would probably fry his mind.
That's just an effect of shitty software that does too much (and yes I'm advocating for a simpler Word or something. Markdown is fine for 95% of use cases.)
Guess what? I have moved my large text layouts over to HTML. Creating printed TOCs in a PDF takes some effort, but once I got that under control, it worked. Takes a makefile, though, and a bit of discipline in the HTML file, but the result is surprisingly good.
I’ve come to that conclusion, too. If only printing support were better, I wouldn’t write anything but HTML.
Have you tried weasyprint? It turns .html into .pdf. Then I use a script with pdfinfo with the -dests option to get the page numbers of the chapters, mixes it with chapter titles from the .html file to create a ToC, which, in turn, gets included into the .html file again - just like TeX does it.
This is helpful in an environment where inputs are either HTML or EPUB files, and output is PDF for printing, HTML for the web site, and/or EPUB-formate.
I haven’t. Thanks for the tip. This might come in handy when we need to create automated documents again.
Anything you put that amount of effort into should be good, as long as you actually care about it.
Lmao the hits keep coming