Closed
Conversation
Member
Author
9343224 to
5a7ef2a
Compare
OSGeo#3634) Enable to use (show/add/delete/rename/query) column name which is reserved DB backend keyword.
The g.message does not need any of the session setup and it can be used during a setup process to report standardized messages to the user. This removes the need to have a full session before running g.message. GISRC is still needed, but the data (file) structures for mapset don't need to exist. The code is combination of what is in g.proj (the 'no init' call and comment) and g.dirseps (memory mode for GISRC). It is also syncing the corresponding lines in g.proj.
…o#3668) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
For reporting errors the g.message tool is called, so the environment setup is always needed (except when doing XY without errors).
* grass.script: Get GISBASE automatically in get_commands The _grass.script.get_commands_ function requires GISBASE (more specifically, path to binary executables and scripts). The need for GISBASE prevents its use before a session (more specifically the runtime part of it) is created. This changes the function to get the GISBASE automatically when not set. It also adds the standard env parameter other functions have (which is useful mainly for tests). * Add mock for tests
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…3691) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Member
Author
|
Hmm.... I think I broke it... Not sure why it's happening. My local clone looks fine. |
Member
Author
|
Replaced by #3727. |
Member
Might be a pull instead when a force push was appropriate: OSGeo/grass-addons#802 (comment) To fix broken states, you can also force push a new branch to an old PR. Preserves comment and review history and links from other PRs. The Git mechanics for that is force pushing to a remote branch of a different name (you force push just the first time). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR rewrites the
d.redrawPython script in C. It works with #3482 to constrain redrawing within the current display extent in the monitor. Without this PR and #3482, the following test can take very long becaused.rast.arrowhas to draw 772,957,282 (number of non-null cells) arrows across the entire DEM even for a very small display extent in the monitor.#3482 and #3492 address the above issue, and this new PR resolves a similar problem with
d.redrawbecause thed.rast.arrowcommand will be triggered again byd.redrawfrom the terminal withoutGRASS_REGION.The basic idea is to delegate all rendering to the monitor that knows about the display extent. Modules when run from the terminal don't have that information (
GRASS_REGION) that is dynamic and internal to the monitor.