Yes, or one of the forks.
break a lot of backwards compatibility or radically change the current way of doing things
Plan 9. We can still have textual interfaces without emulating the ancient use of teletypewriters.
Permanently Deleted
The things I've read (admittedly mostly from the OpenBSD camp) from BSD devs, they seem to not worry about corporations building from their source that much, instead they actively try to get rid of GPL code because it isn't permissive enough for their standards.
Theo wrote "GPL fans said the great problem we would face is that companies would take our BSD code, modify it, and not give back. Nope—the great problem we face is that people would wrap the GPL around our code, and lock us out in the same way that these supposed companies would lock us out. Just like the Linux community, we have many companies giving us code back, all the time.
But once the code is GPL'd, we cannot get it back."
The short answer
People use ed because they want an editor. They don't want an emacsitor or vimitor. Those aren't even words.
The option to not set a root password and instead let the regular user use sudo seems to be mentioned in the installer for the first time around 2007, so it's been there for a while.
Also OpenBSD use different versions, I'm guessing their vi is the original since it can't handle utf-8. And iirc ex(1) is also a vim variant on Linux. I've never met anyone who actually uses ex though. ed(1) I think is just GNU ed. I am not certain about these versions though.
The original vi has not been maintained for many years. Most distributions, including Debian, Fedora, etc, use a version of Vim which (mostly) is similar to how Vi was.
From Fedoras wiki:
"On Fedora, Vim (specifically the vim-minimal package) is also used to provide /bin/vi. This vi command provides no syntax highlighting for opened files, by default, just like the original vi editor. The vim-minimal package comes pre-installed on Fedora."
From the vim-tiny package description on Debian:
"This package contains a minimal version of Vim compiled with no GUI and a small subset of features. This package's sole purpose is to provide the vi binary for base installations."
It is, they have the same text.
Nowadays vi is just a symlink to vim.tiny, so you're actually running vim (in vi mode).
https://www.maketecheasier.com/assets/uploads/2020/08/debian-install-set-password.png.webp
Third paragraph. I'm not trying to be a smart-ass, I also installed Debian a few times without seeing it.
The installer says this when it asks you to type a root password. I don't know why, but for some reason the information is both right there and easy to miss.
A good act does not wash out the bad, nor a bad act the good. Each should have its own reward.
The wave of the reddit protests is over, now lemmy must grow on its own merits rather than being "not reddit".
There's an old saying: "Linux users use Linux because they hate Windows. BSD users use BSD because they love Unix." Obviously this is not true for every individual user, but I think it describes a trend or pattern.
Have you tried setting the +tlig opentype feature in your font definitions?
I think it's a valid concern in this case.
Have you thought about the implications and consequences if we start banning non-violent expressions of opinions because someone else might find it disrespectful?
There is something "clunky" about the website, but to be fair, the first page has a big button to download the installer, which leads to a page where the first link is the version most people want, the second link leads to instructions how to get it onto a usb (or cd/dvd) for linux/windows/mac, and clearly visible a link to all the other versions of the installer that people might want, with explanations what they are for.
For me it's hard to put my finger on why the website is bad, all the information is there. I do agree that it just somehow feels bad, but I don't understand why.
I am not trying to gatekeep. It could be that I'm blind to why debian is hard to install, I think it's about the same as ubuntu or mint or fedora etc. Which means I'm not the right person to improve this area. I do want to lower the thresholds, and currently I'm helping out with that in other areas. This discussion started with the claim that it was hard to find the iso, which I disagree with, and now I'm not sure what we're disagreeing about.
Would a normie Windows user know how to install Windows on a computer without OS? Of course, this hypothetical user doesn't have to, because he/she probably bought a computer with Windows pre-installed. Is there any OS in the world that is easy to install if you don't know what an iso file is? Which measurement are we using when the claim is that Debian is difficult to install? What is an easy install?
New trick to make sure margin notes don't overlap.
OpTeX Tips and tricks section was updated with a macro that automatically makes sure that margin notes don't overlap. It's otherwise a problem when the margin notes are too close.
If you want to do it manually you can use \mnoteskip, but this is an automatic way.
What do you all use your shell account for?
Is it for mail, programming, irc, usenet, website, etc? I'm just curious what other people do when they log into sdfeu.
Easiest way to connect C64 to modern computer screen?
So, I recently got this C64 for free, and I've been wanting to test it. However, figuring out how to connect a monitor has led me to various forums with home-made adapters that require soldering, a 5-pin DIN to 4xRCA to...? My monitor has VGA and HDMI, etc, the usual modern inputs. Someone claimed that the voltages are different which will lead to artifacts and to put a resistor somewhere. I found some box thing from China that looks promising but it's around 150 usd.
What would you recommend for this? Is the expensive box my best bet?
I have no TV or anything that can input RF, just a computer monitor.
Dealing with widows (and orphans if we want).
Orphans and widows. On this subject Tschichold wrote:
"Doubtless all textbooks of typesetting warn that the exit line of a paragraph at the head of a book page must be avoided at all cost. /.../ Is there really nothing we can tighten a little, or space out perhaps? Possibly we can save a line at the beginning of the chapter by moving the first paragraph up? The best method is to simply shorten the preceding page by a line."
Bringhurst wrote:
"Balance facing pages not by adding extra lead or puffing up the word space, but by exporting or importing single lines to and from the preceding or following spreads. The same technique is used to avoid widows, and to extend or shorten any chapters that would otherwise end with a meager few lines on the final page."
In TeX we can set \widowpenalty (and \clubpenalty) to 10000 and if we have vertically stretchable material on the page the type area will get it's height, but lines will not match across the spread. Without strechable material that
A Pragmatic Approach to Paragraphs, by Philip Taylor
What's your method for dealing with underfull/overfull \hboxes and unacceptable badness in general?
LaTeX has the \sloppy command which IIRC sets \tolerance to 9999, and \emergencystretch to a large value. But the default \tolerance is 200 (I think), which is a big difference. It's very "either/or" when maybe there's a more optimal way.
For my native language (swedish) I've found that many issues arise because TeX doesn't find all the possible hyphenation points, so I usually spend time adding words to the hyphenation list.
But still, in any longer text there's usually a couple of paragraphs that just won't set right, I'm curious about your tricks or methods for dealing with them.
Quantum spaces: Designing pages on grids
This is a rather interesting presentation by Jean-Luc Doumont about placing content on a grid, or a subset of the grid. He's kind of taking this idea to the extreme.
A macro to visualize boxes
There's this guy called Stephan V. Bechtolsheim who wrote a series of books on TeX called "TeX in Practice". He's really good at the finer details of, well, everything.
In one of the books, he makes a macro to visualize boxes. It's built up over many pages and chapters with lots of small macros as building blocks. Because he's reusing these macros in different places, it makes a lot of sense.
However, when I wanted to use the box visualizing macro, I found that I had to look up and copy a lot of code to make it work. This was no fun, so I re-wrote it in a "flatter" way where it's just regular plain old macros.
I ended up with this:
undefined
\newdimen\linethickness \linethickness=0.4pt
\def\boxlines #1{%
\hbox{%
% Save original (argument) box
\setbox0 = #1%
% Place bullet at baseline and vertical align of the box
\setbox1 = \hbox{\hskip -2.5pt \lower 2.5pt \hbox{$\circ$}}%
\ht1=0pt \dp1=0pt \wd1=0pt
\box1
% Place a dashed line
Golden canon of page construction
Jan Tschichold and Raul Rosariva independently researched the layout of medieval books, and each came up with a method of construction. Rosarivas version (to the right) lends itself very well to a programmatic approach. We could implement it (in luaTeX) in a few lines like this:
undefined
% Page size (proportions 2:3) \pagewidth=150mm \pageheight=225mm % Undo 1 inch origin (personal preference) \pdfvariable horigin 0pt \pdfvariable vorigin 0pt % Inner margin \hoffset=\pagewidth \divide\hoffset by9 % Top margin \voffset=\pageheight \divide\voffset by9 % Type area width \hsize=\pagewidth \divide\hsize by9 \multiply\hsize by6 % Type area height \vsize=\pageheight \divide\vsize by9 \multiply\vsize by6
This is all well and good if we have vertically stretchable material on every page. But... if we want to do grid typesetting, we will quickly run into "Underfull \vbox (badness 10000)".
Let's say we've se