Bug 401246

Summary:	Unclear shortcut descriptions "In this session", "For this session"
Product:	[Applications] yakuake	Reporter:	Simone Gaiarin <simgunz>
Component:	general	Assignee:	Eike Hein <hein>
Status:	CONFIRMED ---
Severity:	normal	CC:	kde-bugzilla
Priority:	NOR
Version First Reported In:	3.0.5
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Simone Gaiarin 2018-11-20 18:47:45 UTC

SUMMARY
There are some descriptions of some shortcuts that are unclear and some repeat as well. They are:
- In this Session (repeated twice)
- For this session

What do they mean?

I think the description should be made more explicit.

Comment 1 BAKfr 2018-12-13 20:57:11 UTC

I've checked and I didn't find the shortcuts your describe.
You're talking about the "Action" column on the "Configure Shortcuts" window, right ? If not, could you describe where to find them more precisely ? 

Also, do you use a locale other than English ?

Comment 2 Simone Gaiarin 2018-12-13 21:18:17 UTC

Yes the "Action" column. I just tried again now to take a screenshot, and they are not there anymore. 

Though these actions are present in the source code (at least I am not becoming crazy :-) )
https://github.com/panzi/Yakuake/blob/master/app/tabbar.cpp

...figured out while writing this:

if you open a second terminal in the same tab (Right click on the tab name > Split Left/Right) then the context menu of the tab (Right click on the tab name) has new items. In particular:
"Monitor for activity > In this session"
"Monitor for silence > In this session"
"Disable keyboard input > For this session"

At this point, these new actions are also available in the "Configure shortcuts" dialog, but these actions are meaningless there because are not connected to the "parent item" as it happens in the menu.

Comment 3 Justin Zobel 2023-01-19 00:18:41 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!