in reply to Why doesn't 'viewcode' work for type X?

I think I've already run into cases where displaytypes or such were made too DWIM and I've regretting it because a more sensible action became available (and you can replace an error with a good new behavior but backward compat prevents you from easily replacing an ill-advised DWIM action with a more consistent action).

But perhaps a good compromise would be to have node viewcode page include the above link along with the error text so that you could still easily get to the somewhat related "code for the node" but in a way that wouldn't confuse people into thinking that the code actually is part of the node they requested and that could be changed down the road.

- tye        

  • Comment on Re: Why doesn't 'viewcode' work for type X?

Replies are listed 'Best First'.
Re^2: Why doesn't 'viewcode' work for type X?
by demerphq (Chancellor) on Dec 28, 2004 at 09:04 UTC

    Yeah, I've argued for a smarter "viewcode" logic in the past but I think ive come around to your view that this is unnecessary DWIM. Anyway, I thought your point about a better error message is good, and I've now linked in get_display_types as well. I think that should do nicely. Eg: sample sourcecodesection viewcode

    ---
    demerphq