Avoid declaring ac-trigger-commands and company-begin-commands locally

[purcell]

No description provided.

[abo-abo]

If I'm not mistaken, there's an actual problem with your approach
that's bigger than the potential problem that you're trying to solve:

(require 'worf)
(require 'auto-complete)

means that ac-trigger-commands will not be modified and the automatic completion
will not work in worf-mode at all. And 99% of the time, ac-trigger-commands will
just stay at '(self-insert-command) anyway.

Of course this will work, but there's no way to guarantee the order:

(require 'auto-complete)
(require 'worf)

[purcell]

I see your point: neither solution is clean when the code is run at load-time. I guess that in the end, I'd personally add separate "worf-ac-setup" and "worf-company-setup" functions, and do the magic explicitly in there rather than implicitly when the file is required.

P.S. I noticed you're using projectile-find-file, but you don't require or depend on projectile.