Ben Wing <ben(a)666.com> writes:
I think this is a good idea -- it is really not very much work to
add a specifier like this.
I've now looked at the specifier code, and decided that I have no clue
how to implement this. I started out with something like this:
DEFVAR_SPECIFIER ("vertical-scrollbar-visible-p",
&Vvertical_scrollbar_visible_p /*
*Whether the vertical scrollbar is visible.
This is a specifier; use `set-specifier' to change it.
*/ );
Vvertical_scrollbar_visible_p = make_specifier (Qboolean);
set_specifier_fallback (Vvertical_scrollbar_visible_p,
list1 (Fcons (Qnil, Qt)));
set_specifier_caching (Vvertical_scrollbar_visible_p,
slot_offset (struct window,
vertical_scrollbar_visible_p),
some_window_value_changed,
slot_offset (struct frame,
vertical_scrollbar_visible_p),
vertical_scrollbar_visible_p_changed_in_frame);
But it seems non-obvious what each of these functions (like, say,
vertical_scrollbar_visible_p_changed_in_frame) should do, and how the
caches work out.
Horizontal scrollbar is tougher, because it depends on other things,
like truncate-lines and truncate-partial-width-windows. What should
be the semantics of setting this specifier?
So, if you want to have these two specifiers by 21.0, someone else
will have to implement them. Kirill?
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Unspeakable horrors from outer space paralyze the living and
resurrect the dead!