I thought I’d share some findings and start a discussion. This seems like a silly thing to write: I’m attempting to get my some of my reviews completed while doing light cardio on stationary machines (treadmill, bike, elliptical …) to minimize risk of being run over. I’m sure it’s been attempted before and was wondering about other people’s experiences. I want to minimize risk of injury, hence my choice of stationary machines. While reading the cards there’s still a risk of losing balance on a treadmill or elliptical, so TTS (text-to-speech) helps in this situation. Many of my cards have images in certain fields as part of the question or answer which will not work with TTS. To remedy this I created 2 filtered decks: TTS (new) and TTS (due). The main idea with these decks is that certain fields are not vital to the question or answer on any card and thus they may contain images. I never want cards with images in the question/answer to be in this deck because it means exercise is interrupted so I can suspend the cards. Thus a whitelist approach is taken with the search queries. For TTS (new):
(is:new) (-"Deck:~Graveyard*") ("-*<img*" or "Extra:*<img*" or "Pixorize:*<img*" or "First Aid:*<img*"or "Sketchy:*<img*" or "Additional Resources:*<img*")
This gets new cards that aren’t in my “~Graveyard” deck (a “hall of shame” deck in which my many previous bad ideas reside). It ignores cards with images (utilizing the <img HTML tag (trailing > ignored because tag attributes such as src can be in any order)) but then adds cards if they have images in the fields of “Extra”, " Pixorize", “First Aid”, or “Sketchy” (yes I study AnKing).
Similarly, TTS (due):
(is:due) (-“Deck:~Graveyard*”) ("-<img" or “Extra:<img” or “Pixorize:<img” or "First Aid:<img"or “Sketchy:<img” or “Additional Resources:<img”)