Re: Anybody else hitting completion errors on accept?

• To: Scott McKay <SWM@sapsucker.scrc.symbolics.com>
• Subject: Re: Anybody else hitting completion errors on accept?
• From: Peter Karp <pkarp>
• Date: Wed, 1 Jan 92 8:55:43 PST
• Cc: clim@BBN.COM, clim-support@lucid.com
• In-Reply-To: Your message of Tue, 31 Dec 1991 13:28-0500

> In the command processor, hitting the Space key or the Input Editor's
> history yank command (control-meta-Y, or is it Escape control-Y under
> Allegro?)  should yank the default into the input buffer.  I recently
> also fixed a bug that caused a blowout when you typed a completion
> character to non-completing types such as INTEGER.

I have yet to ever get defaults to work under Lucid CLIM on a Sparc.
When, for example, I do clim:accept on a string with a default and a
prompt supplied, both the default and the prompt appear, but neither
space nor ESC ctl-Y nor ctl-meta-Y have any effect.  That is, they do
not cause the default that appears in the prompt to be placed in the
input buffer.

Peter

• Anybody else hitting completion errors on accept?
• From: John Kern <kern@lucid.com>

• Prev: problems with type specifier of the clim::accept function
• Next: Does ink affect non-drawn text?
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)