Re: display question: should ^N and \NNN widths be fixed?

[Richard Stallman]

       + make indent.c C column vars float
       + make callers of indent.c C functions cast retval to int
       + make indent.c C getter functions compute and return float
       - make callers of indent.c C functions cast args to float
       - make indent.c C setter functions accept floats

This seems like the right first step.

     - selectively expand contour to propagate float usage
       - determine criteria for propagation
       - determine which funcs/vars fit that criteria (maybe all?)
       - do the changes where needed
         - remove casts
         - fix resulting breakage

That seems reasonable too.

     - introduce font sensitivity in column computations
       - unify current_column / current_column_1 / string_display_width
       - consult font text-property             <-- potential race condition?

This code is all serial; it can't have race conditions.  Why did you
think there was one?  Perhaps that is a misunderstanding that is worth
identifying so we can clear it up now.

    logistical questions: is it ok to make a branch in cvs?  what should it
    be named?

Yes.  It could be called float-indent.  Eli can help you set it up.

    is it ok to check in the above in etc/TODO?

There is no need.  You know it.