I have to agree. I became so frustrated with M-x TeX-doc that I ended up
rolling my own function to do exactly as you describe.

Of course, another option is to make an enhancement to texdoc (the ultimate
tool) to provide a list of these 'keys' for completion's sake. A close
inspection of texdoc's own documentation [1] might obviate this, however.

Best,
Sean

[1]: http://texdoc.net/texmf-dist/doc/texdoc/texdoc.pdf

On Thu, Dec 10, 2015 at 10:31 AM Mosè Giordano <m...@gnu.org> wrote:

> Dear all,
>
> am I the only one who finds `TeX-doc' overly complicated to the point
> it's sometimes useless?  It fails to find documentation for many
> packages and classes, also pretty common ones like "babel", "fontenc",
> and "memoir".  Wouldn't it better if it simply runs "texdoc NAME"?
> Aucompletion is cool, but in this case is often useless as the
> manual's basenames don't have to, and many times don't, match the name
> of the package.
>
> Bye,
> Mosè
>
> _______________________________________________
> auctex-devel mailing list
> auctex-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/auctex-devel
>
_______________________________________________
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Reply via email to