zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: TAB and PS2 and multiline buffers and vared
Date: Thu, 25 May 2000 15:20:17 +0000	[thread overview]
Message-ID: <1000525152017.ZM2840@candle.brasslantern.com> (raw)
In-Reply-To: <200005250757.JAA32547@beta.informatik.hu-berlin.de>

On May 25,  9:57am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: Re: TAB and PS2 and multiline buffers and vared
}
} Bart Schaefer wrote:
} 
} > The test case was to run `vared functions[_complete_debug]', scroll up
} > to the line `local w="${(qq)words}"', then type ^E ESC RET to open a
} > line, and begin completing on that line.
} 
} The fact that you used `functions[_complete_debug]' was an important
} information, because with that I found a buglet in _in_vared that made 
} _value complete alternatingly assoc keys and values, as if for a
} assingment to $functions.

Aha!

} I still can't see why it completed commands, but it might have
} something to do with this (I could understand it if you had tried it
} with commands[...]).

Actually, although I hadn't noticed it before, the number of completions
offered changes depending on which variable I'm editing, so that probably
is in fact the issue.  If it's still broken after the patch I'll let you
know.

} There is another thing I noticed: ^X? with only one match did not show 
} the _message, because with only one match it didn't show the list at
} all. The patch fixes this in _complete_debug.

Aha, again.  That explains another "bug" I was about to report.

} Hm, should we change the C-code to enforce showing the list when a
} `compadd -x' message was added (that *seems* sensible, but I think
} there may also be cases where one doesn't want that)? Alternatively,
} we could enhance $compstate[list]: if it contains `messages', only the 
} messages are shown (like the `explanations' we have now).

Either or both.  I don't have a strong opinion, at least not yet.

} Well, another thing I noticed is that with a really large prompt and
} completion list scrolling it doesn't stop at the end of the list, so
} that the re-printed prompt scrolls most of the list out of the
} screen. So the patch makes it wait at the very end, allowing us to
} have a look at the whole list before printing the next prompt.

Yay!  Yet another thing I was about to report.  You're batting 300% on
this one.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~2000-05-25 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-25  7:57 Sven Wischnowsky
2000-05-25 15:20 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-31  9:53 Sven Wischnowsky
2000-05-22 14:44 Sven Wischnowsky
2000-05-22 16:52 ` Bart Schaefer
2000-05-22 11:25 Sven Wischnowsky
2000-05-22 14:27 ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1000525152017.ZM2840@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).