Re: More ion-configuration (was Re: problem with queries on man-pages and sed?)

On 2007-01-26, Jurjen Middendorp <[email protected]> wrote:
> No i ment WEdln.complete() (which is bind to tab). What is the old
> tab-completion model?

The usual tab-completion model: Hit tab. If there's only one completion,
it is substituted into the query line. If there are multiple, they're
displayed, and only the common part substituted into the query line.
You can get this with mod_query.set{autoshowcompl=false}. (Well, could
-- apparently there's a segfault problem in the present release.)

> - Is there some more documention on (or in) the ion code somewhere besides
>   the listing of classes in the ion manual? 

No. It should all be self-evident :).

> - the completions are in the edln->compl_list thing? 

Maybe. Probably.

> - edln is the non-visual part and the edit-line and Wedln is the other way
>   around right?

Yep, Edln is the low-level line editor in no way tied to the UI, whereas
WEdln is the the Ion query line UI to it. I had to write Edln, because
all the other line editors available (libreadline and was it editline?)
seem tied to the TTY with no abstraction away from it. (Plus libreadline
sucks for being GPL.)

> - anyway, i think ioncore.create_ws(_,my_ws_params,true) will do what i
>   want, but is _ for the first parameter the current WScreen (also known
>   as the right option)?

Depends on where the call is. In the default configruation, it IIRC is in 
the WScreen bindings, so yes.

> - Is there a way to make Ion obey the maximum window size hints (WM_SIZE_HINTS)
>   throug winprops so they only work for some programs?  I cannot make
>   windows smaller then the application wants, but i can make the window
>   bigger which sometimes is annoying because some programs stay at 1 size

Maybe. Maybe there is already a suitable winprops. RTFM.

-- 
Tuomo