On Fri, Mar 25, 2011 at 6:35 AM, Eli Adam <ea...@co.lincoln.or.us> wrote: >>Consider to post such output as text here for example (easier to read): >>http://osgeo.pastebin.com/ > > I agree that screenshots of text are not as helpful as they could be.
I'd say that screenshots are useful for maps. > I have been wanting to ask a question about pastebins for a variety of OSGeo > mail lists and this is at least a great opportunity for GRASS (perhaps we > should move to discuss?). Are they preferable to putting it in the email > since it is 'too' much for an email? I understand how you may want to > pastebin python or something else very sensitive to spacing, however, I also > thought that one of the main points of the mailing list was posterity and > helping other users by search. If all the relevant information is contained > in an ephemeral pasetbin, searching is much less helpful. > > When should something be contained in an email? > > When should something be put in a pastebin? Suggestions (fairly straightforward): * email: for discussions (can include and small (!) snippets, put long snippets into pastebin for nice syntax highlighting) * GRASS Wiki to create permanent documentation (e.g. summary of discussions in list, nice approaches etc) including code (there is also syntax highlighting possible) * pastebin is only a temporary container for discussions, not for permanment storage. Likewise summaries to the email list are way less useful than adding them to the Wiki where they can be further continued. Makes sense? Markus _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user