Hi Stefano,
> I would like to see an "EXAMPLES" or "RECIPES" section in the manpage, > showing something like this: > Sure, I'll try to include this in the next release. Is the list below what you actually want, or just a randomly generated list? > # shows all tags for each ogg file in the current dir > lltag -S *\.ogg > > # show only a selected list of tags > lltag --show-tags artist,album,title,number *\.ogg > > # set an arbitrary tag (only with ogg vorbis or flac files) > lltag --tag foo=nil foo.ogg > > # delete the foo tag > lltag --tag foo= foo.ogg > > # set the ALBUM, ARTIST and GENRE tags values of the ogg files in the > # current dir > lltag --artist "Queen" --album "Innunendo" --genre "rock" --comment="very > cool" *\.ogg > > # to change instead the "artist, "album" and "genre" values use instead > lltag --tag artist="Queen" --tag genre="rock" --tag album="Innuendo" *\.ogg > > # only change the filename using the tags values specified in <format> > lltag --no-tagging --rename <format> foobar.ogg > > # clear all tags > lltag --clear *\.ogg > I could also put that on the webpage. Right now, I have an How-To at http://home.gna.org/lltag/howto. But, it might be good to improve the Basics section. By the way, why do you escape all the dots in the command lines above? > Maybe a good idea could be to use the Pod::Usage package to let you > embed in the script file itself all the relevant documentation and > let it automatically generate the manpage. > I thought about that in the past. But, I did not see the real advantage of doing so. It might be good to have to doc near the code. But, since lltag is modularized in multiple small perl modules to make the code more easy to read, I am not sure it will be easy to put the doc in there. I'll think about it. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
