{"id":6197,"date":"2012-08-16T12:03:23","date_gmt":"2012-08-16T06:33:23","guid":{"rendered":"https:\/\/2thenew.xyz\/blog\/?p=6197"},"modified":"2012-08-16T12:03:23","modified_gmt":"2012-08-16T06:33:23","slug":"auto-completion-for-grails-scripts-with-dynamic-version-determination","status":"publish","type":"post","link":"https:\/\/2thenew.xyz\/blog\/auto-completion-for-grails-scripts-with-dynamic-version-determination\/","title":{"rendered":"Auto Completion for Grails Scripts with Dynamic Version Determination"},"content":{"rendered":"

We are constantly striving to be more productive by minimizing key-strokes for a lot of commonly used shell commands. Alias is one way of achieving it, but it isn’t always the answer. Bash auto completion is one feature that I use a lot.<\/p>\n

To avoid the hassles of working with multiple grails projects, I use this script <\/a>and for auto completion, I use this wonderful auto completion script by Ted Naleid<\/a>. However, there were a few more scripts\/arguments which we thought would be a great addition to the auto-completion set. Scripts provided by plugins was one such set and this had to come from the appropriate directory under .grails\/$GRAILS_VERSION\/projects\/$PROJ_HOME\/plugins\/*\/scripts.<\/strong><\/em> Another set of options which I thought appropriate were the system properties that we provide.<\/p>\n

So, I came up with the custom auto completion script given below<\/p>\n

[shell]<\/p>\n

_grailsscripts() {<\/p>\n

if [ -z "$PROJ_DIR" ]
\n then
\n if [ -e "application.properties" ]
\n then
\n export GRAILS_VERSION=`grep app.grails.version application.properties | sed -E ‘s\/.*=(.*)\/\\1\/’`
\n export GRAILS_HOME="\/opt\/grails-$GRAILS_VERSION"
\n PWD=`pwd`
\n export PROJ_DIR=`basename $PWD`
\n fi
\n fi
\n SCRIPT_DIRS="$GRAILS_HOME\/scripts .\/scripts ~\/.grails\/scripts"
\n if [ "$PROJ_DIR" ]
\n then for PLUGIN_DIR in $(ls -d ~\/.grails\/$GRAILS_VERSION\/projects\/$PROJ_DIR\/plugins\/*\/scripts 2&gt; \/dev\/null); do
\n SCRIPT_DIRS="$SCRIPT_DIRS $PLUGIN_DIR"
\n done
\n fi
\n if [ -d plugins ]
\n then for PLUGIN_DIR in $(ls -d plugins\/*\/scripts 2&gt; \/dev\/null); do
\n SCRIPT_DIRS="$SCRIPT_DIRS $PLUGIN_DIR"
\n done
\n fi<\/p>\n

for D in $SCRIPT_DIRS; do
\n if [ -d $D ]
\n then ls -1 $D\/*.groovy 2&gt; \/dev\/null | sed -E ‘s\/(.*)\\\/(.*)\\.groovy\/\\2\/’ | sed -E ‘s\/([A-Z])\/-\\1\/g’ | sed -E ‘s\/^-\/\/’ | tr "[:upper:]" "[:lower:]"
\n fi
\n done | sort | uniq | grep -vE "^_"
\n}<\/p>\n

grailsOpts="-Dserver.port= -Dgrails.env= test dev prod"<\/p>\n

_grails() {
\n COMPREPLY=( $(compgen -W "$(_grailsscripts) $grailsOpts" — ${COMP_WORDS[COMP_CWORD]}) )
\n}<\/p>\n

complete -F _grails grails
\ncomplete -F _grails grails-debug<\/p>\n

[\/shell]<\/p>\n

Now, all you need is to add this script under \/etc\/bash_completion.d\/
\n
\nHope this helps you save a few keystrokes.
<\/p>\n","protected":false},"excerpt":{"rendered":"

We are constantly striving to be more productive by minimizing key-strokes for a lot of commonly used shell commands. Alias is one way of achieving it, but it isn’t always the answer. Bash auto completion is one feature that I use a lot. To avoid the hassles of working with multiple grails projects, I use […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":6,"footnotes":""},"categories":[7],"tags":[865,519,4840,866,260,453,8],"class_list":["post-6197","post","type-post","status-publish","format-standard","hentry","category-grails","tag-bash-completion","tag-bash-script","tag-grails","tag-grails-script-auto-complete","tag-linux","tag-shell","tag-ubuntu"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t