I have finally had the time to take a little better look at the code and
actually test
ximgview/wxpyimgview. I replaced my first PR [1] for deleting GRASS_NOTIFY
with a PR [2] with which a G_warning is issued if the system call fails.
The documentation on using ximgview/wxpyimgview, including the
On Fri, 4 Mar 2022 at 10:09, Nicklas Larsson via grass-dev <
grass-dev@lists.osgeo.org> wrote:
> Couldn’t the desired outcome
> of using GRASS_NOTIFY be implemented in another way?
>
The purpose was interactive use from the command line I suppose, so for
these cases users can set a convenient ali
Nicklas Larsson via grass-dev wrote:
> I personally never had the need for the use of GRASS in this way, so forgive
> my ignorance in this regard.
> However, one thing stands out very clear from my newly gained experience:
> there is a lack of documentation on this use of GRASS_NOTIFY. For instan
> On 3 Mar 2022, at 22:20, Glynn Clements wrote:
>
>
> Nicklas Larsson via grass-dev wrote:
>
>> Is there anyone out there who know about usage of the environment
>> variable GRASS_NOTIFY, historically and in the present?
>
> It's an external interface; it isn't used internally.
>
> The inte
Nicklas Larsson via grass-dev wrote:
> Is there anyone out there who know about usage of the environment
> variable GRASS_NOTIFY, historically and in the present?
It's an external interface; it isn't used internally.
The intention is described in the email you cited: to allow a program
(specifi
Hi Devs,
Is there anyone out there who know about usage of the environment variable
GRASS_NOTIFY, historically and in the present?
In addressing an otherwise trivial compiler warning, I stumbled into this for
me strange piece of code and usage of GRASS_NOTIFY in the Raster Display
Library. I p
