Add terminal configuration in projectorganizer

[RaphaelRochet]

Even if xterm and /usr/bin/x-terminal-emulator alternative defaults cover a lot of systems, it will fail if you don't use xterm or a debian-compatible distro.

Could it be configurable via plugin preferences, or project properties ?
Or simply use the terminal we can already set in Geany preferences > tools > terminal ?

Thanks

[techee]

@RaphaelRochet Done in #1432. Would you give it a try?

[RaphaelRochet]

Nice !
Sure I'd give it a try, but can I ?
I use a packaged version of geany 2.0 from Arch repo.

[techee]

Well, I think the only option is to install Geany and geany-plugins from sources. Geany provides nightly builds for Debian only and as the pull request isn't merged yet, nightly builds will be unavailable anyway.

[RaphaelRochet]

Sorry, couldn't compile it. Took a long time to gather dependencies and decrypt autogen nonsense errors, but hit a dead end ...
The configure script looks broken.

/home/raphael/geany-plugins/configure: line 6447: syntax error near unexpected token `newline'
/home/raphael/geany-plugins/configure: line 6447: `yes:'

Edit:
It's quoted from configure.ac:17 earlier in the output:

configure.ac:17: warning: ac_ext=c
configure.ac:17: ac_cpp='$CPP $CPPFLAGS'
configure.ac:17: ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
configure.ac:17: ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
configure.ac:17: ac_compiler_gnu=$ac_cv_c_compiler_gnu
configure.ac:17: if test -n "$ac_tool_prefix"; then
configure.ac:17:   # Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args.
configure.ac:17: set dummy ${ac_tool_prefix}gcc; ac_word=$2
configure.ac:17: { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
configure.ac:17: printf %s "checking for $ac_word... " >&6; }
configure.ac:17: if test ${ac_cv_prog_CC+y}
configure.ac:17: then :
configure.ac:17:   printf %s "(cached) " >&6
configure.ac:17: else case e in #(
configure.ac:17:   e) if test -n "$CC"; then
configure.ac:17:   ac_cv_prog_CC="$CC" # Let the user override the test.
configure.ac:17: else
configure.ac:17: as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
configure.ac:17: for as_dir in $PATH
configure.ac:17: do
configure.ac:17:   IFS=$as_save_IFS
configure.ac:17:   case $as_dir in #(((
configure.ac:17:     '') as_dir=./ ;;
configure.ac:17:     */) ;;
configure.ac:17:     *) as_dir=$as_dir/ ;;
configure.ac:17:   esac
configure.ac:17:     for ac_exec_ext in '' $ac_executable_extensions; do
configure.ac:17:   if as_fn_executable_p "$as_dir$ac_word$ac_exec_ext"; then
configure.ac:17:     ac_cv_prog_CC="${ac_tool_prefix}gcc"
configure.ac:17:     printf "%s\n" "$as_me:${as_lineno-$LINENO}: found $as_dir$ac_word$ac_exec_ext" >&5
configure.ac:17:     break 2
configure.ac:17:   fi
configure.ac:17: done
configure.ac:17:   done
configure.ac:17: IFS=$as_save_IFS
configure.ac:17: 
configure.ac:17: fi ;;
configure.ac:17: esac
configure.ac:17: fi
configure.ac:17: CC=$ac_cv_prog_CC
configure.ac:17: if test -n "$CC"; then
configure.ac:17:   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
configure.ac:17: printf "%s\n" "$CC" >&6; }
configure.ac:17: else
configure.ac:17:   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5
configure.ac:17: printf "%s\n" "no" >&6; }
configure.ac:17: fi
configure.ac:17: 
configure.ac:17: 
configure.ac:17: fi
configure.ac:17: if test -z "$ac_cv_prog_CC"; then
configure.ac:17:   ac_ct_CC=$CC
configure.ac:17:   # Extract the first word of "gcc", so it can be a program name with args.
configure.ac:17: set dummy gcc; ac_word=$2
configure.ac:17: { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
configure.ac:17: printf %s "checking for $ac_word... " >&6; }
configure.ac:17: if test ${ac_cv_prog_ac_ct_CC+y}
configure.ac:17: then :
configure.ac:17:   printf %s "(cached) " >&6
configure.ac:17: else case e in #(
configure.ac:17:   e) if test -n "$ac_ct_CC"; then
configure.ac:17:   ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
configure.ac:17: else
configure.ac:17: as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
configure.ac:17: for as_dir in $PATH
configure.ac:17: do
configure.ac:17:   IFS=$as_save_IFS
configure.ac:17:   case $as_dir in #(((
configure.ac:17:     '') as_dir=./ ;;
configure.ac:17:     */) ;;
configure.ac:17:     *) as_dir=$as_dir/ ;;
configure.ac:17:   esac
configure.ac:17:     for ac_exec_ext in '' $ac_executable_extensions; do
configure.ac:17:   if as_fn_executable_p "$as_dir$ac_word$ac_exec_ext"; then
configure.ac:17:     ac_cv_prog_ac_ct_CC="gcc"
configure.ac:17:     printf "%s\n" "$as_me:${as_lineno-$LINENO}: found $as_dir$ac_word$ac_exec_ext" >&5
configure.ac:17:     break 2
configure.ac:17:   fi
configure.ac:17: done
configure.ac:17:   done
configure.ac:17: IFS=$as_save_IFS
configure.ac:17: 
configure.ac:17: fi ;;
configure.ac:17: esac
configure.ac:17: fi
configure.ac:17: ac_ct_CC=$ac_cv_prog_ac_ct_CC
configure.ac:17: if test -n "$ac_ct_CC"; then
configure.ac:17:   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
configure.ac:17: printf "%s\n" "$ac_ct_CC" >&6; }
configure.ac:17: else
configure.ac:17:   { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5
configure.ac:17: printf "%s\n" "no" >&6; }
configure.ac:17: fi
configure.ac:17: 
configure.ac:17:   if test "x$ac_ct_CC" = x; then
configure.ac:17:     CC=""
configure.ac:17:   else
configure.ac:17:     case $cross_compiling:$ac_tool_warned in
configure.ac:17: yes: is m4_require'd but not m4_defun'd
./lib/autoconf/programs.m4:189: _AC_TOOL_WARN is expanded from...
./lib/autoconf/programs.m4:221: AC_CHECK_TOOL is expanded from...
./lib/autoconf/c.m4:460: AC_PROG_CC is expanded from...
configure.ac:17: the top level

