[GRASS-dev] Message standardization

Wolf Bergenheim wolf+grass at bergenheim.net
Sun Dec 16 22:03:59 EST 2007

On 17.12.2007 01:35, Hamish wrote:
> Ellipses
>    *  Suspension points used to indicate some process is being done
> should be placed next to last word, without space. e.g. "Reading map..."
> instead of "Reading map ..." 
>     --HB: FWIW & my 2c, 1) to me keeping the space before the ellipse
> looks better; is this a purely cosmetic choice or is there some style
> logic? 2) these messages may be good candidates for G_verbose_message().

1) Yeah I agree space before the ellipsis looks maybe a bit better with
a space before it. However, not having the space before seems to be
recommended, as you can see for instance in Wikipedia [1]

[1] http://en.wikipedia.org/wiki/Ellipsis

> "Map <roads> in <user1>" or "Map <roads at user1>"
>     * "Map <roads at user1>" preferred - ML
>     * If the element was given on the command line, then the user knows
> which mapset it came from, and the @mapset part is just extra noise,
> perhaps use the ->answer string from the parser instead of the
> processed ("%s@%s", name, mapset)? If the element is taken from the data
> (how? i.group?) where the user hasn't explicitly defined the map, then
> @mapset it appropriate. Also output maps are always created in the
> current mapset* so @mapset is redundant and should not be used for new
> maps. [* i.rectify, r.in.gdal, v.in.ogr are exceptions that can create
> maps in other mapsets or new locations] --HB

FWIW I think that using @mapset should be limited to cases where mapset
is not the current mapset. And should *always* be used in that case
whether the input came from the user or not.



<:3 )---- Wolf Bergenheim ----( 8:>

More information about the grass-dev mailing list