And combined with -E, it'll quit immediately if the output is smaller than the terminal size.
...And combined with some of the other options in the post, my go-to has been "less -SEXIER" for a long time. Specifying E twice doesn't seem to do anything except make this easier to remember.
I recommend -FX instead of -EX. They both quit immediately if the output is smaller than the screen size, but -FX does not quit if the output is larger and you jump to the end of a large file, so you can continue to do things like scroll back or search.
git uses "less -FRX" by default. This is how I learned about -F.
(To be pedentic, git uses "LESS=FRX less", which accomplishes the same thing.)
I hate -E. Quitting immediately does not do good things to my muscle memory. I’m using to hitting q to quit less when I am done. Now the q key becomes part of the input to the shell prompt (or worse if there’s a different tool invoking less and now q might be interpreted differently by that tool). I value the consistency of user interaction more than saving a keystroke.
With my mortgage, interest is monthly on the remaining principal and paying extra in a month is entirely on the principal - it reduces the total interest paid, so the bank gets less.
The idea that you pay the interest up front is a very common misunderstanding of how mortgages work and more broadly the concept of an amortization schedule.
String concatenation isn't usually considered a "formatting style", that refers to the other three rows of the table which use a template string and have specialized syntax inside it to format the values.
More specifically on that last point, I remember reading something like Google's biggest contribution hardware-wise was using lots of cheap, easliy-replaced distributed storage with redundancy instead of expensive large singular storage with error-correction? Or maybe it was memory and not storage. Whatever it was I remember them not caring as much about error correction as others, and being able to use relatively cheap hardware because of it.
Given the audience here vs the general population, I can't help but wonder if it's just the alternate search engines like DuckDuckGo/Kagi/Bing that are losing search traffic. From the population sizes even the alternate ones that are Google-based might just not be enough to be visible in Google's numbers.
Babylon 5 was mostly in order, if you want to see something really screwed up check out the spinoff Crusade. On top of what the network did it was written more serially than Babylon 5 was.
I actually read their comment as "vibe vibe live" which combined with the unknown terms in the next line (a reference to Dune combined with something else, I guess?) made GGP's question fit quite well.
Personal guess based on the impression I get from my parents' TV: You know how when you pause video while something is moving quickly, that object is blurred in the frame? Motion smoothing has that to work with, and causes the blur to persist longer than it should, which is why it looks bizarre - you're seeing motion blurs for larger movements than what's actually happening. Like the object should have moved twice the distance for the amount of blur, but it didn't. Something recorded and replayed at a high framerate wouldn't have this problem.
...And combined with some of the other options in the post, my go-to has been "less -SEXIER" for a long time. Specifying E twice doesn't seem to do anything except make this easier to remember.
reply