Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 125881 - HOME and END keys don't work in less
Summary: HOME and END keys don't work in less
Keywords:
Status: CLOSED DUPLICATE of bug 122815
Alias: None
Product: Fedora
Classification: Fedora
Component: less
Version: 2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-13 05:46 UTC by Ian Laurie
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:04:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ian Laurie 2004-06-13 05:46:40 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
In less the HOME and END keys do not work, but the corresponding "g"
and "G" keys do.  Even when lesskey is used to generate a local .less
file you cannot get the HOME and END keys to function.

HOME and END work fine in other applications.

Version-Release number of selected component (if applicable):
less-382-3

How reproducible:
Always

Steps to Reproduce:
1. Run the command "less /etc/services"
2. Try and use the HOME or END keys.
3.
    

Actual Results:  The HOME and END keys do nothing, even when entries
exist for them in .lesskey and a new .less file was generated from it.

Expected Results:  HOME and END should work as they did in Fedora Core 1.

Additional info:

HOME and END do work just fine in other apps.
Comment 1 Karsten Hopp 2004-06-13 17:52:52 UTC 

*** This bug has been marked as a duplicate of 122815 ***
Comment 2 Red Hat Bugzilla 2006-02-21 19:04:03 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.