ulterno

joined 1 week ago
[–] ulterno 1 points 2 days ago

But! But! Wikipedia is not a reliable source! Uwaaan! /s

[–] ulterno 6 points 2 days ago* (last edited 2 days ago)

At this point, just use a ladder. It'd be safer too.

That would also make space for a slide-down pole, which would be faster.

[–] ulterno -1 points 2 days ago

Docker is not running on client machine.

[–] ulterno 2 points 2 days ago* (last edited 2 days ago)

Did you not know?
You can simply select all files you want to commit, in the File Manager, Ctrl+C, then paste in the terminal and it will automatically add all those file names (full paths) separated with spaces at the cursor. At least in KDE: Dolphin -> zsh + Konsole it does.

And sure, it might look like 2 extra steps, but you will still be clicking around a lot in case of a GUI anyway.

I tend to just type partial filenames and use tab completions, which are also pretty configurable. And the only dissatisfaction I have rn, is that I don't have zsh module for completions with pascal case and snake case.

[–] ulterno 5 points 2 days ago

That's definitely how it is seen.
If I were to see "Discard Changes" anywhere in a dialogue, I would assume it will discard whatever changes I made in that dialogue. In this case, probably some source control related changes. If it were to say "Warning: This will Discard ALL changes!!!", I might do a double take, but had I never used git CLI before, I would still assume that at most it would discard "ALL" changes made in the current session.

For me personally, I would consider it more useful for it to say:

This action will delete the following files:
- followed
- by
- a
- list
- of
- files
- that
- would
- be
- deleted
Continue?

Which neither has to look like a warning, acting like you might be doing something you don't want to and also is much more useful for someone like me who wants to double check what exactly I am deleting.


Also, I have used git CLI before and apart from being able to see blame in the editor itself and maybe a better representation of tree, I don't feel the need to use any git GUI tool. Even when I tried, I realised it was slower and more finicky to use. So, it would stand to reason that it should be targetted towards people who don't use CLI (and might have never used git CLI).

[–] ulterno 2 points 2 days ago

Yes, e.g. I got the 're in blue and everything else light grey.

[–] ulterno 1 points 2 days ago

Is this guard supposed to be slacking off on the job?

It works on Firefox EndeavourOS

[–] ulterno 0 points 3 days ago (2 children)

At least that's what I aim for in Civ VI.
No idea about you

[–] ulterno 1 points 3 days ago

What if it were 10/100 Gb/s ?

[–] ulterno 7 points 3 days ago* (last edited 3 days ago)

For LibreOffice, I'd go with, worse and better at the same time.

  • I have just noticed, overtime, that it has some problems in some cases, where MS Office does better, while there are certain cases where it does better.

There are 2 major pain points though:

  1. Calc UI stutters when using the scrollbar with mouse click and drag.
  2. Adding images to files makes the whole thing way slower than acceptable.

I haven't used it for a few months though, so something might have changed. But the second issue specifically is a long time one.

On the other hand, the formula usages are much better in Calc. Also, the documents don't get wonky between versions as much as MS Office

[–] ulterno 10 points 3 days ago

Of course I visited the hospital for a CT scan.

Of course I'm not telling you to hit your head for fun.

This is just a fun story, not evidence for anything.

People have survived failed parachutes. Doesn't mean we can all be Alex Mercer.

[–] ulterno 2 points 3 days ago

That's why I keep a pen and paper. For power outages.

Apart from that, if there's light:

  • some exercise
  • kirigami
  • wash clothes (by hand)
  • eat random (edible) stuff which I would otherwise use to cook
    • cooking needs electricity

No light:

  • sleep
view more: ‹ prev next ›