

Think of them as operating on the whole column at once.
For example LAG would be like selecting a whole column in excel and copy pasting it one row down


Think of them as operating on the whole column at once.
For example LAG would be like selecting a whole column in excel and copy pasting it one row down
No, I’ve removed the indentation of the first ul
Too much list indentation. Cool glow effect


It would, but it does not have SATA. You can find much cheaper computers that do have it


For a server like this 4GB of DDR4 is enough. And that is cheap still.


That’s a good point, months would need new names. And dates should have some other format, maybe a F prefix: FYYYY-MM-DD


Ah, another oppurtunity to bring up international fixed calendar that could reuse the calendar every year!


Let’s say I manage an engineering department. How could I promote people who build simple software?


This looks … great.
Ha. Lol. That’s bad
Context: this happens if you use patch(1) with patches generated by git format-patch. If you do, you should be using git am instead.


I wouldn’t call it state-of-the-art, but rather maybe most-straightforward or database-agnostic or as-simple-as-they-get


Yes. Highlighting, these selection actions and symbol detection all work with tree-sitter grammars. The whole premise of the editor is a modern-modal-editing with tree-sitter grammars.


I’m a bit surprised helix editor is not mentioned. It is based on tree-sitter grammars and allows for stuff like select-around-function or select-around-argument, to use grammar in the code navigation. Pretty wild and useful.


You are either a crazy nutjob or a genius thinker. Interesting idea
Wikipedia to the rescue:
However, some formats (ex., HDV, DVCPRO HD) use non-square pixels internally for image storage, as a way to reduce the amount of data that must be processed, thus limiting the necessary transfer rates and maintaining compatibility with existing interfaces.
Actual displays do not generally have non-square pixels, though digital sensors might;
TLDR; some formats use non-square pixels for reducing file size, some digital sensors has non-square pixels.


Does anyone know why anyone would want to encode their video using PAR != 1? Reducing the file size, by storing less pixels in one dimension, but not the other?


Did Nextcloud get any more performant in the last 5years, or did the Austrian ministry shoot itself in the foot?
This looks awesome