It is currently expected that UIs will figure out when to hide msg_history_show messages by themselves.

I think this is bad for two reasons:

• It makes UIs less similar, increasing the number of things to learn when going from one UI to another.
• It makes UIs different from the TUI, which offers a press ENTER prompt when the time to hide msg_history_show messages has come.

After [di

Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef

Improve Docs

Please describe which part of docs should be improved or typo fixed

Currently in getting-started, there would always be a $ at the front of each command, which makes users hard to do three-click to directly copy the whole command and run without modification. They have to manually delete `

Issue

i am trying to uninstall my previous installed conky from source with:
sudo make uninstall
but make is complaining that there is no rule for uninstalling.

Link to the page

theme.bg_normal and theme.fg_normal appear 5 times each; theme.bg_systray, theme.border_width, theme.font and theme.useless_gap appear 2 times each.

Command used to check duplicates:

$ cat theme.lua
local theme = {}

-- Default variables
-- theme.bg_normal = nil
[...]
-- theme.wibar_s

Our coverity (scan.coverity.com) reports about dead code (CWE-561)
in cases where variable of type struct errinj * is compared with
NULL at if condition. Dead code appears due to function-like macro
errinj() always returns NULL at non-debug version, so execution
never goes into if block.

Examples of such cases:

• https://github.com/tar