On Tue, Dec 1, 2015 at 9:53 AM, Jachym Cepicky wrote:
> renamed g.search.module -> g.search.modules
Backported to GRASS GIS 7.0.svn (upcoming 7.0.4) in r67759
Cheers
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mai
renamed g.search.module -> g.search.modules
po 30. 11. 2015 v 22:33 odesílatel Vaclav Petras
napsal:
>
> On Mon, Nov 30, 2015 at 4:22 PM, Markus Neteler wrote:
>
>> > Considering the fact that an important/main use case is interactive
>> usage in
>> > the command line, I now lean towards:
>>
On Mon, Nov 30, 2015 at 4:22 PM, Markus Neteler wrote:
> > Considering the fact that an important/main use case is interactive
> usage in
> > the command line, I now lean towards:
> >
> > g.search.module aspect
>
> I would suggest to not use the singular "module" but plural "modules"
> which woul
On Mon, Nov 30, 2015 at 4:12 PM, Jachym Cepicky
wrote:
> the script called g.search.module is now in trunk, I've added tests
>
Great. It is really fast (without -m). It will be useful.
> (Vašek: they seem to be far too verbose to me, anything I could do about
> that?)
>
Yes, partially. The it
Hi
On Sat, Nov 28, 2015 at 3:29 PM, Vaclav Petras wrote:
>
> On Sat, Nov 28, 2015 at 5:09 AM, Jachym Cepicky
> wrote:
>>
>> Vašku, if we agree on adding more search engines to g.search, I suggest to
>> define the features and interface (--help output) now and I can start think
>> about more gene
OK guys,
the script called g.search.module is now in trunk, I've added tests (Vašek:
they seem to be far too verbose to me, anything I could do about that?)
I've left the colorize and print_output functions in the file, reason:
better code structure would have to be implemented (read: IMHO decora
On Mon, Nov 30, 2015 at 3:27 AM, Jachym Cepicky
wrote:
> about the tests - generally yes, I'm writing it. Are you referring to
> r3.info or to g.search.* modules? I could not found any example to
> r3.info tests
>
I meant r3.info as it is more critical but g.search.* is similar just not
critica
Well,
about the tests - generally yes, I'm writing it. Are you referring to
r3.info or to g.search.* modules? I could not found any example to r3.info
tests
I've rewritten r3.info so that the code is the same, as r.info (with -e
flag) - but I can not tell, I'm satisfied with the result (there ar
On Sun, Nov 29, 2015 at 7:06 AM, Jachym Cepicky
wrote:
> the code is in the same repository but packed in the g.search.module
> directory now, not sure, if the g.extension will work again
g.extension supports only directories which have Makefile, i.e. Makefile
must be in the root directory of t
Guys,
I've patched r3.info a bit (not sure, whether it's ok)
https://trac.osgeo.org/grass/changeset/66983/ for potential better
g.search.data output
i would like to move colorize, print_results from g.search.module to some
reachable place within existing grass python code base - any hint?
Jachym
Guys,
I would like to declare g.search.module "done" - I've introduced some more
functions (reusable for other g.search.* modules), colorized terminal
output (-c), shell script (-g) and json (-j) output, added sniffing in
manual pages too (-m), better terminal output (line width <= 79 characters)
On 29 November 2015 at 00:04, Markus Neteler wrote:
> Hi Jachym,
>
Hi Jachym,
>
> So cool!!! Thank you,
>
+1, really cool
> Markus
>
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.o
Hi Jachym,
On Fri, Nov 27, 2015 at 4:51 PM, Jachym Cepicky
wrote:
> Hi all,
>
> I've tried to implement command line alternative to module search based on
> keywords, which is available in the gui - it's called g.search
GRASS 7.1.svn (nc_spm_08_grass7):~ > g.extension g.search
url=https://github
Hi Jachym,
2015-11-28 17:27 GMT+01:00 Jachym Cepicky :
> if nobody protests, I'll prepare basic framework for g.search.* modules and
> let you know, once it's about to be ready
absolutely cool, thanks for your work! Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/
OK guys,
if nobody protests, I'll prepare basic framework for g.search.* modules and
let you know, once it's about to be ready
Jachym
so 28. 11. 2015 v 15:52 odesílatel Yann napsal:
> +1 awesomeness
> +1 for trunk
>
> On 27/11/2015 17:12, Vaclav Petras wrote:
> > On Fri, Nov 27, 2015 at 10:51
+1 awesomeness
+1 for trunk
On 27/11/2015 17:12, Vaclav Petras wrote:
On Fri, Nov 27, 2015 at 10:51 AM, Jachym Cepicky
wrote:
Hi all,
I've tried to implement command line alternative to module search based on
keywords, which is available in the gui - it's called g.search
Any chance, you mig
On Sat, Nov 28, 2015 at 5:09 AM, Jachym Cepicky
wrote:
> Vašku, if we agree on adding more search engines to g.search, I suggest to
> define the features and interface (--help output) now and I can start think
> about more generic concept of the code
>
> modules
> maps, groups
> mapsets
> locatio
Vašku, if we agree on adding more search engines to g.search, I suggest to
define the features and interface (--help output) now and I can start think
about more generic concept of the code
modules
maps, groups
mapsets
locations?
regions
...
OR and AND flag
terminal output, shell script output,
On Fri, Nov 27, 2015 at 6:06 PM, Jachym Cepicky
wrote:
> ahoj Vašku,
>
> not sure about the maps. wouldn't be better to extend g.list?
>
Perhaps, the search could include title names as well - this would be the
extension to g.list. This makes sense as you usually know if you are
searching maps/gr
ahoj Vašku,
not sure about the maps. wouldn't be better to extend g.list?
about the name: g.module.search?
need to work on the output a bit more...
would -g flag be useful as well?
glad you like it
jachym
On Fri, Nov 27, 2015, 17:13 Vaclav Petras wrote:
> On Fri, Nov 27, 2015 at 10:51 AM,
On Fri, Nov 27, 2015 at 10:51 AM, Jachym Cepicky
wrote:
> Hi all,
>
> I've tried to implement command line alternative to module search based on
> keywords, which is available in the gui - it's called g.search
>
> Any chance, you might find this useful ? Any comment to the source code
> and outpu
Hi all,
I've tried to implement command line alternative to module search based on
keywords, which is available in the gui - it's called g.search
Any chance, you might find this useful ? Any comment to the source code and
outputs?
https://github.com/jachym/g.search
Jachym
__
22 matches
Mail list logo
