On 31/10/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 10/31/06, A. S. Budden <[EMAIL PROTECTED]> wrote:
> On 27/10/06, Benji Fisher <[EMAIL PROTECTED]> wrote:
> > On Fri, Oct 27, 2006 at 04:46:02PM +0100, A. S. Budden wrote:
> > > Dear all,
> > >
> > > I've recently started using the CleverTab function below, modified from
> > > the bottom of the comments page on tip 102. This is brilliant from my
> > > point of view:
> > >
> > > - tab produces tabs at the start of the line for indenting*;
> > > - tab shows the longest unique option in the omnicomplete list
> > > when using omnicompletion;
> > > - tab cycles through the list of completions if the popup menu is
> > > visible but omnicompletion isn't used;
> > > - otherwise, it returns a tab.
> > >
> > > What I'd like to do is change the last one of those so that it puts in
> > > enough spaces to reach the next tabstop so that good formatting is
> > > maintained regardless of the tabstop setting on a users editor.
> > >
> > > However, I can't figure out how to achieve this.
> > >
> > > The 'expandtab' option is no use as it will change the tabs at the start
> > > of the line (used for indentation) to spaces, which will result in a
> > > really badly formatted piece of source code (as it is edited by several
> > > people who all like different tab stops)*. Similarly, replacing "\<Tab>"
> > > in the last return line with " " is no use as it will always insert
> > > four spaces, even if we're halfway through a tab stop (it's also not
> > > very flexible for different tabstop settings).
> > >
> > > Can anyone offer any suggestions for this?
> > [snip]
> >
> > The 'expandtab' option does not affect existing tabs in the file
> > (unless you :retab) so it should be safe to have your function reset/set
> > it depending on whether you are at the start of the line or not. I have
> > not tested this.
>
> Many thanks for your help Benji, both suggestions look useful. I've
> been playing around with the first option (as the code _should_ be a bit
> neater I think), but I'd quite like to ensure that expandtab is left off
> at the end of the insertion (as I'd like to be able to enable and
> disable use of CleverTab).
>
> The problem with this is that inside one of the 'if/elseif/else' blocks,
> I need to set expandtab, print something into the insert buffer and then
> reset expandtab. I'm struggling with this, despite having played around
> with lots of possibilities and done what I feel is a fairly
> comprehensive trawl of the documentation.
>
> What I've tried:
>
> ---
> let &expandtab = 1
> return "\<Tab>"
> let &expandtab = 0 " Never gets executed
> ---
> let &expandtab = 1
> feedkeys("\<Tab>", 'n') " Gets executed AFTER the return
> let &expandtab = 0
> return ""
Try this:
set &expandtab = 1
call feedkeys("\<Tab>\<C-O>:set noet\n", 'n')
Ah!
I'd tried it without the "\" before the <C-O> and it hadn't worked
(forgot to mention it earlier!), but hadn't thought to escape it.
Thanks for that.
Ok, that leads me on to the next question (and I suspect that this is
slightly more challenging). I've made a couple of changes to the
CleverTab script such that the first test looks for "^\t*$" instead of
\s and such that the test for a space now looks for "\A" (i.e. only
using omnifunc if after likely object name). This is working really
well, but falls down in the following situation:
I type (underscore substituted for space; <AI-*> to indicate vim's
autoindenting and <-*> is a TAB):
if_(x_==_1)
{
<AI---->x_=_1;<><------>//_This_is_a_comment<ENTER>
<AI---->_<-----><------>//_that_continues<ENTER>
<AI-------------------->//_onto_the_following_lines
<A FEW BACKSPACES>
}
I get:
if_(x_==_1)
{
<------>x_=_1;__________//_This_is_a_comment
<------>________________//_that_continues
<------><------><------>//_onto_the_following_lines
}
The third line should be:
<------>________________//_onto_the_following_lines
Did that make sense?
The key problem here is that the autoindenting is, rather
understandably, using tabs to achieve the indent, but if another
developer works on the code with ts set to something different, the
comment on the third line won't line up.
Has anyone got any suggestions or am I asking too much from my editor?!
Cheers,
Al
