Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

g.gisenv: Describe where the variables are stored in manual #232

Merged
merged 3 commits into from
Jan 12, 2022
Merged

g.gisenv: Describe where the variables are stored in manual #232

merged 3 commits into from
Jan 12, 2022

Conversation

jidanni
Copy link
Contributor

@jidanni jidanni commented Dec 3, 2019

@metzm
Copy link
Contributor

metzm commented Dec 3, 2019

This is an error in the g.gisenv manual. It does not store variables in $GISDBASE/$LOCATION_NAME/$MAPSET/VAR. This file only stores information about the default vector database connection, which can be modified for the current mapset with db.connect.

@neteler neteler requested a review from metzm April 26, 2020 19:09
@neteler
Copy link
Member

neteler commented Jun 22, 2020 •
edited
Loading

This is an error in the g.gisenv manual. It does not store variables in $GISDBASE/$LOCATION_NAME/$MAPSET/VAR. This file only stores information about the default vector database connection, which can be modified for the current mapset with db.connect.

Should the currently proposed modification be removed then?

@neteler neteler added manual Documentation related issues bug Something isn't working labels Dec 9, 2021
@neteler neteler added this to the 8.0.0 milestone Dec 9, 2021
@metzm
Copy link
Contributor

metzm commented Jan 12, 2022

This is an error in the g.gisenv manual. It does not store variables in $GISDBASE/$LOCATION_NAME/$MAPSET/VAR. This file only stores information about the default vector database connection, which can be modified for the current mapset with db.connect.

Should the currently proposed modification be removed then?

No, I was mistaken, g.gisenv can indeed use $GISDBASE/$LOCATION_NAME/$MAPSET/VAR to read/write variables. The change is fine with me.

@neteler
Copy link
Member

neteler commented Jan 12, 2022

(Close/reopen to wake up flake8 test)

@neteler neteler closed this Jan 12, 2022
@neteler neteler reopened this Jan 12, 2022
@neteler neteler merged commit 3bd5de2 into OSGeo:main Jan 12, 2022
neteler pushed a commit that referenced this pull request Jan 12, 2022
@jidanni @neteler
Update g.gisenv.html (#232)
975faad 
* Update g.gisenv.html, see https://trac.osgeo.org/grass/ticket/3997
@wenzeslaus wenzeslaus changed the title Update g.gisenv.html g.gisenv: Describe where the variables are stored in manual Apr 27, 2022
ninsbl pushed a commit to ninsbl/grass that referenced this pull request Oct 26, 2022
@jidanni @ninsbl
Update g.gisenv.html (OSGeo#232)
00d730a 
* Update g.gisenv.html, see https://trac.osgeo.org/grass/ticket/3997
ninsbl pushed a commit to ninsbl/grass that referenced this pull request Feb 17, 2023
@jidanni @ninsbl
Update g.gisenv.html (OSGeo#232)
ff8517c 
* Update g.gisenv.html, see https://trac.osgeo.org/grass/ticket/3997
neteler pushed a commit to nilason/grass that referenced this pull request Nov 7, 2023
@jidanni @neteler
Update g.gisenv.html (OSGeo#232)
5884498 
* Update g.gisenv.html, see https://trac.osgeo.org/grass/ticket/3997
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@neteler neteler neteler left review comments

@metzm metzm metzm approved these changes

Assignees
No one assigned
Labels
bug Something isn't working manual Documentation related issues
Projects
None yet
Milestone
8.0.0
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@jidanni @metzm @neteler