[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    =?UTF-8?B?UmU6IC0taW50ZXJhY3RpdmUgbW9kZTogcmVhZGxpbmUgc3VwcG9ydCDijKjirIY=?=
From:       Martin_Ågren <martin.agren () gmail ! com>
Date:       2017-07-20 11:50:37
Message-ID: CAN0heSqsn-XGgZFxc+kLiBPSdzrtqg6JR4_g9062F+jZmLu0Bg () mail ! gmail ! com
[Download RAW message or body]

On 20 July 2017 at 11:20, Marcel Partap <mpartap@gmx.net> wrote:
> So the readline library powers the advanced line editing capabilities beh=
ind f.e. the bash or the ipython shell. Besides navigating with the cursor =
keys, it provides a history function accessible by the up cursor key =E2=8C=
=A8=E2=AC=86 .
> At the moment, git interactive mode seems (?) not to make use of it, so t=
here's no line editing at all. A typo at the beginning of a line must be co=
rrected by reverse deleting up to it, then retyping the rest unchanged. Wit=
h readline, the home/end keys for jumping to beginning or end work, as do t=
he left/right keys in a familiar way.
> The history function comes in handy when f.e. repeatedly using `git clean=
 -i` and feeding the "filter by pattern" command a string like "*.patch". L=
ike, that's the use case that prompted me to write to this list. : )

Ok, I see. When I saw your first mail, I was thinking about "git
rebase -i" and thought, "how could that possibly help?". :) I have no
idea what it would take to implement this (portably!) in git.

Martin
[prev in list] [next in list] [prev in thread] [next in thread]