I suppose that at least part of the problem is focus. I usually turn to the list for answers to problems that I've not been able to solve from the existing documentation. It usually doesn't occur to me that there might be some larger use for the question itself. It probably should--- as an obvious for example, look at FAQs for instance. There what might be an annoyance is changed to a resource, usually without a great deal of effort.
--hsm On Thu, Dec 3, 2009 at 5:19 AM, Alexander Kobel <n...@a-kobel.de> wrote: > Hugh Myers wrote: >> >> [...] As long as I'm exposing my thinking to the world (at least the >> Lilypond world) another thing that needs to be pointed out to the UC >> (User Community) is that they have a sure and certain value in their >> ability to say that they don't understand a particular piece of >> documentation. [...] > > Correct. Which is part of why Graham does even consider to answer many > requests on -user. It must be really frustrating to invest that much time > and energy in the docs, and see people a) ignoring it, or b) reading and > trying to understand it, but not mentioning in their mails what (or even > better: why) they don't understand it. > The latter case is plainly sad, the second is - well, don't really know, > since you always assume the first one, and develop some ignorance; but it's > certainly not helpful from the second type of inquirer to not give hints > what should be done better, just as you said. > > May I remark that a short scan through your mails starting a new thread > revealed only two pointer to the manuals (in "instantiating voices" and > "broken link")? > Not that I do any better, I have to admit. (*Writes down note to himself.*) > > > Cheers, > Alexander > _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
