auto completion offers builtins and file functions for octave (bug #41371) * file-editor-tab.cc (update_lexer): read settings whether builtin and file functions should also be considered in auto completion for octave files; when functions are also displayed, updating of the files with prepared auto completion informations depends on last modification date of package lists; (add_octave_apis): new function for adding strings to the lexer APIs from the internal octave functions * file-editor-tab.h (add_octave_apis): new function * main-window.cc (handle_octave_ready): call function for creating the empty tab in the editor here because all octave functions must be known for creating the auto completion information * settings-dialog.ui: new checkboxes for auto completion of octaves buitlin and file functions * settings-dialog.cc (constructor): read states for new checkboxes from the settings file; (write_changed_settings): write states of new checkboxes into the settings file

syntax: regexp
# The recurrent (^|/) idiom in the regexps below should be understood
# to mean "at any directory" while the ^ idiom means "from the
# project's top-level directory".

# gnulib makes these silly backup files
.~$

# This directory gets created by gnulib during the build. 
# It contains no Octave files.
^libgnu/*

# This directory mostly contains cruft during build time, but it does
# contain some Octave code, so we gotta be a bit more careful about
# what we ignore here
^m4/(?!ax_).+\.m4$

# Emacs tools create these
(^|/)TAGS$
(^|/)semantic.cache$

(/|^)Makefile\.in$
^INSTALL$

^aclocal\.m4$
^build-.*($|/)
^configure$
^autom4te\.cache($|/)
^config\.in\.h$

# e.g. doc/faq/OctaveFAQ.info
#      doc/interpreter/octave.info-4
^doc/.*\.info(-\d)?$

^doc/\w*/stamp-vti$
^doc/\w*/version\.texi$
^doc/interpreter/images\.mk$

# e.g. liboctave/operators/smx-op-inc.mk
^liboctave/operators/\w+-op-\w+\.mk$

^libinterp/dldfcn/module\.mk$