personally, I use: -g=podcast
I've actually added that exclusion to my top level Audio and Video viewschemes.
Though I don't see anything wrong with using [feed url]. There are often many ways to achieve your goal with MC, sometimes, there are pros and cons involved with different routes, but in this case, I don't see any difference and the end results are the same.
tips:as mentioned above, if you don't use formatting around the search term, then "contains" is implied. if you have spaces in your string, you need to use double quotes.
[name]=single
[name]="two words"
If you wrap the term in square brackets, it implies "precisely matches"
[name]=[single]
[name]=[two words]
If you combine quotes and square brackets, it implies "ends with"....
[name]="single]
[name]="two words]
or begins with...
[name]=[single"
[name]=[two words"
Go to tools > options > library and find "Name" in the list, select it, then hit the edit button:
Have a look in the lower left corner under "search".
Every field that has the "default search field" ticked will be searched if you simply type a search term into the search box, and don't specify a [field name] to search by.
Also, the keywords field is
extremely useful if you want to get into smartlist building. Taking a few seconds to configure keywords for often used fields will save you a bundle of typing in the future.
In the [name] example above, you can see that n is a keyword, which means that...
[name]=single and n=single are exactly the same search.
A few that I've added are:
- mt= for [media type]
- ft= for [file type]
- fnn= for [filename (name)]
- fnp= for [filename (path)]
- fn= for [filename]
- aaa= for [album artist (auto)]
- lp= for [last played]
- np= for [number plays]
- tn= for [track #]
-marko.