this post was submitted on 25 Aug 2025
1557 points (98.9% liked)

linuxmemes

27042 readers
315 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 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.
    • 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, no politics, no trolling or ragebaiting.
    • 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.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    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.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    1557
    siempre lo hago (eviltoast.org)
    submitted 6 days ago by AleMegadeth@eviltoast.org to c/linuxmemes@lemmy.world
    209 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] IcedRaktajino@startrek.website 23 points 6 days ago* (last edited 6 days ago) (5 children)

    Pretty much, yeah.

    Rather than jot down in a text file the various ffmpeg commands I use frequently...

    Raktajino@laptop:~/Downloads$ history | grep ffmpeg
   12  sudo apt install audacity gimp ffmpeg mplayer
  184  history | grep ffmpeg
  215  ffmpeg -i source.mkv -ss 629 -t 7 out.mkv
  217  ffmpeg -i out.mkv -s 0.5 -vf scale=1280:720 out.mp4
  218  ffmpeg -i out.mkv -ss 0.5 -vf scale=1280:720 out.mp4
  231  ffmpeg -i out.mp4 -vf "subtitles=out.srt" final.mp4
  503  ffmpeg -i toofat.wav toofat.mp3
  ...
  682  history | grep ffmpeg
  684  ffmpeg -i 1.gif -i 2.gif -filter_complex "[1:0] [2:0] concat=n=2" out.gif
  685  ffmpeg -i 1.gif -i 2.gif -filter_complex "[1:0] [2:0] concat=n=2:v=1" out.gif
  686  ffmpeg -i 1.gif -i 2.gif -filter_complex "[1:0] [2:0] concat=n=2:v=1" -map '[v]' out.gif
  687  history | grep ffmpeg
  688  ffmpeg -i 1.gif -i 2.gif -filter_complex "[0:0] 12:0] concat=n=2:v=1" -map '[v]' out.gif
  689  ffmpeg -i 1.gif -i 2.gif -filter_complex "[0:0] 1:0] concat=n=2:v=1" -map '[v]' out.gif
  690  ffmpeg -i 1.gif -i 2.gif -filter_complex "[0:0] [1:0] concat=n=2:v=1" -map '[v]' out.gif
  691  ffmpeg -i 1.gif -i 2.gif -filter_complex "[0:0] [1:0] concat=n=2"  out.gif
  694  history | grep ffmpeg
    [–] Ediacarium@feddit.org 11 points 6 days ago* (last edited 6 days ago) (2 children)

    I like how 'history | grep ffmpeg' shows up twice

    [–] IcedRaktajino@startrek.website 6 points 6 days ago

    I like how I was courageous enough to not fix the actual typos/failed commands in the actual history lol.

    [–] bdonvr@thelemmy.club 2 points 6 days ago (1 children)

    I'm begging you to use CTRL+R

    [–] PotatoesFall@discuss.tchncs.de 1 points 6 days ago (1 children)

    If you have a fzf or other plugin installed, great. the vanilla Ctrl R is kinda mid in most shells IMO

    [–] bdonvr@thelemmy.club 1 points 6 days ago (1 children)

    It's still lighyears ahead of hitting up forty times.

    [–] PotatoesFall@discuss.tchncs.de 1 points 5 days ago

    exactly, which is why history | grep can, in some cases, be better than vanilla Ctrl + R

    [–] cmnybo@discuss.tchncs.de 1 points 6 days ago

    You can also create aliases for frequently used commands. You can even put a function in an alias so it can accept arguments, but it would probably be better to just write a shell script at that point.

    [–] corsicanguppy@lemmy.ca 1 points 6 days ago* (last edited 6 days ago)

    You're gonna love once you start

    1. tagging your ffmpeg commands like do a thing # dothingname

    2. Just !?dothingname later to recall it and run it.

    Its a little easier to NOT accidentally !?alt and discover halt is matched first.