From a037f7b4647c07d9f33bc849fd6f0ae3e3422754 Mon Sep 17 00:00:00 2001 From: wm4 Date: Thu, 23 Oct 2014 19:11:31 +0200 Subject: terminal: strictly don't read terminal input if stdout is not a terminal Doing that doesn't make sense anyway: it's meant for interactive input, and if the output of the player is not on the terminal, how will you interact with it? It was also quite in the way when trying to read verbose output with e.g. less while the player was running, because the player would grab half of all input meant for less (simply because stdin is still connected to the terminal). Remove the now redundant special-casing of pipe input. --- options/parse_commandline.c | 4 ---- 1 file changed, 4 deletions(-) (limited to 'options') diff --git a/options/parse_commandline.c b/options/parse_commandline.c index 254dc3cba7..f82706a52a 100644 --- a/options/parse_commandline.c +++ b/options/parse_commandline.c @@ -257,10 +257,6 @@ int m_config_parse_mp_command_line(m_config_t *config, struct playlist *files, process_non_option(files, file0); } talloc_free(tmp); - - // Lock stdin if it will be used as input - if (bstrcmp0(file, "-") == 0) - m_config_set_option0(config, "input-terminal", "no"); } } -- cgit v1.2.3