From 6174686bc346e24fd146a725a97d77e571ebf5b4 Mon Sep 17 00:00:00 2001 From: Reto Kromer Date: Sun, 10 Feb 2019 17:44:10 +0100 Subject: doc/faq: update macOS and URLs Signed-off-by: Gyan Doshi --- doc/faq.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/faq.texi b/doc/faq.texi index 58986cf332..8b165eb436 100644 --- a/doc/faq.texi +++ b/doc/faq.texi @@ -76,7 +76,7 @@ the gcc developers. Note that we will not add workarounds for gcc bugs. Also note that (some of) the gcc developers believe this is not a bug or not a bug they should fix: -@url{http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203}. +@url{https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203}. Then again, some of them do not know the difference between an undecidable problem and an NP-hard problem... @@ -516,7 +516,7 @@ in the ffmpeg invocation. This is effective whether you run ffmpeg in a shell or invoke ffmpeg in its own process via an operating system API. As an alternative, when you are running ffmpeg in a shell, you can redirect -standard input to @code{/dev/null} (on Linux and Mac OS) +standard input to @code{/dev/null} (on Linux and macOS) or @code{NUL} (on Windows). You can do this redirect either on the ffmpeg invocation, or from a shell script which calls ffmpeg. @@ -526,7 +526,7 @@ For example: ffmpeg -nostdin -i INPUT OUTPUT @end example -or (on Linux, Mac OS, and other UNIX-like shells): +or (on Linux, macOS, and other UNIX-like shells): @example ffmpeg -i INPUT OUTPUT