• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How might I filter documentation being searched?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How might I filter documentation being searched?


  • Subject: Re: How might I filter documentation being searched?
  • From: Crispin Bennett <email@hidden>
  • Date: Thu, 16 Aug 2012 15:03:33 +1000


On 16/08/2012, at 12:06 PM, Shane Stanley wrote:

Interesting. I've filed a couple that I've seen addressed. Now that's no evidence that they were addressed by my bugs, but one at least was on a section I wouldn't suspect is widely used.


I've had at least one docs browser bug addressed too. I don't think there's any lack of assiduousness (or a fortiori capacity or creativity) involved. But the secrecy of the whole process is dreadfully off-putting (for example, if a bug is closed as a dupe, you're not permitted even to find out if it's been addressed, other than by happenstance). I find my bug-filling time more efficiently directed towards products of companies that understand two-way communication.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: How might I filter documentation being searched? (From: Matt Neuburg <email@hidden>)
 >Re: How might I filter documentation being searched? (From: Shane Stanley <email@hidden>)

  • Prev by Date: Re: How to keep individual resource-based files as separate files inside the /Resources folder?
  • Next by Date: Re: #import competition broken on 4.4.1
  • Previous by thread: Re: How might I filter documentation being searched?
  • Next by thread: Keep output in the console
  • Index(es):
    • Date
    • Thread