I use Fedora 8. Description of problem: The dbus-send manpage does not mention --reply-timeout and does not show that --print-reply takes an argument Version-Release number of selected component (if applicable): dbus-1.1.2-7.fc8 How reproducible: always Steps to Reproduce: 1.man dbus-send 2.dbus-send --help Actual results: dbus-help shows that there is --reply-timeout and that --print-reply takes an argument Expected results: --reply-timeout should be mentioned in the manpage and the argument of --print-reply should be explained.
(dbus/doc is a defunct project to design a documentation extension to D-Bus introspection; moving this to dbus/core.)
Created attachment 56746 [details] [review] [1/3] dbus-send.1: use bold and italic type consistently According to man-pages(7) * bold is for literal text, the name of the thing being documented, or the name of another man page * italic is for replaceable text, usually in all-caps * normal type (in the SYNOPSIS) is for special syntax like the [] indicating optional things Bug: https://bugs.freedesktop.org/show_bug.cgi?id=14005 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Created attachment 56747 [details] [review] [2/3] dbus-send.1, dbus-send: document --print-reply=literal consistently Bug: https://bugs.freedesktop.org/show_bug.cgi?id=14005 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Created attachment 56748 [details] [review] [3/3] dbus-send.1: document --reply-timeout Bug: https://bugs.freedesktop.org/show_bug.cgi?id=14005 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
In git: ssh://people.freedesktop.org/~smcv/dbus.git doc-dbus-send-14005
Looks all good to me text-wise. My groff-fu is non-existant however, so I can't say anything about the formatting changes. But it looks alright if I apply and build it. So I think this should be enough for a review.
Thanks, fixed in git for 1.5.10
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.