Max Jones

> @weiji14 @meghanrjones I know this is different than what we discussed at the PyGMT meeting last night, but after giving it some more thought, I would prefer not getting...

I support Will wanting to merge in https://github.com/GenericMappingTools/pygmt/pull/1299 and https://github.com/GenericMappingTools/pygmt/pull/1284 before addressing this issue to keep things moving. At the same time, I would prefer that the argument format for...

> @GenericMappingTools/pygmt-maintainers Has this issue been settled yet? The only two votes are for the long names. Yes, I think we can settle it for long names.

@willschlitzer, would you mind if I worked on a follow-up to https://github.com/GenericMappingTools/pygmt/pull/1336 with a helper function using the code that you've written for returning different output types depending on ``output_type``?...

I have a pretty general question that relates to this issue. The standardized code for returning tabular output (this issue) or raster data (https://github.com/GenericMappingTools/pygmt/issues/1400) relies on using pandas or xarray...

> > What's the reason for handling the return through temporary files versus creating a second virtual file to hold in-memory output? > > If there is a way to...

> The **-C** documentation says > > > Remember to supply -X and -Y settings if you have moved since the clip started. > > How can we revert the...

> How can we revert the -X and -Y setttings in a context manager? We might not have to do anything about this. See discussion/confusion at https://github.com/GenericMappingTools/gmt/issues/6406.

> The -C documentation says "Remember to supply -X and -Y settings if you have moved since the clip started." How can we revert the -X and -Y setttings in...

> We'll need to discuss whether to add this. I recognize the value of using pre-commit, but I find that it is another layer of friction for new contributors to...