On 12/13/12 at 03:20pm, Eric Pruitt wrote:
> Hey Manolo,
>
> On Thu, Dec 13, 2012 at 03:04:01PM -0500, Manolo Martínez wrote:
> > I was wondering if anyone knows of a patch that provides the means to
> > return to the previously focused window (if it exists). That is, for
> > example, if I'm
> > o
On 12/13/12 at 10:16pm, Andreas Amann wrote:
> On Thu, Dec 13, 2012 at 03:04:01PM -0500, Manolo Martínez wrote:
> > Hello,
> >
> > I was wondering if anyone knows of a patch that provides the means to
> > return to the previously focused window (if it exists). That is, for
> > example, if I'm
> >
Hey Manolo,
On Thu, Dec 13, 2012 at 03:04:01PM -0500, Manolo Martínez wrote:
> I was wondering if anyone knows of a patch that provides the means to
> return to the previously focused window (if it exists). That is, for
> example, if I'm
> on window1 and launch a window2, MOD+p (say) would take me
On Thu, Dec 13, 2012 at 03:04:01PM -0500, Manolo Martínez wrote:
> Hello,
>
> I was wondering if anyone knows of a patch that provides the means to
> return to the previously focused window (if it exists). That is, for
> example, if I'm
> on window1 and launch a window2, MOD+p (say) would take me
Hello,
I was wondering if anyone knows of a patch that provides the means to
return to the previously focused window (if it exists). That is, for
example, if I'm
on window1 and launch a window2, MOD+p (say) would take me back to
window1.
Thanks
Manolo
--
Greetings.
On Thu, 13 Dec 2012 20:46:11 +0100 "Benjamin R. Haskell"
wrote:
> On Thu, 13 Dec 2012, Roberto E. Vargas Caballero wrote:
>
> >> Looking in the repository I can see that the commit 16ccf (Fix tab
> >> key) inserted this code, and I have tested that is such commit it was
> >> workin
> But, it's error-prone to have two places to keep track of what keys
> get mapped. So, I fixed this for myself a while ago by removing
> mappedkeys entirely. Patch attached.
I agree with you that it is error-prone, but if we remove it then each time
a key is pressed it is necessary look up in
On Thu, 13 Dec 2012, Roberto E. Vargas Caballero wrote:
Looking in the repository I can see that the commit 16ccf (Fix tab
key) inserted this code, and I have tested that is such commit it was
working, so we have a regression. I am going try now a bisection and
try locate which commit broken t
> Looking in the repository I can see that the commit 16ccf (Fix tab key)
> inserted this code, and I have tested that is such commit it was working, so
> we have a regression. I am going try now a bisection and try locate which
> commit broken this key.
The bisect indicates that the commit which
On Thu, Dec 13, 2012 at 10:49:22AM +0200, Edgaras wrote:
> I use Vim, and there you can cycle forward through completion using "Tab" and
> backward using "Shift+Tab", this does not work in st, but it works in xterm. I
> tested against tip.
Using xev I see that X server sends ISO_Left_Tab event, an
Am 11.12.2012 um 18:34 schrieb Christoph Lohmann <2...@r-36.net>:
> I don’t know why people prefer to see the big patches inline,
Ideally the patches are small :)
> so you
> have the scroll past the whole patch to the next e‐mail, when you are
So, scrolling is a problem for you? I do +
Am 11.12.2012 um 12:38 schrieb Marc Andre Tanner :
Please send patches as attached files.
>>>
>>> Since we are using now git, it is easier and logic send the patches in this
>>> way, so the code of the patch can be included and modified in replies. You
>>> only have to use git am if you wan
I use Vim, and there you can cycle forward through completion using "Tab" and
backward using "Shift+Tab", this does not work in st, but it works in xterm. I
tested against tip.
Though I guess there is some interesting stuff going on with this, since in
general it seems tab sends ^I and thus you ca
13 matches
Mail list logo
