|
From: | siko1056 |
Subject: | Re: datetick, reason for explicitly undocumented behavior? |
Date: | Sun, 1 Jan 2017 11:48:36 -0800 (PST) |
Jonathan Suever wrote > It's worth noting that the OP was using the second example on the online > documentation > <https://octave.sourceforge.io/octave/function/datetick.html> > as a guide which also incorrectly transposes the first two inputs. I have > submitted a bug report to the bug tracker > <https://savannah.gnu.org/bugs/?49954>. > > I'm more than happy to help fix this documentation error if someone can > point me towards the best way to contribute changes towards the online > documentation. > > -Jonathan As explained in the bug tracker [1] the change of the online documentation [2] (actually it is a documentation maintained by Octave forge, the official Octave documentation for the latest release is found at [3]) depends on a page update by Carnë. But the state of Octave forge is kind of uncertain at the moment [4]. Kai. [1]: https://savannah.gnu.org/bugs/?49954 [2]: https://octave.sourceforge.io/octave/function/datetick.html [3]: https://www.gnu.org/software/octave/doc/interpreter/XREFdatetick.html [4]: http://octave.1599824.n4.nabble.com/Octave-Forge-Looking-for-a-new-leader-td4681121.html -- View this message in context: http://octave.1599824.n4.nabble.com/datetick-reason-for-explicitly-undocumented-behavior-tp4681183p4681206.html Sent from the Octave - General mailing list archive at Nabble.com.
[Prev in Thread] | Current Thread | [Next in Thread] |