* The main function does some setup that includes reading parameters from
* the command line to change its behaviour and test different results.
* These are:
- * @li -t <some_num> maximum number of threads to run at the same time.
- * @li -p <some_path> adds @c some_path to the list used by the feedback jobs.
+ * @li -t \<some_num\> maximum number of threads to run at the same time.
+ * @li -p \<some_path\> adds @c some_path to the list used by the feedback jobs.
* This parameter can be used multiple times.
- * @li -m <some_num> the number of messages to process before the program is
+ * @li -m \<some_num\> the number of messages to process before the program is
* signalled to exit.
*
* Skipping some bits, we init Ecore and our application data.
/**
* Change the HTTP version used for the request
+ * @param url_con Connection object through which the request will be sent.
* @param version The version to be used
* @return EINA_TRUE on success, EINA_FALSE on failure to change version
* @since 1.2
* Use this function to add a SSL PEM private key
* Simply specify the key file here to use it in the server object for connecting or listening.
* If there is an error loading the key, an error will automatically be logged.
+ * @param svr The server object
* @param key_file The path to the key file.
* @return EINA_FALSE if the file cannot be loaded,
* otherwise EINA_TRUE.
* @brief Set the "i demand attention" flag on a canvas window
*
* @param ee The Ecore_Evas
- * @param demand_attention The flag state to set
+ * @param demand The flag state to set
*
* A window may demand attention now (eg you must enter a password before
* continuing), and so it may flag a window with this.
* Synchronously modifies the regions in the following manner:
* If @p repair is @c XCB_NONE:
* 1) parts = damage
- * 2) damage = <empty>
+ * 2) damage = \<empty\>
* Otherwise:
* 1) parts = damage INTERSECT repair
* 2) damage = damage - parts