242 points

Oh fuck. I’ll use this from now on. Except for if I won’t use it next week. Then I’ll forget about it because my memory is a damn sieve.

permalink
report
reply
121 points

Just take the next step and make a text file you dump all these commands into and then forget about in a week. When you randomly stumble across it years from now you’ll be able to say “wow, I could have used this 10 months ago if I remembered it existed!”

permalink
report
parent
reply
54 points

I make a separate text file per command so I can search them!

Which I dont.

permalink
report
parent
reply
33 points

I usually print these out and put them in a safe deposit box at a bank so I never lose them

permalink
report
parent
reply
12 points

We can store those text files in a terminal and search for them from the command line with man command!

permalink
report
parent
reply
3 points

I keep a persistent “sticky note” (in KDE) drop down on my top bar where I copy/paste important commands, scripts, etc.

I actually remember to use it sometimes.

permalink
report
parent
reply
12 points

Use a systemd timer to send yourself a reminder. Discoverd them recently myself and honestly liking them more than cron.

permalink
report
parent
reply
5 points

I feel you. It’s however gotten a lot better since I turned some of these commands into abbreviations. They’re aliases that expands in place, more or less. Fish has them natively, I personally use zsh-abbr.

permalink
report
parent
reply
2 points

Fish is super useful, but I usually only start it up if I’m having trouble finding or remembering a command.

permalink
report
parent
reply
3 points

Yeah, it’s a good shell. I’ve found the lack of compatibility with some bash tools to be inconvenient enough that I just went back to zsh and found alternatives for the parts that I liked about it. Works well enough for me.

permalink
report
parent
reply
1 point

Using a large shell history (currently at 57283 entries) along with readline (and sometimes fzf) has served me well over the past few yeas when trying to remember past commands.

permalink
report
parent
reply
115 points

me: systemd is not that bloated

systemd:

permalink
report
reply
55 points

You need a calendar and time handling anyways for logging purposes and to set timers correctly. It’s likely not that much extra work exposing that functionality.

permalink
report
parent
reply
17 points

No, UNIX philosophy demands that every single one of those things is one or more separate things and that half of them are poorly or not at all maintained. Just like God intended.

permalink
report
parent
reply
1 point

Finding the next super holiday is a core system feature I could survive without. 🎉

permalink
report
parent
reply
16 points

Try scheduling a cron tab job to run a task on dates defined that way.

permalink
report
parent
reply
3 points

But that’s not what I need and the world revolves around me…

permalink
report
parent
reply
13 points

I think this is for setting date oriented timers

permalink
report
parent
reply
99 points

Usually such things have a simple explanation. systemd does a lot with time and date, for example scheduling tasks. It’s quite obvious that it has this capabilities, when you think about it.

permalink
report
reply
45 points

Usually such things have a simple explanation. systemd does a lot with time and date, for example scheduling tasks. It’s quite obvious that it has this capabilities, when you think about it.

FTFY

permalink
report
parent
reply
7 points

Not that that’s bad when it’s stuff like this

permalink
report
parent
reply
-7 points

Yes it is.

permalink
report
parent
reply
1 point

Too much

But that has been a complaint for 10 years and it’s only gotten worse

I wouldn’t mind systemd if it weren’t for the fact that it was to be a startup system that promised to make everything easier and faster to startup yet managing systemd is a drag at best, and of it did one thing it’s making my systems boot up like mud

permalink
report
parent
reply
2 points

I feel like the glued together collection of scripts was way worse to manage than systemd.

permalink
report
parent
reply
-2 points

I thought the same, but didn’t we already have things like chron syntax for this? Systemd didn’t have to build its own library.

permalink
report
parent
reply
14 points

Systemd’s method is more powerful than Cron syntax.

permalink
report
parent
reply
7 points

Aight, didn’t know that. I cannot yet imagine any scheduled task that would require anything more advanced than cron (or a similar standalone syntax), but I’ll just trust you with that one.

permalink
report
parent
reply
6 points

Can you tell Cron to catch up on the things that should’ve happened but didn’t because the system was off?

permalink
report
parent
reply
7 points

I think fcron and anacron can do that

permalink
report
parent
reply
87 points

systemd is a great operating system, it just lacks a decent text editor.

permalink
report
reply
36 points

Good thing it’s editor agnostic so everybody can do the right thing in the end and choose nano

permalink
report
parent
reply
40 points

Funny way to misspell vim

permalink
report
parent
reply
13 points

Micro anyone? :D

permalink
report
parent
reply
2 points

Enough people mention it that I’ve jumped over to helix

permalink
report
parent
reply
12 points

alias systemd-texted=micro

permalink
report
parent
reply
1 point

Have you tried emacs with evil mode? It’s a bit slow, not as slow as VS code or anything, but not really fast. But it’s basically neovim but you get to use lisp to configure it instead of lua

permalink
report
parent
reply
60 points

Thanks! I hate this. 🖤

permalink
report
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

Hint: :q!


Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules
2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like “every user of thing”.
  • Don’t get baited into back-and-forth insults. We are not animals.
  • Leave remarks of “peasantry” to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
4. No recent reposts
  • Everybody uses Arch btw, can’t quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.

 

Please report posts and comments that break these rules!


Important: never execute code or follow advice that you don’t understand or can’t verify, especially here. The word of the day is credibility. This is a meme community – even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don’t remove France.

Community stats

  • 7.5K

    Monthly active users

  • 1.4K

    Posts

  • 76K

    Comments