Bug 69014 - Mark text with keyboard
Summary: Mark text with keyboard
Status: RESOLVED DUPLICATE of bug 100317
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-25 18:23 UTC by Claes
Modified: 2007-06-02 16:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claes 2003-11-25 18:23:17 UTC
Version:            (using KDE KDE 3.1)
Installed from:    SuSE RPMs

It would be very useful if it was possible to mark text on the screen or in the history with the keyboard (as alternative to using the mouse). Instead of selecting this text with the mouse, I imagine it could be possible to enter a "mark mode" which is used to select instead of enter text. Selecting the text would work like in a regular text editor. That is - move the cursor with the arrow keys and select text with for example shift + arrow keys. After this, enter "regular mode" again and paste the selected text in regular manner.

The purpose is to provide mouseless operations when working on the prompt. A common use case is to grep after files, and after that use some of their paths on the command line. Today, this is most easily done by copying the path from the history to the command line with the mouse. I would like to do this pasting by only using the keyboard. 

This would be a big advantage since it would allow all operations to be performed without using the mouse. Apart from being convenient, it would allow better ergonomy when working with Konsole.
Comment 1 Dennis P. Nikolaenko 2006-12-06 15:20:29 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 Robert Knight 2007-06-02 16:46:58 UTC
Marked as duplicated of 100317, that report has more comments and more votes, so it makes sense to make it the main report for this problem even though it is newer.

*** This bug has been marked as a duplicate of 100317 ***