[HN Gopher] Emacs: ffmpeg and macOS aliasing commands
       ___________________________________________________________________
        
       Emacs: ffmpeg and macOS aliasing commands
        
       Author : xenodium
       Score  : 36 points
       Date   : 2022-12-18 14:58 UTC (8 hours ago)
        
 (HTM) web link (xenodium.com)
 (TXT) w3m dump (xenodium.com)
        
       | patchtopic wrote:
       | is this for cutting a whole documentary in ffmpeg?
       | 
       | https://www.youtube.com/watch?v=9kaIXkImCAM
        
       | taviso wrote:
       | For non-emacs users, I'm aware of navi which is a similar editor-
       | independent solution.
       | 
       | https://github.com/denisidoro/navi
        
       | p4bl0 wrote:
       | My personal method is to type "ffmpeg" and then hit Ctrl+R
       | repeatedly until I make it to the last time I used it to do what
       | I want to do again now, and then adapt the command from history
       | to my current needs.
       | 
       | It's not very efficient, but I don't feel it needs to be, and it
       | requires no particular setup (except setting Bash to keep history
       | forever but that's something useful I would do anyway for other
       | use cases).
        
         | xenodium wrote:
         | Ah, yes. This served me fairly well for some time. However, I
         | also needed to remember the actual tool I used for the job. Was
         | it ffmpeg? ffprobe? gifsicle? was it ImageMagick's convert? Not
         | too bad if these are the only tools, but I also use pandoc,
         | BluetoothConnector, pdftotext, qpdf, multiple AppleScripts,
         | qrencode, system_profiler, fb-rotate, duti, sips, git... Bash
         | history also remembers failed attempts, so I need to filter
         | those out as I recall the successful one...
         | 
         | Wrapping the winning command with a memorable function makes it
         | a bit easier for me to recall the right incantation via fuzzy
         | searching. For example: "set default" (resolves to dwim-shell-
         | commands-macos-set-default-app) vs "duti" (which I can never
         | remember).
        
         | gumby wrote:
         | Why not do `history | grep ffmpeg`? Each line will be prefixed
         | with its place in the history ("445 ffmpeg --whatever") and you
         | can just press `!445` to run it.
        
         | tempodox wrote:
         | By creating/editing `~/.inputrc` you can customize history
         | navigation in bash. Enter `help bind` in bash to see an
         | overview or consult [1].
         | 
         | A line like                 "\e[A": history-search-backward
         | 
         | only shows history entries that start with the current text
         | when you hit cursor-up, for instance.
         | 
         | [1] https://www.gnu.org/savannah-
         | checkouts/gnu/bash/manual/html_...
        
         | BeetleB wrote:
         | Ctrl+R combined with fzf is your friend :-)
        
           | michaelcampbell wrote:
           | Amen to that, I use almost nothing else these days except for
           | when I have a new bespoke command I've never typed before.
           | Even then fzf helps since I rarely am typing something
           | COMPLETELY new.
        
       | nonoesp wrote:
       | I use Typinator expansions with the input video path (from the
       | clipboard) as a variable to perform common ffmpeg operations,
       | such as downsize, speed up, extract audio, strip audio, export
       | frames to create GIF animations, or encoding as MP4.
       | 
       | Typinator lets you use what's on the clipboard but also add
       | scripting (say, Python or JavaScript) when certain parameters
       | need to be calculated, like sizes or names.
        
       | BeetleB wrote:
       | For things like this, I utilize the Babel feature in Org mode.
        
       ___________________________________________________________________
       (page generated 2022-12-18 23:01 UTC)