Several small issues

[Martin Pohlack]

Hi Marc,

[...]

>>>You again should have a look at the manpage (just search for scroll). In any
>>>case, read the manpage! Really, do it!
>>
>>Rest assured that I did this (for quite some time) before posting here
>>(my posted config might indicate this too).
> 
> 
> I must admit that I would have expected questions like "secondary screen
> scroll seems to be enabled, but it still doesn't work". It helps to know
> what you already tried or not, and a "it doesn't work" sounds very much
> like "I didn't even look at the manpage". Sorry for that.

Eh yes, I suppose I could have expressed myself more clearly, but I was
not so sure whether I was going into the right direction anyway with my
sec. screen assessment.

>>I would like to suggest a slight improvement to the manpage here (and
>>other similar parts):
>>
>>...
>>      -ssc|+ssc
>>           Turn on/off secondary screen (default enabled); resource
>>           secondaryScreen.
>>...
>>
>>The order "-ssc|+ssc" and "on/off" is either wrong or the option naming
>>is misleading.  '-' should be associated with turning something 'off'
>>and '+' with turning something 'on', both should be listed in the same
>>order to reduce confusion -> off/on
> 
> 
> No, the wording is right, and the logic is correct, too. "-" _always_
> turns options on, and "+" turns them off in programs that allow single
> toggling options.
> 
> According to your loginb, you'd have to write
> 
>    rm +f xxx
> 
> instead of
> 
>    rm -f xxx
> 
> To enable the force option.

Nooooooooo.  I would never assume to make such a big change in the world
;-).

I was refering to simple binary switches where the program does know the
+ and the - version (which rm does not for -f).

E.g. take xset:

  +dpms enables DPMS and -dpms disables it.
  -fp removes something +fp adds something to the font path.

> I do admit that - is not the most convincing on-switch, but its out of
> my control, its traditional behaviour. Changing it would break many existing
> scripts and would make its behaviour inconsistent with other apps.

Ok, but maybe this could be shown more clearly in the manpage.  Xset's
manpage for example splits the entries for +dpms and -dpms.  However I
don't like the repeating of many words.  How about:

Old version:

      -ssc|+ssc
           Turn on/off secondary screen (default enabled); resource
           secondaryScreen.

New version:

      -ssc
           Turn on secondary screen (default); resource
           secondaryScreen.

      +ssc
           Turns the secondary screen off.

>>http://lists.schmorp.de/pipermail/rxvt-unicode/2006q1/000177.html
> 
> 
> Wow, you even researched the list archive, now I'm impressed :)

:-/.  You are kidding, right?

Personally, I think researching such an issue before hand with man pages
/ google / ... is much faster than waiting for an answer from someone
else ...

>>:-) Thanks again, but I don't see how spending even more time in the
>>manpage would have helped me here.
> 
> 
> I agree. Now, you should have mentioned your progress so far, that would
> likely have reduced the time we both spent to find out wether you looked at
> those options or not :)

Ack.  I'm usually not the --verbose type ...

Cheers,
Martin


PS.: For the archive, I solved the first problem with the following
lines in my .Xdefaults:

...
URxvt.keysym.KP_Multiply:   *
URxvt.keysym.KP_Subtract:   -
URxvt.keysym.KP_Add:        +
...