Bug 3988 - "Run on select" is not documented
Summary: "Run on select" is not documented
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.16.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2018-03-14 16:28 UTC by George
Modified: 2018-03-14 17:38 UTC (History)
0 users

See Also:


Attachments

Description George 2018-03-14 16:28:31 UTC
The manual doesn't mention what "Run on select" does (Quick search).
Comment 1 Paul 2018-03-14 16:46:48 UTC
not a bug
Comment 2 George 2018-03-14 16:52:20 UTC
Well, it may be considered a documentation bug. In any case: please document it.
Comment 3 Paul 2018-03-14 16:56:17 UTC
well, what do you think 'run on select' could do with a name like that? Could it possibly run the filter when you select it from the dropdown list, as opposed to pressing Enter to run the selected rule?
Comment 4 Paul 2018-03-14 16:57:27 UTC
besides, a 'documentation bug' is surely documentation which is wrong and not missing documentation, wouldn't you say?
Comment 5 George 2018-03-14 17:38:34 UTC
> well, what do you think 'run on select' could do with a name like that?

If I knew, I wouldn't look for documentation :)

> Could it possibly run the filter when you select it from the dropdown list, as opposed to pressing Enter to run the selected rule?

It could also mean "run the filter on selecting a folder". But without clarification it is a guess work.

> besides, a 'documentation bug' is surely documentation which is wrong and not missing documentation, wouldn't you say?

Not necessarily. Something missing or incomplete could also be an issue leading to confusion, guess work and from that unexpected results which can damage user data.

Some software projects deliberately have separate branches or even separate bugzilla's for such requests. As this one has only one bugzilla - I reported it here.

Is it a problem to write 1-2 sentences in the manual saying what it does? Or should it remain deliberately non-documented just to prove that it is not a bug? :)

Note You need to log in before you can comment on or make changes to this bug.