![]() Manual system independent way to specify it (so the default value of Solution 3: default to platform specific desktop, but provide no Personally I would not like making file name args that complex. Maybe the syntax should be a bit different to avoidĬonfusion with the shell mechanism. Interpreted by the -screenshot-template option only. We could add a screenshot template format specifier, though, which is Having something expanded, and may even cause security issues. This would make it very hard or impossible to specify paths without Suggestion then: property expansion in all file name options? So Thing is rather how to specify such paths without adding a complex Ignoring this and implementing it the easy way might be fine, but on the other hand could lead to confusion if the user actually has a configuration which we didn't predict. Linux has relatively complicated rules to determine the desktop directory: So solution 3: default to platform specific desktop, but provide no manual system independent way to specify it (so the default value of the option would be computed at startup)?Īm um 13:54 schrieb wm4 isn't ~/Desktop even correct on Windows? Not sure if any locales translate it.īoth OSX and Windows have API calls to retrieve the actual desktop directory. Suggestion then: property expansion in all file name options? So $ would always be the desktop? Or, as extension to ~, ~desktop/ to mean the desktop? Thing is rather how to specify such paths without adding a complex language for file names. Reply to this email directly or view it on GitHub. I'd say just expand shell stuff yourself when putting it into your config dir ) Not sure what to do, maybe just add a format specified or a property that returns the home directory? But then the syntax would still be different. causes weird issues like: what if you really want to pass a filename containing "~"? ![]() requires code (which could be incorrect, is bloat, etc.), and 2. It would require us to do shell expansion, which 1. And it gives us a nice way to set platform dependent screenshot dirs.ītw: isn't ~/Desktop even correct on Windows? Not sure if any locales translate it.Īm um 01:36 schrieb wm4 a different issue. I actually like the idea to have ~ work in config files too. However, if we want this, we should do it consistently for all filename options. Relative paths can always be prefixed by. It is only ever handled at the beginning of the path, so no absolute paths (starting with /) can ever be hit by it. I would try to keep it short, like "mpv_screenshot_%n". They could contain filenames, dates, playback position - whatever makes sense. We also could change the screenshot filenames from "shot0001.jpg" to something else. Most users probably want to find their screenshots quickly to upload and post them somewhere. So mpv would upload the screenshots to my server.Įven if locally, the screenshots may end up deeply buried in some neatly organized file structure that the user has to navigate to first again or in a totally messy Downloads folder. I often play stuff from a remote server that is mounted via AFP. ![]() What if the file is not on the local filesystem? This would already not work with read-only media like DVDs. Or in the directory the played file is located? I would suggest that mpv tries to save screenshots to ~/Desktop/, since this exists on OS X and also on some (most?) Linux flavors and falls back to ~/ if there isn't a ~/Desktop/. I personally hate it when applications clutter my home dir. ![]() Alternatively, how about storing screenshots in the home directory (~) ![]()
0 Comments
Leave a Reply. |