The below is my usecase:
("mid3iconv -e gbk <file>"
:command "mid3iconv"
:arguments ("-e" "gbk" name))
There are garbled characters in many Chinese mp3 file's tags,
so I need run "mid3iconv -e gbk mp3-file" to convert.
If I run in bash, I need to find the file, convert and rebuild emms cache ...
If we have this pipe function, I just select all track and run
emms-tag-editor-pipe command,
then select "mid3iconv -e gkb <file>" pipe, all works will be auto finished.
by the way, "mid3iconv -e gbk <file>" pipe included in the patch just an
example to
show how emms-tag-editor-pipe to work :-)
other example :-)
("scp <file> feng@localhost:/home/feng/Music/<artist>/>"
:command "scp"
:arguments
(lambda (track)
(let* ((file (emms-track-name track))
(artist (emms-track-get track 'info-artist "Misc"))
(dir (concat "feng@localhost:/home/feng/Music/" artist)))
(list file dir))))
At 2020-11-11 00:57:00, "Yoni Rabkin" <[email protected]> wrote:
>
>Can you give me an example of how the pipe functionality would work?
>Under which circumstances would one use this, as opposed to a shell
>command?
>
>Your explanation will be valuable especially in the context of writing a
>manual entry explaining how the feature works.
>
>Thanks.
>
>--
> "Cut your own wood and it will warm you twice"
