[issue27681] readline: consecutive rl_kill_word do not append

2016-08-04 Thread Quentin Santos

New submission from Quentin Santos:

In readline, "kill" basically means "cut" and "yank", "paste. When killing 
twice in a row, it tries to group the kills. This can be shown to work with 
rl_unix_word_rubout; with the default emacs keymap, type:

>>> hello world

Then hit ^W (Control+W, rl_unix_word_rubout) twice, then ^Y (Control+Y, 
rl_yank). You should get back the two words.

Now, using rl_backward_kill_word (Meta ^H), twice, yanking only puts back the 
last killed word (here, "hello "). With rl_kill_word (^A for start of line, 
then ^D), twice, yanking also puts back only the last killed word (here, " 
world"). The expected behavior is to get back both words (there, "hello world").

The behavior appears in both CPython's REPL (2.7 and 3.5 at least) and in the 
readline module. Other programs (bash, pypy, irb) that use readline show the 
expected behavior, as well as zsh (with its own implementation of readline).

Granted, I can not really imagine and issue with a lowest priority.

--
components: IO, Library (Lib)
messages: 271964
nosy: qsantos
priority: normal
severity: normal
status: open
title: readline: consecutive rl_kill_word do not append
versions: Python 2.7, Python 3.5

___
Python tracker 
<http://bugs.python.org/issue27681>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue27681] readline: consecutive rl_kill_word do not append

2016-08-04 Thread Quentin Santos

Quentin Santos added the comment:

I had not thought of checking gdb. Thanks for the information, I will look into 
that!

--

___
Python tracker 
<http://bugs.python.org/issue27681>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com