Hi,
any objections to backporting r.proj -p and -g flags? it makes it so you
don't need the v.in.region + v.proj tricks and makes the work flow a lot
easier (no need to change GRASS sessions).
also, any objections to backport v.in.lines? it's mostly just a wrapper
script with an easier to underst
#1191: make install gives sed error in r43810
---+
Reporter: cgsbob| Owner: grass-...@…
Type: defect| Status: reopened
Priority: normal| Milesto
#224: cache bug in DGLib
--+-
Reporter: martinl | Owner: grass-...@…
Type: defect | Status: reopened
Priority: major| Milestone: 6.4.1
Comp
#224: cache bug in DGLib
--+-
Reporter: martinl | Owner: grass-...@…
Type: defect | Status: reopened
Priority: major| Milestone: 6.4.1
Comp
#1191: make install gives sed error in r43810
---+
Reporter: cgsbob| Owner: grass-...@…
Type: defect| Status: reopened
Priority: normal| Milesto
Hi Helena,
>YOu mean (e.g. my Script is called i.test.py
>I should have a i.test.bat in bin folder and with the following?
>@"%GRASS_SH%" -c '"%GISBASE%/scripts/i.test.py" %*'
>??
>How can I know if ther python is in the path?
>
>THanks
>helena
maybe following code in the source could help you,
h
#224: cache bug in DGLib
--+-
Reporter: martinl | Owner: grass-...@…
Type: defect | Status: reopened
Priority: major| Milestone: 6.4.1
Comp
Hi
> If I understand Glynn's comments correctly it won't work through the main
> build system, but for personal add-on scripts that's not the end of the
> world.
>
> That is exacly what I want. I have my winGRASS6.4 installation and I want
to run/use some Python scripts. Just that...
> the imp