[techee]

You are talking to a guy who does his best not to understand autotools to preserve his sanity ;-)

Anyway, if it's line 17, have you installed libtool? Also, have you successfully compiled and installed Geany too? geany-plugins will require the not yet released 2.1 version.

[RaphaelRochet]

Yeah that autotools thing looks crazy ... no clue what it's complaining about :(
I really made my best, libtool 2.5.4.23-5b58-dirty and geany 2.1 (git >= 876242d8b) .

[techee]

What exactly is on line 6447 where this error happens?

[RaphaelRochet]

6447 is the "yes:" line. Autogen outputs is m4_require'd but not m4_defun'd just after that line. But had no luck finding out what that means :(

I guess some chunk of code is missing here, causing that syntax error.

...
  if test "x$ac_ct_CC" = x; then
    CC=""
  else
    case $cross_compiling:$ac_tool_warned in
yes:

{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
printf "%s\n" "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
    CC=$ac_ct_CC
  fi
else
  CC="$ac_cv_prog_CC"
fi
...

[techee]

Interesting. The corresponding piece of code looks this way on my machine:

  if test "x$ac_ct_CC" = x; then
    CC=""
  else
    case $cross_compiling:$ac_tool_warned in
yes:)
{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
printf "%s\n" "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
    CC=$ac_ct_CC
  fi
else
  CC="$ac_cv_prog_CC"
fi

fi

The only differences I see is ) after yes: and no empty line after it. What happens if you modify it this way (stupid workaround but I have no idea why your output differs).

[RaphaelRochet]

Did it, unfortunately it fails later :

./configure: line 7293: syntax error near unexpected token `)'
./configure: line 7293: `)'

Line 7293 is the lonely ) here ... could it be the ) that was missing earlier .. man I feel my sanity is fading away quickly ...

...
 if
  test "x$enable_dependency_tracking" != xno \
  && test "$am_cv_CC_dependencies_compiler_type" = gcc3; then
  am__fastdepCC_TRUE=
  am__fastdepCC_FALSE='#'
else
  am__fastdepCC_TRUE='#'
  am__fastdepCC_FALSE=
fi

)

# Check whether --enable-static was given.
...

Will try to remove it. What can go wrong ...