problem: how to disable project files from semantic autocomplete.

problem: how to disable project files from semantic autocomplete.

[Paul K]

Hallo Group.

I'm working with large C++ project where cedet freezes for a very long time
at autocompletion.
What I really require from cedet/semantic is to autocomplete from linux
system libraries, ie it does not have to complete from project C++ files.

Thus my idea is to remove `project' from throttle:

(setq semanticdb-find-default-throttle '(unloaded system recursive))

Unfortunatelly it does not do the job, ie. my project C++ files are still
parsed/searched at auto completion thus auto completion time is very long.

Some env details:

emacs-version is a variable defined in `C source code'.
Its value is "24.3.1"

auto-complete is an installed package.
    Version: 20140414.2324

cedet-version is a variable defined in `cedet.el'.
Its value is "2.0"

my C++ project file:
semanticdb-find-default-throttle is a variable defined in `db-find.el'.
Its value is (local unloaded system recursive)

Re: problem: how to disable project files from semantic autocomplete.

[Emanuel Berg]

Paul K <mafeuser@gmail.com> writes:

> I'm working with large C++ project where cedet
> freezes for a very long time at autocompletion.  What
> I really require from cedet/semantic is to
> autocomplete from linux system libraries, ie it does
> not have to complete from project C++ files.

Are you autocompleting the file *names*, or functions,
variable names, etc., inside those files?

I can't say I recommend autocompletion, in either
case. It doesn't save you time, is my experience,
instead it makes for a bumpy ride - it is
error-prone. There is always this programmer -
frustrated, hitting everything in sight, jumping up and
down trying to "save time" (I'm not saying you are like
this, I have never seen you - just saying it is common
computer character) - and they always hammer the
keyboard like it is a drumset. I think it is much
better to learn to *type*, and then to keep the modules
neat and files small, and to have clear, not-too-long
common names (that are easy to spell) for
everything. Only in those stinking M$ Visual Basic and
Access DB interfaces is Hungarian notation and
autocompletion perhaps just a bit usable because in
those if you setup a dialog and an "OK" button, that
creates *a zillion* items and they are impossible to
remember otherwise.

But -

For filenames, if you use Dired, check out

completion-ignored-extensions is a variable defined in
`C source code'.

Its value is (".o" "~" ".bin" ".lbin" ".so" ".a" ".ln"
".blg" ".bbl" ".elc" ".lof" ".glo" ".idx" ".lot"
".svn/" ".hg/" ".git/" ".bzr/" "CVS/" "_darcs/" "_MTN/"
".fmt" ".tfm" ".class" ".fas" ".lib" ".mem" ".x86f"
".sparcf" ".dfsl" ".pfsl" ".d64fsl" ".p64fsl"
".lx64fsl" ".lx32fsl" ".dx64fsl" ".dx32fsl" ".fx64fsl"
".fx32fsl" ".sx64fsl" ".sx32fsl" ".wx64fsl" ".wx32fsl"
".fasl" ".ufsl" ".fsl" ".dxl" ".lo" ".la" ".gmo" ".mo"
".toc" ".aux" ".cp" ".fn" ".ky" ".pg" ".tp" ".vr"
".cps" ".fns" ".kys" ".pgs" ".tps" ".vrs" ".pyc"
".pyo")

Documentation: Completion ignores file names ending in
any string in this list.  It does not ignore them if
all possible completions end in one of these strings or
when displaying a list of completions.  It ignores
directory names if they match any string in this list
which ends in a slash.

-- 
underground experts united:
http://user.it.uu.se/~embe8573