b3lm0nt
Joined 3 years ago
Joined 3 years ago
Because the technologies we had were good enough. It turned out that very few people needed to cross an ocean in three hours instead of six hours. On my way to this conference, I flew from Switzerland to San Francisco. It took eleven hours and cost me around a thousand dollars. It was a long flight and kind of uncomfortable and boring. But I crossed the planet in half a day!
Being able to get anywhere in the world in a day is really good enough. We complain about air travel but consider that for a couple of thousand dollars, you can go anywhere, overnight.
The people designing the planes of tomorrow got so caught up in the technology that they forgot to ask the very important question, “what are we building this for?”
Shuffleboard At McMurdo: https://idlewords.com/2016/05/shuffleboard_at_mcmurdo.htm
IMO you don't need a special tool to manage your home directory / dotfiles. Git is the tool. Your home directory is a repo with a .git directory like any other repo. No other tools; no symlinks; nothing else. Commit what you want and gitignore the rest. I've done this since 2008.
Never had a problem with it.
Being tied to either EMacs or an enterprise solution like LispWorks to get the full language experience was ultimately a non-starter. I’d love for someone to build an alternative CL development experience that could work in a wider range of text editors and IDEs.
There is a lot to learn from CL, but I think it can be hard to access for most developers.
Plus, it makes my home office feel more in tune with my profession. I like to see the books on the shelf and leaf through them while waiting for my CI to build.
Really looking forward to the 3rd edition of Absolute OpenBSD.
- LAMP (Linux, Apache, MySQL, PHP)
- CGI programming (/cgi-bin/)
- HTML, CSS, JS (with XMLHttpRequest to avoid full page reloads)
- AOLServer with Tcl (still developed as NaviServer)
- FTPing your HTML and CSS directly to the server
HTMX in particular is decidedly non-Lindy.
Approx. 12 different AWS services and 30+ instances...
Second point: to resolve the issue you're running into, remove these lines from the groff file to allow the default margins for PDF rendering to occur.
\# Set the line lenth to \nl
.ll \nl
There can occasionally be some strange behavior with the macros when different output devices are used (some options are ignored, some may have unexpected consequences). I took a look at the PDF output using my file directly, and it looks like the em sizing for gropdf is different from the grotty implementation, causing some overflow. (Maybe the font needs to be set explicitly before setting the line-length? Not sure).Using a different unit of measurement (like inches or points) may be a better option for PDF files: https://www.gnu.org/software/groff/manual/html_node/Measurem...
Bonus note: you can confirm the final output device that will be used by a groff command by adding the -V option. Example:
groff -Tpdf -V examaple.groff
Outputs: troff -Tpdf example.groff | gropdf
Using -Tascii instead will produce: troff -Tascii example.groff | grotty
Ref on output devices: https://www.gnu.org/software/groff/manual/html_node/Output-D...* Edit: See 2b3a51's response for a better explanation.