#122 Documentation for rangeset modes

closed-accepted
nobody
5
2004-09-08
2004-08-19
Tony Balinski
No

This is in response to the bug "[ 1005442 ]
documentation for rangeset_set_mode( r, type ) not
clear" - hopefully it makes the meaning of the
different modification behaviour modes clearer.

Discussion

  • Tony Balinski
    Tony Balinski
    2004-08-19

    cvs diff -u on help.etx (of today)

     
  • Thorsten Haude
    Thorsten Haude
    2004-08-19

    Logged In: YES
    user_id=119143

    The different modes are explained very good.

    The introduction is a bit heavy. I'm not sure how to improve
    this though. A soothing statement like "you normally don't
    have to care" would help, as would a diagram.

     
  • Nathan Gray
    Nathan Gray
    2004-08-19

    Logged In: YES
    user_id=121553

    This text looks good to me. The only criticism I have is that the rangeset
    macro subroutines should be documented along with the rest of the
    subroutines, not in their own section. It might still be good to have a
    separate section describing range sets and their usage, but the functions
    themselves should be documented with the other macro functions,
    perhaps with a link to the detailed rangeset information.

     
  • Tony Balinski
    Tony Balinski
    2004-08-19

    Logged In: YES
    user_id=618141

    Putting all built-in functions into one help page would make
    for a huge page. I'm not sure that's advisable. As it is, the
    current structure is that of 5.4 (which has another page
    for highlighting information functions too).

    Thorsten is probably right: my intro to the mode options
    repeats a little of what is already mentioned further up
    (maintenance of range positions etc). I don't know. He's
    also right that generally you don't need to change modes
    usually.

     
  • Tony Balinski
    Tony Balinski
    2004-09-08

    • status: open --> closed-accepted
     
  • Tony Balinski
    Tony Balinski
    2004-09-08

    Logged In: YES
    user_id=618141

    Already integrated into NEdit 5.5