why '[cpan://module]' isn't always easy to use

Replies are listed 'Best First'.
Re: why '[cpan://module]' isn't always easy to use by ysth (Canon) on Oct 22, 2004 at 21:24 UTC
It's ironic that you should post this just after search.cpan.org experienced a lengthy down time. Some other alternatives: http://search.cpan.org/dist/Tcl-Tk (by distribution name; automatically latest version) http://search.cpan.org/perldoc/Tcl::Tk (module doc, not distribution; works even if module is part of a larger distribution; seems to be latest non-beta version)	[reply]
Re: why '[cpan://module]' isn't always easy to use by jeffa (Bishop) on Oct 22, 2004 at 21:20 UTC
Nope, you did the right thing, but there is one improvement you can make: `[http://search.cpan.org/~vkon/Tcl-Tk]` => http://search.cpan.org/~vkon/Tcl-Tk Just drop the version number from the URL and search.cpan.org will link to the most recent release. I myself am perfectly fine with having to do the extra work myself, as the `[cpan://]` (and `[kobe://]`) tag handles the majority very nicely. UPDATE: ysth++ for substituting `~user` with the easier to recall `dist` ;) jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)	[reply]
Re: why '[cpan://module]' isn't always easy to use by bart (Canon) on Oct 23, 2004 at 07:32 UTC
There's another search mode on search.cpan.org, which normally would always point to the most recent version of a module: http://search.cpan.org/search?module=Tcl::Tk. For this particular case, it returns (for now) an intermediate search results page. I would think that's what you want anyway. But for most modules, it'll jump directly into the module's docs, for example for CGI: http://search.cpan.org/search?module=CGI I wish Perlmonks had a cpan shortcut to that kind of search: it'll only find exact matches, but it (usually) jumps straight into the docs. I would think that for references people make to modules make in posts, this would be a most excellent link.	[reply]
Why do you leave broken HTML in all of your nodes? by demerphq (Chancellor) on Oct 25, 2004 at 09:37 UTC
Hi Courage. Please don't delete the div tags that are automatically added to wrap your signature. If you insist on doing so then please also remove the close tags that are appended after your signature. The content of your node should go ABOVE the comment line. This is so users who prefer not to have the clutter of signatures everywhere have an easy way to filter them out. Thanks. BTW so you know, castaway is busy scurying around removing the broken html from all your nodes. Thank god for janitors eh? --- demerphq _{First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi Flux8}	[reply]
Re: Why do you leave broken HTML in all of your nodes? by Anonymous Monk on Oct 25, 2004 at 14:40 UTC
Wouldn't it be easier to write a checker once, and not spending cleaning up after people for ever? I mean, this is a Perl site, and writing an pseudo-HTML checker shouldn't be too hard, should it?	[reply]
Re^2: Why do you leave broken HTML in all of your nodes? by demerphq (Chancellor) on Oct 25, 2004 at 14:46 UTC
We have checking software in place. However we also have a policy of not modifying peoples posts without the change being accountable. So we dont unilaterally modify peoples posts, and we certainly wont use automatic measures to do so. The fact is that in this case the broken HTML is directly due to concious decisions made by Courage and as such the easiest thing to do is to ask him not to continue. --- demerphq _{First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi Flux8}	[reply]
Re: Why do you leave broken HTML in all of your nodes? by Courage (Parson) on Oct 25, 2004 at 19:56 UTC
I did deleting of `<div>` tags because I was not knowledgable enough how to deal with them. Moreover, they happen to appear only recently, and I did not saw them year ago, so I just did not got to used to them yet (how say this in English?) After you directly pointed me to those 'div' tags, I will have much more respect to them. Especially in case I'll be better programmer after that. And I want to send many thanks to all participants of monastery who spend their efforts improving it, and my additional personal respect to those who are improving my nodes. Best regards, Courage, the Cowardly Dog	[reply] [d/l]
Re^2: Why do you leave broken HTML in all of your nodes? by demerphq (Chancellor) on Oct 25, 2004 at 22:33 UTC
People like to turn off signatures, so we started autowrapping them. Just leave them be and post above the comment line and everything will be cool. :-) BTW, if you want to put default content in your node that _isnt_ part of your signature then you can go to User Settings and use the Note Template box for that. It can be useful to have both a signature and a template. --- demerphq _{First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi Flux8}	[reply]
Re: why '[cpan://module]' isn't always easy to use by Courage (Parson) on Oct 25, 2004 at 08:06 UTC
Thank you all for good advices!	[reply]
Re: why '[cpan://module]' isn't always easy to use by ikegami (Patriarch) on Oct 25, 2004 at 20:36 UTC
The reason you're having problems is because two libraries (TclTk and Tcl-Tk) share the same namespace (Tcl::Tk). `[cpan://]` searches 'Modules'. I usally get better results by searching for 'All'. 'All' actually lists the TclTk (old version of Tcl::Tk) library followed immediately by the Tcl-Tk library (new version of Tcl::Tk).	[reply] [d/l]
Re^2: why '[cpan://module]' isn't always easy to use by Courage (Parson) on Oct 26, 2004 at 17:59 UTC
Elder naming convention belonged to Malcolm and I do not dare even thinking about removing them. (or may be it is reasonable?) Probably removing old version will cure situation... Best regards, Courage, the Cowardly Dog	[reply]