Am 21.01.2012 19:10, schrieb Richard Everson:
[ ... ]
Hi Richard,
thanks a lot for the patch.
Could not look at it closer yet; just some ideas, as the completion
issues affects other reports/request too, true auto-completion is ahead.
(completion-at-point) says:
"Complete the thing at point according to local mode.
This runs the hook `completion-at-point-functions' until a member
returns non-nil."
That's basically the proceeding I'm heading to: py-complete-function
should hand over a list of completion-functions sorted with resp. to
environment.
So far just an idea.
As sometimes it might not be obvious what's the best path to choose, it
might be of interest having alternatives. Should you reach a point where
you want to see something, while a different path has been chosen here,
please don't hesitate to open a personal branch, so we may play with it.
All you need AFAIK is applying to be member of the team, which is
nothing more than a formality.
Am 21.01.2012 19:10, schrieb Richard Everson:
[ ... ]
Hi Richard,
thanks a lot for the patch.
Could not look at it closer yet; just some ideas, as the completion
issues affects other reports/request too, true auto-completion is ahead.
(completion- at-point) says:
"Complete the thing at point according to local mode. at-point- functions' until a member
This runs the hook `completion-
returns non-nil."
That's basically the proceeding I'm heading to: py-complete- function functions sorted with resp. to
should hand over a list of completion-
environment.
So far just an idea.
As sometimes it might not be obvious what's the best path to choose, it
might be of interest having alternatives. Should you reach a point where
you want to see something, while a different path has been chosen here,
please don't hesitate to open a personal branch, so we may play with it.
All you need AFAIK is applying to be member of the team, which is
nothing more than a formality.
Afterwards
bzr push lp:~MY-NAME/python-mode/MY-BRANCH
should do it.
So far from this morning,
Cheers,
Andreas