Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 178793
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Balint Dobai-Pataky <dpblnt@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
emerge.info emerge --info text/plain Balint Dobai-Pataky 2007-05-16 17:39 0000 3.49 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 178793 depends on: Show dependency tree
Bug 178793 blocks: 181943
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-05-16 17:38 0000
i have the inputrc from baselayout-1.12.10-r4
which includes 
"\e[5C": forward-word
which is not recognized by the new vte and thus i can't jump word backward in
mcedit, control+left_key in dosemu.
other keys are also broken, like
shift+down in mcedit.


Reproducible: Always

Steps to Reproduce:
1.upgrade to vte-0.16.0
2.open an xterminal or gnome-terminal 
3. open mcedit file
4. press control+left_key

------- Comment #1 From Balint Dobai-Pataky 2007-05-16 17:39:33 0000 -------
Created an attachment (id=119458) [details]
emerge --info

------- Comment #2 From Mart Raudsepp 2007-06-13 19:50:28 0000 -------
forward-word and backward-work don't work for me even in bash with vte-0.16.5
:(
I'll take a closer look at this when I have the rest of gnome 2.18 installed -
if someone manages to figure this one out earlier, I would appreciate

------- Comment #3 From Mart Raudsepp 2007-06-19 02:12:27 0000 -------
Seems to be a regression from http://bugzilla.gnome.org/show_bug.cgi?id=337252
and it's reopened and regression is discovered in later comments.
Meanwhile alt+left/right arrow works for backwards/forwards-char in bash
(readline?) but doesn't help for mcedit.

------- Comment #4 From Sebastian Rick Rijkers 2007-06-27 23:04:13 0000 -------
(In reply to comment #3)

The patch from comment #12 in that bug fixes the same issue I was having in VIM
with control+cursor keys.

------- Comment #5 From Daniel Gryniewicz 2007-07-27 13:44:13 0000 -------
Upstream patch added to 0.16.6-r1.

------- Comment #6 From Mart Raudsepp 2007-07-30 04:22:41 0000 -------
This patch doesn't seem to fix ctrl+left/right arrow cursor movement in
readline/bash for me, which is the most major regression in my book for 0.16.
Reopening for more research on this. Will try with 0.16.7 release soon.

------- Comment #7 From Balint Dobai-Pataky 2007-07-30 06:30:08 0000 -------
it fixes control+left/right, shift+down/up, shift+F5 for me, 
thanks.

------- Comment #8 From Mart Raudsepp 2007-07-30 09:25:01 0000 -------
(In reply to comment #7)
> it fixes control+left/right, shift+down/up, shift+F5 for me, 
> thanks.

In where does it fix control+left/right for you?
I think I get it fixed in things like midnight commander that are in the mode
where you can't scroll back (alternative mode I think), and it doesn't work for
bash, where alt+left/right work.
I'm starting to get the impression that's how it is supposed to work and it
just happened to also work with ctrl+left/right in bash before by accident in
gnome 2.16 or something like that.
So original report seems to be handled indeed, with mcedit shift+down and
ctrl+left in mcedit and vim working.

------- Comment #9 From Balint Dobai-Pataky 2007-07-30 11:21:41 0000 -------
fist i tested it in mcedit,
now i looked at it in bash, and it's strange: control+left jumps a word
backward, but control+right does not jump a word forward.
indeed, alt+right/left works in bash as expected.

------- Comment #10 From Simonas Leleiva 2007-09-20 09:49:47 0000 -------
The whole thing'd hit the stable gentoo. Solution for bash mcedit etc:

put these things in your /etc/inputrc next to gnome-terminal section about
(escape + arrow key)
"\e[1;5C": forward-word
"\e[1;5D": backward-word

Hope this fix hits ebuilds soon as well

(thread on this: http://forums.gentoo.org/viewtopic-p-4115692-highlight-.html)

------- Comment #11 From Simonas Leleiva 2007-12-10 09:32:39 0000 -------
C'mon, guys, my baselayout's just gotten updated today to 1.12.9-r2, and
/etc/inputrc again got dispatch-conf`ed to the one _without_ essential lines

"\e[1;5C": forward-word
"\e[1;5D": backward-word


So when are you going to inject this thing into portage?

------- Comment #12 From Mart Raudsepp 2007-12-10 09:44:17 0000 -------
base-system, what's your view on this?

------- Comment #13 From SpanKY 2008-01-16 02:03:15 0000 -------
people seem to be confused about inputrc.  it is merely a configuration file. 
it is not required whatsoever for proper behavior on a system.  the *defaults*
in it are there *only* as a convenience.  the file is intended for modification
and customization *by end users*.  i could just as soon as not add any lines at
all to the file and make users uncomment them *as they want*.  this is exactly
what many other distributions do.

claiming that the existence (or lack) of any line in /etc/inputrc as a bug is
incorrect.

------- Comment #14 From Gilles Dartiguelongue 2009-01-11 23:00:33 0000 -------
closing fixed per upstream status bug and comment from base-system.

If you want customization of /etc/inputrc, please contact baselayout
maintainer.
Thanks for reporting.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug