I'm happy with semicolons, but want to know if everyone else is. Newlines won't work. A newline (hitting enter/return from the keyboard) causes the command to be parsed.
Michael On 7/4/07 2:08 AM, "Hamish" <[EMAIL PROTECTED]> wrote: > Michael wrote: >>>> 2nd splitting that allows for multiple d.* commands to be separated >>>> by semi-colons. This may or may not be a good idea in the end, but >>>> I thought I'd see how it worked out. > Paul: >>> Shell uses semi-colons. But you could you not just enter the two >>> commands separately one after the other? I suppose if it was >>> something that would take a long time to draw then that would be >>> slow. > Michael: >> The problem is that you need a defined separator that indicates where >> one command AND its arguments stop and another one starts. You could >> perhaps look for another "d." string, but a defined separator is >> easier to use and perhaps more reliable. > > If you don't like semi-colons, would the newline char work? > > > Hamish __________________________________________ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
