QProcessEnvironment documentation typo fix
Task-number: QTBUG-45985 Change-Id: I42de961ca6d57847c135abd8395494d0e416ab05 Reviewed-by: Sze Howe Koh <szehowe.koh@gmail.com>bb10
parent
24dc597386
commit
925822eca5
|
|
@ -127,7 +127,7 @@ QT_BEGIN_NAMESPACE
|
|||
Unix environment allows both variable names and contents to contain arbitrary
|
||||
binary data (except for the NUL character). QProcessEnvironment will preserve
|
||||
such variables, but does not support manipulating variables whose names or
|
||||
values are not encodable by the current locale settings (see
|
||||
values cannot be encoded by the current locale settings (see
|
||||
QTextCodec::codecForLocale).
|
||||
|
||||
On Windows, the variable names are case-insensitive, but case-preserving.
|
||||
|
|
@ -528,7 +528,7 @@ void QProcessPrivate::Channel::clear()
|
|||
QProcess can merge the two output channels, so that standard
|
||||
output and standard error data from the running process both use
|
||||
the standard output channel. Call setProcessChannelMode() with
|
||||
MergedChannels before starting the process to activative
|
||||
MergedChannels before starting the process to activate
|
||||
this feature. You also have the option of forwarding the output of
|
||||
the running process to the calling, main process, by passing
|
||||
ForwardedChannels as the argument. It is also possible to forward
|
||||
|
|
@ -1266,7 +1266,7 @@ QProcess::InputChannelMode QProcess::inputChannelMode() const
|
|||
/*!
|
||||
\since 5.2
|
||||
|
||||
Sets the channel mode of the QProcess standard intput
|
||||
Sets the channel mode of the QProcess standard input
|
||||
channel to the \a mode specified.
|
||||
This mode will be used the next time start() is called.
|
||||
|
||||
|
|
@ -2311,7 +2311,7 @@ void QProcess::setArguments(const QStringList &arguments)
|
|||
The process may not exit as a result of calling this function (it is given
|
||||
the chance to prompt the user for any unsaved files, etc).
|
||||
|
||||
On Windows, terminate() posts a WM_CLOSE message to all toplevel windows
|
||||
On Windows, terminate() posts a WM_CLOSE message to all top-level windows
|
||||
of the process and then to the main thread of the process itself. On Unix
|
||||
and OS X the \c SIGTERM signal is sent.
|
||||
|
||||
|
|
@ -2507,7 +2507,7 @@ QT_END_INCLUDE_NAMESPACE
|
|||
|
||||
This function does not cache the system environment. Therefore, it's
|
||||
possible to obtain an updated version of the environment if low-level C
|
||||
library functions like \tt setenv ot \tt putenv have been called.
|
||||
library functions like \tt setenv or \tt putenv have been called.
|
||||
|
||||
However, note that repeated calls to this function will recreate the
|
||||
list of environment variables, which is a non-trivial operation.
|
||||
|
|
@ -2537,7 +2537,7 @@ QStringList QProcess::systemEnvironment()
|
|||
It is returned as a QProcessEnvironment. This function does not
|
||||
cache the system environment. Therefore, it's possible to obtain
|
||||
an updated version of the environment if low-level C library
|
||||
functions like \tt setenv ot \tt putenv have been called.
|
||||
functions like \tt setenv or \tt putenv have been called.
|
||||
|
||||
However, note that repeated calls to this function will recreate the
|
||||
QProcessEnvironment object, which is a non-trivial operation.
|
||||
|
|
|
|||
Loading…
Reference in New Issue