Re: Numbering invisible parts

[Shenghuo ZHU <zsh@cs.rochester.edu>]

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic@srce.hr> writes:

[...]


Hrvoje> Thanks; this is cool, although it breaks the usual
Hrvoje> "no-argument-means-1" assumption with cooked numerical
Hrvoje> prefixes.

Hrvoje> However, it only partially fixes my problem, because I would
Hrvoje> like `1 b' (or just b) to work on the first button I see, `2
Hrvoje> b' on the second, etc.

Hrvoje> Maybe numbering invisible parts should be an option?  I never
Hrvoje> want to number invisible parts, while Kai always wants to
Hrvoje> number them.  Sounds like we need an option to settle our
Hrvoje> differences.  :-)

The numbers come from dissecting function. They are kinda like the IDs
of parts. Though some buttons are displayed, they need ID.

Suppose a complicated case like (message/rfc822 is an attachment part)

[1. multipart/mixed]
        [2. message/rfc822]
                [7. multipart/mixed]
                        [8. image/jpeg]
                        [9. text/plain]
        [3. multipart/mixed]
                [4. image/gif]
                [5. text/html]
        [6. image/bmp]

Why I got such numbered buttons? Because part message/rfc822 is
dissected when it is displayed. So we get unordered buttons.

Suppose we could number the buttons in order. How about (un)display
the message/rfc822 button?  We still get non-contiguous buttons. (In
pGnus, undisplaying a button does not affect its sibling buttons.  I
don't think relabeling them is reasonable.)

-- 
Shenghuo ZHU