Re: [GRASS-dev] [GRASS GIS] #3849: Do we need to clear the screen when entering/exiting GRASS?

#3849: Do we need to clear the screen when entering/exiting GRASS? --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: Component: Startup |Version:

Re: [GRASS-dev] Segment library zero filling

On Mon, May 20, 2019 at 1:46 PM Markus Metz wrote: > > On Mon, May 20, 2019 at 7:18 PM Vaclav Petras > wrote: > > > > On Mon, May 20, 2019 at 11:57 AM Markus Metz < > markus.metz.gisw...@gmail.com> wrote: > >> > >> On Mon, May 20, 2019 at 5:39 PM Vaclav Petras > wrote: > >> > > >> > Hi MarkusM

Re: [GRASS-dev] Segment library zero filling

On Mon, May 20, 2019 at 7:18 PM Vaclav Petras wrote: > > > > On Mon, May 20, 2019 at 11:57 AM Markus Metz < markus.metz.gisw...@gmail.com> wrote: >> >> >> >> On Mon, May 20, 2019 at 5:39 PM Vaclav Petras wrote: >> > >> > Hi MarkusM and all, >> > >> > I'm trying to understand if the Segment_open()

Re: [GRASS-dev] Segment library zero filling

On Mon, May 20, 2019 at 11:57 AM Markus Metz wrote: > > > On Mon, May 20, 2019 at 5:39 PM Vaclav Petras > wrote: > > > > Hi MarkusM and all, > > > > I'm trying to understand if the Segment_open() [1] function fills with > zeros or not. I don't think it does since it is calling G_malloc (malloc)

Re: [GRASS-dev] Segment library zero filling

On Mon, May 20, 2019 at 5:39 PM Vaclav Petras wrote: > > Hi MarkusM and all, > > I'm trying to understand if the Segment_open() [1] function fills with zeros or not. I don't think it does since it is calling G_malloc (malloc) or Segment_format_nofill(). However, it is not completely clear to me wh

[GRASS-dev] Segment library zero filling

Hi MarkusM and all, I'm trying to understand if the Segment_open() [1] function fills with zeros or not. I don't think it does since it is calling G_malloc (malloc) or Segment_format_nofill(). However, it is not completely clear to me what is supposed to be doing because documentation still says i

Re: [GRASS-dev] [GRASS GIS] #3846: r.contour started producing broken/segmented contour lines since 7.4

#3846: r.contour started producing broken/segmented contour lines since 7.4 --+--- Reporter: metello | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: Component: Raster |Version: u

[GRASS-dev] black: Python code formatter (eg PEP8)

FYI Back - Python code formatter (eg. PEP8) https://github.com/python/black # example: default settings mit max. 79 Buchstaben per Zeile $ black -l 79 ./*.py Online playground: https://black.now.sh/ Would that be useful for us? cheers Markus ___ gras

Re: [GRASS-dev] git: how to switch between branches?

Hello Markus I don't have real-world experience with this, but I am not sure if changing branches and distcleaning/recompiling is the most convenient workflow. I think I would prefer to have multiple local repositories with different branches checked out. Thankfully git makes it rather easy to hav