vimprobable-users Mailing List for Vimprobable (Page 9)
Vimprobable is a lean web browser optimised for full keyboard control
Brought to you by:
hanness
Menu
▾
▴
vimprobable-users — Mailing list for Vimprobable users
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(77) |
Sep
(44) |
Oct
(43) |
Nov
(38) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(40) |
Feb
(18) |
Mar
(12) |
Apr
(25) |
May
(12) |
Jun
(13) |
Jul
(17) |
Aug
(3) |
Sep
(20) |
Oct
(42) |
Nov
(9) |
Dec
(2) |
| 2013 |
Jan
(9) |
Feb
(29) |
Mar
(9) |
Apr
(7) |
May
(38) |
Jun
|
Jul
(7) |
Aug
|
Sep
(5) |
Oct
(10) |
Nov
(11) |
Dec
(1) |
| 2014 |
Jan
(16) |
Feb
(18) |
Mar
(11) |
Apr
(5) |
May
(13) |
Jun
(5) |
Jul
(5) |
Aug
(7) |
Sep
(30) |
Oct
|
Nov
|
Dec
(26) |
| 2015 |
Jan
(5) |
Feb
(19) |
Mar
(8) |
Apr
(15) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(16) |
Dec
(10) |
| 2016 |
Jan
|
Feb
(1) |
Mar
(14) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Thorsten K. <tho...@gm...> - 2014-02-10 20:13:40
|
On Mon, Feb 10, 2014 at 08:36:50PM +0100, Serge E. Hallyn wrote: > Quoting Thorsten Köhne (tho...@gm...): > > On Mon, Feb 10, 2014 at 04:19:43PM +0100, Serge E. Hallyn wrote: > > > Quoting Hannes Schüller (ha...@yl...): > > > > On Sat, 8 Feb 2014 18:10:23 +0100, "Serge E. Hallyn" <se...@ha...> > > > > wrote: > > > > > Most of the time I'm just following ixquick links, which start in a > > > > > new window anyway, with 'f', which is why I occasionally get annoyed > > > > > but not enough to look into it yet :) > > > > > > > > This is really strange. 'F' works fine for me on Ixquick and I can't > > > > reproduce the behaviour of 'f' opening links in a new window either - > > > > > > Sorry, I didn't mean to imply that 'f' opening results in a new window > > > is a bug. I have that as a setting :) I was just saying that because > > > I have that by default the 'F' not working hasn't really bothered me > > > enough to report it. > > > > > > > Just tried your build. Still got the same problem, even with vimb > > (vimprobable-fork). > > I'm getting lost - if you mean F still doesn't open a new window, > then yes, that was the point of my original email. 'F' is not > workign for me, right-clicking and selecting 'Open in a new window' > does. > > -serge Yep, that's exactly what I mean. f opens the link in the existing window, F still doesn't do anything (visible...) |
|
From: Serge E. H. <se...@ha...> - 2014-02-10 19:36:58
|
Quoting Thorsten Köhne (tho...@gm...): > On Mon, Feb 10, 2014 at 04:19:43PM +0100, Serge E. Hallyn wrote: > > Quoting Hannes Schüller (ha...@yl...): > > > On Sat, 8 Feb 2014 18:10:23 +0100, "Serge E. Hallyn" <se...@ha...> > > > wrote: > > > > Most of the time I'm just following ixquick links, which start in a > > > > new window anyway, with 'f', which is why I occasionally get annoyed > > > > but not enough to look into it yet :) > > > > > > This is really strange. 'F' works fine for me on Ixquick and I can't > > > reproduce the behaviour of 'f' opening links in a new window either - > > > > Sorry, I didn't mean to imply that 'f' opening results in a new window > > is a bug. I have that as a setting :) I was just saying that because > > I have that by default the 'F' not working hasn't really bothered me > > enough to report it. > > > > Just tried your build. Still got the same problem, even with vimb > (vimprobable-fork). I'm getting lost - if you mean F still doesn't open a new window, then yes, that was the point of my original email. 'F' is not workign for me, right-clicking and selecting 'Open in a new window' does. -serge |
|
From: Thorsten K. <tho...@gm...> - 2014-02-10 19:29:42
|
On Mon, Feb 10, 2014 at 04:19:43PM +0100, Serge E. Hallyn wrote: > Quoting Hannes Schüller (ha...@yl...): > > On Sat, 8 Feb 2014 18:10:23 +0100, "Serge E. Hallyn" <se...@ha...> > > wrote: > > > Most of the time I'm just following ixquick links, which start in a > > > new window anyway, with 'f', which is why I occasionally get annoyed > > > but not enough to look into it yet :) > > > > This is really strange. 'F' works fine for me on Ixquick and I can't > > reproduce the behaviour of 'f' opening links in a new window either - > > Sorry, I didn't mean to imply that 'f' opening results in a new window > is a bug. I have that as a setting :) I was just saying that because > I have that by default the 'F' not working hasn't really bothered me > enough to report it. > Just tried your build. Still got the same problem, even with vimb (vimprobable-fork). |
|
From: Serge E. H. <se...@ha...> - 2014-02-10 15:19:51
|
Quoting Hannes Schüller (ha...@yl...): > On Sat, 8 Feb 2014 18:10:23 +0100, "Serge E. Hallyn" <se...@ha...> > wrote: > > Most of the time I'm just following ixquick links, which start in a > > new window anyway, with 'f', which is why I occasionally get annoyed > > but not enough to look into it yet :) > > This is really strange. 'F' works fine for me on Ixquick and I can't > reproduce the behaviour of 'f' opening links in a new window either - Sorry, I didn't mean to imply that 'f' opening results in a new window is a bug. I have that as a setting :) I was just saying that because I have that by default the 'F' not working hasn't really bothered me enough to report it. > with or without Javascript. Thorsten, can you confirm Serge's issues > with 'f' as well? > > Hannes > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > Vimprobable-users mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimprobable-users |
|
From: Thorsten K. <tho...@gm...> - 2014-02-08 17:45:56
|
On Sat, Feb 08, 2014 at 06:39:36PM +0100, Hannes Schüller wrote: > On Sat, 8 Feb 2014 18:10:23 +0100, "Serge E. Hallyn" <se...@ha...> > wrote: > > Most of the time I'm just following ixquick links, which start in a > > new window anyway, with 'f', which is why I occasionally get annoyed > > but not enough to look into it yet :) > > This is really strange. 'F' works fine for me on Ixquick and I can't > reproduce the behaviour of 'f' opening links in a new window either - > with or without Javascript. Thorsten, can you confirm Serge's issues > with 'f' as well? Sorry, I can't. 'f' opens the link in the existing window... > > Hannes > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > Vimprobable-users mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimprobable-users |
|
From: Hannes S. <ha...@yl...> - 2014-02-08 17:39:30
|
On Sat, 8 Feb 2014 18:10:23 +0100, "Serge E. Hallyn" <se...@ha...> wrote: > Most of the time I'm just following ixquick links, which start in a > new window anyway, with 'f', which is why I occasionally get annoyed > but not enough to look into it yet :) This is really strange. 'F' works fine for me on Ixquick and I can't reproduce the behaviour of 'f' opening links in a new window either - with or without Javascript. Thorsten, can you confirm Serge's issues with 'f' as well? Hannes |
|
From: Serge E. H. <se...@ha...> - 2014-02-08 17:29:10
|
Quoting Hannes Schüller (ha...@yl...): > Hi Thorsten! > > On Fri, 7 Feb 2014 22:35:13 +0100, Thorsten Köhne > <tho...@gm...> wrote: > > I hope that's the right place for my question... > > It certainly is! > > > I'm using Vimprobable2 (git) on Debian Testing (ratpoison wm). I've > > been using it on Arch Linux before without any problems. But since I > > migrated to Debian, Vimprobable won't follow links in an new Tab > > (:tabopen still working fine). > > So what you're saying is F or , don't work for you? What happens when > you activate them? Are the links hinted at all? Can you activate them > by entering the appropriate number or string? What happens after trying > to fire the link? Any output on the terminal? Come to think of it, same thing for me. 1. F does make the hints show up, then hitting 2 (for instance) just does nothing 2. right-clicking and choosing 'open in new window' does work. 3. nothing shows up in terminal if I started vimprobable there. (Source for mine is at https://launchpad.net/~serge-hallyn/+archive/vimprobable/+sourcepub/3761573/+listing-archive-extra ) Most of the time I'm just following ixquick links, which start in a new window anyway, with 'f', which is why I occasionally get annoyed but not enough to look into it yet :) thanks, -serge |
|
From: Thorsten K. <tho...@gm...> - 2014-02-08 17:17:24
|
On Sat, Feb 08, 2014 at 01:00:37PM +0100, Hannes Schüller wrote: > Hi Thorsten! > Hi Hannes! > On Fri, 7 Feb 2014 22:35:13 +0100, Thorsten Köhne > <tho...@gm...> wrote: > > I hope that's the right place for my question... > > It certainly is! > > > I'm using Vimprobable2 (git) on Debian Testing (ratpoison wm). I've > > been using it on Arch Linux before without any problems. But since I > > migrated to Debian, Vimprobable won't follow links in an new Tab > > (:tabopen still working fine). > > So what you're saying is F or , don't work for you? What happens when > you activate them? Are the links hinted at all? Can you activate them > by entering the appropriate number or string? What happens after trying > to fire the link? Any output on the terminal? > Well, after pressing F all links are highlighted and until hitting Return everything runs as expected. But after that, nothing (visible, at least for me) happens. And no output on the terminal. Ahh, I guess I forgot one certainly important information: Opening a link in a new tab by mouse is working.... > Hannes > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > Vimprobable-users mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimprobable-users |
|
From: Hannes S. <ha...@yl...> - 2014-02-08 12:31:08
|
Hi Thorsten! On Fri, 7 Feb 2014 22:35:13 +0100, Thorsten Köhne <tho...@gm...> wrote: > I hope that's the right place for my question... It certainly is! > I'm using Vimprobable2 (git) on Debian Testing (ratpoison wm). I've > been using it on Arch Linux before without any problems. But since I > migrated to Debian, Vimprobable won't follow links in an new Tab > (:tabopen still working fine). So what you're saying is F or , don't work for you? What happens when you activate them? Are the links hinted at all? Can you activate them by entering the appropriate number or string? What happens after trying to fire the link? Any output on the terminal? Hannes |
|
From: Thorsten K. <tho...@gm...> - 2014-02-07 21:35:25
|
Hello, I hope that's the right place for my question... I'm using Vimprobable2 (git) on Debian Testing (ratpoison wm). I've been using it on Arch Linux before without any problems. But since I migrated to Debian, Vimprobable won't follow links in an new Tab (:tabopen still working fine). BTW, I didn't change the config, all dependencies (libsoup, libwebkit, libgtk) are installed. Any help (hint) will be appreciated, since I like using that browser very much. Thanks in advance! |
|
From: Hannes S. <ha...@yl...> - 2014-01-19 19:10:44
|
This is a bugfix release. While fixing the "map d" issue, 1.4.1 introduced an even more subtle defect regarding the mapping of key combinations which were not in the default configuration. This issue had been reported by Marcos on the mailing list and by jeaye on IRC. Both confirmed the bugfix, so here it is - enjoy the new version! Hannes |
|
From: Hannes S. <ha...@yl...> - 2014-01-19 07:31:44
|
Marcos Cruz <vim...@pr...> wrote: > En/Je/On 2014-01-12 12:05, Hannes Schüller escribió / skribis / > wrote : > > can you please test the attached patch? > > It seems the patch fix the problem: Now "Ctrl-Q" and "\" work! > > I see what the patch does, but I don't understand why only certain > dead-key combinations failed (e.g. "Ctrl-Q" failed t but "Ctrl-X' > worked). The problem was that all redefinitions of existing keybindings worked, but no new ones could be defined. I'll try to push out a bugfix release soon :) Hannes |
|
From: Marcos C. <vim...@pr...> - 2014-01-18 19:34:39
|
En/Je/On 2014-01-12 12:05, Hannes Schüller escribió / skribis / wrote : > can you please test the attached patch? I've been busy, sorry. It seems the patch fix the problem: Now "Ctrl-Q" and "\" work! Finally I've installed 1.4.1 (I was using 1.4.0 because of this problem). I'll try all keymaps. I see what the patch does, but I don't understand why only certain dead-key combinations failed (e.g. "Ctrl-Q" failed t but "Ctrl-X' worked). Thank you. -- Marcos Cruz http://programandala.net |
|
From: Hannes S. <ha...@yl...> - 2014-01-12 11:05:42
|
Hi, can you please test the attached patch? Hannes |
|
From: Marcos C. <vim...@pr...> - 2014-01-03 22:10:12
|
En/Je/On 2014-01-03 22:47, Hannes Schüller escribió / skribis / wrote : > On Fri, 3 Jan 2014 22:16:32 +0100, Marcos Cruz wrote: > > including the mappings of single keys that implicity > > _require_ a modifier > > I'm not sure I understand what you mean. Do you have any examples? I mean a single keypress, not combined with <C-> or <M1->: map \=source map *=pgzi map _=pgzo but which actually requires a modifier, a dead key, Alt or AltGr or even Shift, because of the keyboard layout. For example, I think the backslash character needs a single keypress with an English QWERTY layout, but it needs AltGr with my Spanish Dvorak layout. Those mappings don't work, or at least those in my config file. The only mappings not affected are single keys that need no modifier. All this looks an issue of my system, but it happens only with Vimprobable2 1.4.1 :) I'll do some tests to find out the error conditions. -- Marcos Cruz http://programandala.net |
|
From: Hannes S. <ha...@yl...> - 2014-01-03 21:47:28
|
On Fri, 3 Jan 2014 22:16:32 +0100, Marcos Cruz <vim...@pr...> wrote: > including the mappings of single keys that implicity > _require_ a modifier I'm not sure I understand what you mean. Do you have any examples? Hannes |
|
From: Marcos C. <vim...@pr...> - 2014-01-03 21:43:25
|
En/Je/On 2014-01-02 13:46, Hannes Schüller escribió / skribis / wrote : > map <C-x>=quit > in vimprobablerc and it's working. I don't understand. <C-x> works here too, and also <C-u>. But many others don't, including the mappings of single keys that implicity _require_ a modifier. It makes no difference in vimprobablerc or the command line. When I switch back to 1.4.0, all mappings work. I'll investigate further. I'll try to find out a pattern or a clue. -- Marcos Cruz http://programandala.net |
|
From: Hannes S. <ha...@yl...> - 2014-01-02 12:47:12
|
On Thu, 2 Jan 2014 13:02:50 +0100, Marcos Cruz <vim...@pr...> wrote: > I just realized my Ctrl- and M1- mappings don't work with 1.4.1. I put map <C-x>=quit in vimprobablerc and it's working. The crappy layout of the examples in the man page need to be fixed, of course, but I can't reproduce this behaviour you're describing. Hannes |
|
From: Marcos C. <vim...@pr...> - 2014-01-02 12:37:34
|
En/Je/On 2014-01-02 13:02, Marcos Cruz escribió / skribis / wrote : > available formats (<C-x>, Ctrl-X...), Oops, there's only one format: map <C-q> quit I supposed there was a new alternative format after taking a look at the man page, because its layout is unclear in this example: Examples: <C-h> : Ctrl-h <C-k> : Ctrl-k z<M1-i>: z followed by Alt-i I suggest this: Examples: <C-h> means Ctrl-h <C-k> means Ctrl-k z<M1-i> means z followed by Alt-i Anyway I use the good (and only) format it in my config file and in the command line, and it does not work with 1.4.1. -- Marcos Cruz http://programandala.net |
|
From: Marcos C. <vim...@pr...> - 2014-01-02 12:29:42
|
I just realized my Ctrl- and M1- mappings don't work with 1.4.1. I tried defining them in the command line too, with the different available formats (<C-x>, Ctrl-X...), but they still don't work. Compililng 1.4.1 with the bundled config.h and keymap.h, or with my custom versions from 1.4.0 makes no difference. I returned to 1.4.0 and all mappings work. It doesn't seem a problem of my mine. Can someone confirm? -- Marcos Cruz http://programandala.net |
|
From: Marcos C. <vim...@pr...> - 2014-01-02 11:36:28
|
En/Je/On 2014-01-01 16:17, Hannes Schüller escribió / skribis / wrote : > See vimprobablerc.5 ;) Oops, I always forget there are two man pages. "January 0b11111011110", all right! |
|
From: Hannes S. <ha...@yl...> - 2014-01-01 15:17:35
|
On Wed, 1 Jan 2014 15:41:37 +0100, Marcos Cruz <vim...@pr...> wrote: > > - Amending the missing man page documentation for the new settings > > introduced in 1.4.0 > > The new man page still reads "January 2013" instead of "January > 0x7DE"! ;) See vimprobablerc.5 ;) Hannes |
|
From: Marcos C. <vim...@pr...> - 2014-01-01 15:08:31
|
Thank you! I compiled and installed it without problem (on Raspbian). > - Amending the missing man page documentation for the new settings > introduced in 1.4.0 The new man page still reads "January 2013" instead of "January 0x7DE"! ;) -- Marcos Cruz http://programandala.net |
|
From: Hannes S. <ha...@yl...> - 2014-01-01 11:32:58
|
This is a bugfix release which will enable us to appear recent for the rest of this year :) It contains two fixes: - Bugfix for "map d" (patch by desyncr) - Amending the missing man page documentation for the new settings introduced in 1.4.0 Happy new year everyone! Hannes |
|
From: Hannes S. <ha...@yl...> - 2014-01-01 11:16:48
|
This patch is now merged. Thanks Marcos for reporting and DC for fixing it! Hannes |
2 messages has been excluded from this view by a project administrator.
