this post was submitted on 25 May 2024
654 points (99.2% liked)

linuxmemes

21226 readers
89 users here now

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 members of the community for any reason.
  • 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, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     

    I usually use .bak... .old seems so... old.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] whotookkarl@lemmy.world 5 points 5 months ago* (last edited 5 months ago) (2 children)

    I like adding a backup function to .profile that can take a file or list of files as an argument and make a copy with a date suffix on the file name, and same date additional backups just add a character like ~ at the end. It's in version control, but if I'm testing a change it's just faster to restore the file from a copy in the same place.

    [–] lseif@sopuli.xyz 3 points 5 months ago

    i so agree. i have a script that copies all file arguments into the directory .backups/YYYY-mm-DD-HHMM/ ... handy for risky git operations too.

    [–] palordrolap@kbin.social 2 points 5 months ago

    Obligatory note that /etc/profile and ~/.profile are only run by login shells, and many terminal emulators do not execute a login shell by default.

    Unfortunately, there is no standard secondary place* that all shells execute, so check your chosen shell's manual for what it does run on startup and put your functions into one of those. Preferably one that goes in your homedir.

    Alternatively have that file source ~/.profile assuming that won't cause an infinite loop.

    * And not even a primary if you count *csh, but if you use those you have other problems.