vimprobable-users — Mailing list for Vimprobable users

Re: [Vimprobable-users] [Patch] Totally insecure password saving (rough patch, give feedback)

[<ha...@yl...>]

Hi,

this is not something I would use at all, personally. If anyone would 
like to see this feature in mainline, please speak up!

Finally, if you want to develop this further, it would of course be 
much nicer if it was configured through some file. Either the way you 
described or simple in a new file. This touches a bit on the discussion 
of "configuration versus data" - I'd say usernames and passwords are 
data, so I'd handle it like bookmarks (i.e. in a dedicated file). But 
opinions on this may differ, too.

Hannes

Re: [Vimprobable-users] Fw: DuckDuckGo as a search option in Vimprobable

[<ha...@yl...>]

Seeing that feedback has been unanimously positive, I will include this 
option into the next release.

Hannes

[Vimprobable-users] All my recent patches in one convenient download

[Matt C. <je...@gm...>]

Hi all,

The last few patches I have made, I have made available on my site at:

http://ahungry.com/Software/Vimprobable2/

The quick summary includes:

Proper insert/normal mode detection
Option to auto-escape inputs on page load (such as duckduckgo.com
automatically adding user to input mode)
Changed default search to duckduckgo.com
Username/password saving via hinting.js file

You can find the previously sent tabbed patch (open new tabs on right,
not left) at:

http://ahungry.com/Software/Tabbed/

Attached is the full vimprobable2 patch for your patching pleasure.

Note regarding hinting.js, my first thought was this is a very
insecure way to store it, however you can always re-checkout the
hinting.js file after modifying it with your passwords, as the
compiled vimprobable2 binary will then have them saved at that point.

-Matt

[Vimprobable-users] [Patch] Totally insecure password saving (rough patch, give feedback)

[Matt C. <je...@gm...>]

Hello all,

This patch modifies the hinting.js file and will require user
customization after patching, as your username/pass combos are stored
in the hinting.js file (just remove the sample ones).

I have tested on a fair number of pages (20+) and it seems to fill in
the proper username/pass boxes on all of them.

If this seems like a good idea, I can probably rewrite the onload JS
call to be an internal call made by main.c (and possible pulled from a
set parameter, like :set pass1=someurl:someuser:somepass.

This adds almost non-existent overhead to the program in it's current
implementation and allows password/username saving based on url regex
(so you can store one user/pass set for all your accounts.google
credentials etc.).

My next idea is to implement a similar feature for htaccess passwords,
by doing some redirection, so that if you go to a site such as
test.yoursite.com, which requires htaccess it could automatically
redirect to yourUser:you...@te....

Thanks,
-Matt

Re: [Vimprobable-users] RC file consolidation

[Matt C. <je...@gm...>]

Hi Daniel,

Try the following:

map q1=:open http://example.com
map Q1=:tabopen http://example.com

Note the colon after the equal sign, as open/tabopen require it.

Regarding quickmarks, I love the feature so I'd prefer not to remove
it, although it is true the same could be accomplished via the
mapping.

On 1/24/12, Daniel Carl <dan...@gm...> wrote:
> Hi!
> On Sun, Jan 15, 2012 at 04:34:36PM +0100, Hannes Schüller wrote:
>> as far as possible). Nevertheless, so far, the consensus seemed to be to
>> merge it. So this is the last chance for major protest.
>>
>> Hannes
>
> In my opinion the merge of searchengines and the previous vimprobablerc
> is a good solution, because there are not as many searchengines that we
> have to consider the memory consumption, when parsing the new
> consolidated vimprobablerc file at startup.
>
> Maybe we can reduce the code complexity and number of files by removing
> the quickmark feature. I think we can use an modified 'map' to allow
> something like this in vimprobablerc to have the same feature in a more
> generic way:
>
> map q1=open http://foo.bar.baz/path_to_file
> map Q1=tabopen http://foo.bar.baz/path_to_file
>
> With this mapping a user can create much more quickmarks as by the
> current implementation.
>
> But for now this mapping doesn't work.
>
> Daniel
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Vimprobable-users mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimprobable-users
>

Re: [Vimprobable-users] [Patch] Slightly off-topic - Patch for suckless tools "tabbed"

[Daniel C. <dan...@gm...>]

Hi!
On Fri, Jan 20, 2012 at 03:10:34PM -0500, Matt Carter wrote:
> Hello all,
> 
> For whatever reason, I feel crippled without using vimprobable2 with
> tabbed (I also change window managers frequently so its nice to have
> consistent behavior with multiple vimprobable2's), however opening new
> tabs on the left makes me lose my already opened windows place (I like
> knowing ^1 will always take me to my first opened tab).
> 
> Attached is a patch which changes default behavior to open new tabs to
> the right of all other tabs (instead of left).
> 
> Thanks,
> -Matt

This patch is really nice and works for me.

Daniel

Re: [Vimprobable-users] RC file consolidation

[Daniel C. <dan...@gm...>]

Hi!
On Sun, Jan 15, 2012 at 04:34:36PM +0100, Hannes Schüller wrote:
> as far as possible). Nevertheless, so far, the consensus seemed to be to
> merge it. So this is the last chance for major protest.
> 
> Hannes

In my opinion the merge of searchengines and the previous vimprobablerc
is a good solution, because there are not as many searchengines that we
have to consider the memory consumption, when parsing the new
consolidated vimprobablerc file at startup.

Maybe we can reduce the code complexity and number of files by removing
the quickmark feature. I think we can use an modified 'map' to allow
something like this in vimprobablerc to have the same feature in a more
generic way:

map q1=open http://foo.bar.baz/path_to_file
map Q1=tabopen http://foo.bar.baz/path_to_file

With this mapping a user can create much more quickmarks as by the
current implementation. 

But for now this mapping doesn't work.

Daniel

Re: [Vimprobable-users] Fw: DuckDuckGo as a search option in Vimprobable

[Jorge A. H. <jor...@gm...>]

On Fri, Jan 20, 2012 at 10:46:06PM +0100, Hans-Peter Deifel wrote:
> On 20:55 Fri 20 Jan     , Hannes Schüller wrote:
> > Please see the e-mails below. I believe someone has suggested this
> > search engine before. Personally, I don't have any experience with it.
> > So I'd like to hear everyone's opinion about including it into the
> > default set of search engines (e.g. as "d"). Yes or no?
> 
> It's already my default, so yes.



> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d

> _______________________________________________
> Vimprobable-users mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimprobable-users

Same here. I recommended.

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Matthew C. <je...@gm...>]

Hello all,

Further testing shows a bug when changing modes that was causing
PASS-THROUGH mode to be set when mousing over certain links (not sure
how  - I guess my lazy coding).

I have rewritten the problematic statement and attached is the good
patch file for main.c (the old config.h patch file should still be
good).

Let me know of any bugs you may find if you do try this out.

Thanks,
-Matt

On Sat, Jan 21, 2012 at 02:20:48AM -0500, Matthew Carter wrote:
> Hello all,
> 
> My best patch set to date.
> 
> These two patches do the following:
> 
> Add toggleable option:
> 
> set escapeinput=[true|false]
> 
> With true (default) the following new behavior happens:
> 
> Any auto-focused inputs are immediately escaped on page load (done
> inside main.c so it no longer relies on a javascript call).
> 
> With false the new behavior above is ignored.
> 
> In both modes, vimprobable2 will now correctly see focused fields 
> and change to "insert mode" so you can type in the highlighted field 
> (finally no more being stuck in an insert box without being in "insert
> mode").
> 
> This also works with any unique website features which put the user into an
> input box (such as duckduckgo.com's bang syntax box to the right of main
> search bar) and will properly convert to "insert mode".
> 
> Lastly,
> 
> I set the default search engine to duckduckgo (also changed default
> command bar color to a darker theme).
> 
> Hannes, hopefully this saved you some work.  With these changes I have
> hopefully resolved some annoyances of vimprobable2 for all.
> 
> Next up I want to add password saving (possibly just unsecure/plaintext).  
> Has this been done in the past and discarded due to fattening up the code?
> 
> Also how do I get my name added to LICENSE? :)
> 
> Thanks,
> -Matthew Carter
> 
> On Sat, Jan 21, 2012 at 12:56:29PM +0600, Alexander Aksarin wrote:
> > On 20:40 Fri 20 Jan     , Hannes Schüller wrote:
> > > Matt Carter <je...@gm...> wrote:
> > > > Patch for hinting.js file, not sure if anyone else will find it useful
> > > > but it escapes auto-focused input fields (such as on google.com) which
> > > > mess up the current vimprobable2 mode detection (focused input without
> > > > being in insert mode).
> > Thank You. Auto-focus input fields is annoying.
> > 
> > > This is an interesting one. I think there are two options, out of which
> > > this is one. The other way would be to actually go to INSERT mode
> > > automatically if a form element is focused (which would mean
> > > re-introducing focus watchers in some limited way).
> > > 
> > > Everyone - which behaviour is preferable?
> > I prefer first, because it's more predictable and confortable for me.
> > 
> > ------------------------------------------------------------------------------
> > Try before you buy = See our experts in action!
> > The most comprehensive online learning library for Microsoft developers
> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> > Metro Style Apps, more. Free future releases when you subscribe now!
> > http://p.sf.net/sfu/learndevnow-dev2
> > _______________________________________________
> > Vimprobable-users mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vimprobable-users
> 
> -- 
> Matthew Carter
> je...@gm...

> diff --git a/config.h b/config.h
> index b2f8e78..0e8ef4f 100644
> --- a/config.h
> +++ b/config.h
> @@ -28,8 +28,8 @@ char sslcolor[MAX_SETTING_SIZE]         = "#000000";            /* color for sta
>  
>                                          /*  normal,                 warning,                error       */
>  static const char *urlboxfont[]         = { "monospace normal 8",   "monospace normal 8",   "monospace bold 8"};
> -static const char *urlboxcolor[]        = { NULL,                   "#ff0000",              "#ffffff" };
> -static const char *urlboxbgcolor[]      = { NULL,                   NULL,                   "#ff0000" };
> +static const char *urlboxcolor[]        = { "#ffffff",                   "#ff0000",              "#ffffff" };
> +static const char *urlboxbgcolor[]      = { "#222222",                   NULL,                   "#ff0000" };
>  
>                                          /*  normal,                 error               */
>  static const char *completionfont[]     = { "monospace normal 8",   "monospace bold 8" };
> @@ -82,13 +82,14 @@ gboolean complete_case_sensitive        = TRUE;
>  
>  /* search engines */
>  static Searchengine searchengines[] = {
> +	 { "d",			  "http://duckduckgo.com/?q=%s" },
>      { "i",          "http://ixquick.com/do/metasearch.pl?query=%s" },
>      { "s",          "https://ssl.scroogle.org/cgi-bin/nbbwssl.cgi?Gw=%s" },
>      { "w",          "https://secure.wikimedia.org/wikipedia/en/w/index.php?title=Special%%3ASearch&search=%s&go=Go" },
>      { "wd",         "https://secure.wikimedia.org/wikipedia/de/w/index.php?title=Special%%3ASearch&search=%s&go=Go" },
>  };
>  
> -static char defaultsearch[MAX_SETTING_SIZE] = "i";
> +static char defaultsearch[MAX_SETTING_SIZE] = "d";
>  
>  /* command mapping */
>  Command commands[COMMANDSIZE] = {
> @@ -185,4 +186,5 @@ static Setting browsersettings[] = {
>      { "statusbar",       NULL,               "",                            FALSE,          TRUE,            FALSE,          FALSE  },
>      { "inputbox",        NULL,               "",                            FALSE,          TRUE,            FALSE,          FALSE  },
>      { "completioncase",  NULL,               "",                            FALSE,          TRUE,            FALSE,          FALSE  },
> +    { "escapeinput",		 NULL,               "",                            FALSE,          TRUE,            FALSE,          FALSE  },
>  };

> diff --git a/main.c b/main.c
> index f106245..fe21823 100644
> --- a/main.c
> +++ b/main.c
> @@ -6,6 +6,7 @@
>      (c) 2010-2011 by Thomas Adam
>      (c) 2011 by Albert Kim
>      (c) 2011 by Daniel Carl
> +	 (c) 2012 by Matthew Carter
>      see LICENSE file
>  */
>  
> @@ -141,6 +142,8 @@ static char followTarget[8] = "";
>  char *error_msg = NULL;
>  char *config_base = NULL;
>  
> +static gboolean escape_input_on_load = TRUE;
> +
>  GList *activeDownloads;
>  
>  #include "config.h"
> @@ -214,6 +217,14 @@ webview_load_committed_cb(WebKitWebView *webview, WebKitWebFrame *frame, gpointe
>  
>  void
>  webview_load_finished_cb(WebKitWebView *webview, WebKitWebFrame *frame, gpointer user_data) {
> +	if(escape_input_on_load) {
> +    Arg a = { .i = Silent, .s = g_strdup("hints.clearFocus();") };
> +	 script(&a);
> +	 g_free(a.s);
> +	 a.i = ModeNormal;
> +	 a.s = NULL;
> +	 set(&a);
> +	}
>      if (HISTORY_MAX_ENTRIES > 0)
>          history();
>      update_state();
> @@ -638,7 +649,16 @@ notify_event_cb(GtkWidget *widget, GdkEvent *event, gpointer user_data) {
>              Arg a = { .i = ModeNormal };
>              set(&a);
>          }
> -    }
> +    } else {
> +		 gchar *value = NULL, *message = NULL;
> +		 jsapi_evaluate_script("window.getSelection().focusNode", &value, &message);
> +		 Arg a;
> +		 if(!strcmp(value, "[object HTMLFormElement]"))
> +			 a.i = ModeInsert;
> +		 g_free(value);
> +		 g_free(message);
> +		 set(&a);
> +	 }
>      return FALSE;
>  }
>  
> @@ -1921,7 +1941,9 @@ process_set_line(char *line) {
>                  gtk_widget_set_visible(GTK_WIDGET(statusbar), boolval);
>              } else if (strlen(my_pair.what) == 8 && strncmp("inputbox", my_pair.what, 8) == 0) {
>                  gtk_widget_set_visible(inputbox, boolval);
> -            }
> +            } else if (strlen(my_pair.what) == 11 && strncmp("escapeinput", my_pair.what, 11) == 0) {
> +					escape_input_on_load = boolval;
> +				}
>  
>              /* reload page? */
>              if (browsersettings[i].reload)


-- 
Matthew Carter
je...@gm...

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Matthew C. <je...@gm...>]

Hello all,

My best patch set to date.

These two patches do the following:

Add toggleable option:

set escapeinput=[true|false]

With true (default) the following new behavior happens:

Any auto-focused inputs are immediately escaped on page load (done
inside main.c so it no longer relies on a javascript call).

With false the new behavior above is ignored.

In both modes, vimprobable2 will now correctly see focused fields 
and change to "insert mode" so you can type in the highlighted field 
(finally no more being stuck in an insert box without being in "insert
mode").

This also works with any unique website features which put the user into an
input box (such as duckduckgo.com's bang syntax box to the right of main
search bar) and will properly convert to "insert mode".

Lastly,

I set the default search engine to duckduckgo (also changed default
command bar color to a darker theme).

Hannes, hopefully this saved you some work.  With these changes I have
hopefully resolved some annoyances of vimprobable2 for all.

Next up I want to add password saving (possibly just unsecure/plaintext).  
Has this been done in the past and discarded due to fattening up the code?

Also how do I get my name added to LICENSE? :)

Thanks,
-Matthew Carter

On Sat, Jan 21, 2012 at 12:56:29PM +0600, Alexander Aksarin wrote:
> On 20:40 Fri 20 Jan     , Hannes Schüller wrote:
> > Matt Carter <je...@gm...> wrote:
> > > Patch for hinting.js file, not sure if anyone else will find it useful
> > > but it escapes auto-focused input fields (such as on google.com) which
> > > mess up the current vimprobable2 mode detection (focused input without
> > > being in insert mode).
> Thank You. Auto-focus input fields is annoying.
> 
> > This is an interesting one. I think there are two options, out of which
> > this is one. The other way would be to actually go to INSERT mode
> > automatically if a form element is focused (which would mean
> > re-introducing focus watchers in some limited way).
> > 
> > Everyone - which behaviour is preferable?
> I prefer first, because it's more predictable and confortable for me.
> 
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Vimprobable-users mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimprobable-users

-- 
Matthew Carter
je...@gm...

Re: [Vimprobable-users] Fw: DuckDuckGo as a search option in Vimprobable

[Alexander A. <al....@gm...>]

On 20:55 Fri 20 Jan     , Hannes Schüller wrote:
> Please see the e-mails below. I believe someone has suggested this
> search engine before. Personally, I don't have any experience with it.
> So I'd like to hear everyone's opinion about including it into the
> default set of search engines (e.g. as "d"). Yes or no?
I use it as my default more than year. It's very good. I vote yes.

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Alexander A. <al....@gm...>]

On 20:40 Fri 20 Jan     , Hannes Schüller wrote:
> Matt Carter <je...@gm...> wrote:
> > Patch for hinting.js file, not sure if anyone else will find it useful
> > but it escapes auto-focused input fields (such as on google.com) which
> > mess up the current vimprobable2 mode detection (focused input without
> > being in insert mode).
Thank You. Auto-focus input fields is annoying.

> This is an interesting one. I think there are two options, out of which
> this is one. The other way would be to actually go to INSERT mode
> automatically if a form element is focused (which would mean
> re-introducing focus watchers in some limited way).
> 
> Everyone - which behaviour is preferable?
I prefer first, because it's more predictable and confortable for me.

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Matthew C. <je...@gm...>]

Hello all,

I believe I have a much better version of patch attached (and someone
who knows more of vimprobable2 could probably write it even better).

I removed the change to hinting.js as behavior was not consistent if 
the page took more than 1000ms to render and instead added to the
webview_load_finished_cb, where behavior seems much more consistent.

Find patch attached.

-Matt

On Fri, Jan 20, 2012 at 11:06:54PM +0100, Hannes Schüller wrote:
> Matt Carter <je...@gm...> wrote:
> > I personally hate the auto focus of input fields [...]
> >
> > Would adding focus watchers be more or less resource intensive than
> > escaping all inputs on page load?
> 
> It would give control to the website (as other browsers do it), i.e.
> focus the specified input field and enter INPUT mode. Personally, I
> agree that this is intrusive and annoying, but again, this is how the
> website intended it and how other browsers handle it.
> 
> Your patch, on the other hand, gives control to the user. Might be
> preferable since we generally *do* strive to give as much power to the
> user as possible.
> 
> Hannes



> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d

> _______________________________________________
> Vimprobable-users mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimprobable-users


-- 
Matthew Carter
je...@gm...

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Jason R. <jas...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21/01/12 11:08, Hans-Peter Deifel wrote:
> On 20:40 Fri 20 Jan     , Hannes Schüller wrote:
>> Hello Matt!
>>
>> Matt Carter <je...@gm...> wrote:
>>> Patch for hinting.js file, not sure if anyone else will find it useful
>>> but it escapes auto-focused input fields (such as on google.com) which
>>> mess up the current vimprobable2 mode detection (focused input without
>>> being in insert mode).
>>
>> This is an interesting one. I think there are two options, out of which
>> this is one. The other way would be to actually go to INSERT mode
>> automatically if a form element is focused (which would mean
>> re-introducing focus watchers in some limited way).
>>
>> Everyone - which behaviour is preferable?
> 
> I don't really know. But I think Hut is right, it should be consistent
> with the cursor.
> 

Agreed.

/J
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJPGelhAAoJEEReUuqxvU5AM+UH/0wn4t0kkBqkGlGlkj9keNvr
SSZdcJah3pQMoIJG5nIeAJmCqun72ud3N0HnxA9GOcNLlOrvEa1l5FtvA01LKk7p
zk+CIVnvkbWZE0qEbVIVlBzYvLBOavB4q8O/4PI2ws+TSaERu/oyobW8qS9W75ze
M7aru40T63AGJocylBlNL4XWoEWxXU6HZpFysW9w5H2cRdb4/GTeHTeVCMBfC3Cu
wIHsW2PDGqVc+Ae2X0btbFEk9pMY8Vu8/vKB0HnzE4JIUfXT72fE79C+7/ZQilY2
UNzgHPPk2eVmoM/05soUiabT3UMYFtlB4xeR0mSLLPcJyVlRjWAKtaz63bnbMzQ=
=tA5M
-----END PGP SIGNATURE-----

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Hans-Peter D. <hpd...@gm...>]

On 20:40 Fri 20 Jan     , Hannes Schüller wrote:
> Hello Matt!
> 
> Matt Carter <je...@gm...> wrote:
> > Patch for hinting.js file, not sure if anyone else will find it useful
> > but it escapes auto-focused input fields (such as on google.com) which
> > mess up the current vimprobable2 mode detection (focused input without
> > being in insert mode).
> 
> This is an interesting one. I think there are two options, out of which
> this is one. The other way would be to actually go to INSERT mode
> automatically if a form element is focused (which would mean
> re-introducing focus watchers in some limited way).
> 
> Everyone - which behaviour is preferable?

I don't really know. But I think Hut is right, it should be consistent
with the cursor.

Interestingly, Pentadactyl and Vimperator seem to differ on this one.
Pentadactyl doesn't focus the input field and Vimperator does.

--
HP

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Hannes S. <ha...@yl...>]

Matt Carter <je...@gm...> wrote:
> I personally hate the auto focus of input fields [...]
>
> Would adding focus watchers be more or less resource intensive than
> escaping all inputs on page load?

It would give control to the website (as other browsers do it), i.e.
focus the specified input field and enter INPUT mode. Personally, I
agree that this is intrusive and annoying, but again, this is how the
website intended it and how other browsers handle it.

Your patch, on the other hand, gives control to the user. Might be
preferable since we generally *do* strive to give as much power to the
user as possible.

Hannes

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Matt C. <je...@gm...>]

I personally hate the auto focus of input fields (even on
non-vimprobable2 browsers when using Space to scroll down page) as it
interrupts my navigation method (keyboard) unless I specifically want
to enter the input field (by using hints or gi on vimprobable2).

Would adding focus watchers be more or less resource intensive than
escaping all inputs on page load?

My patch could probably be tweaked so it doesn't do a full 1000 ms
timeout (in local testing it seems like 500 may be plenty if not too
much).

On 1/20/12, Hannes Schüller <ha...@yl...> wrote:
> Hut <hu...@la...> wrote:
>> > Matt Carter <je...@gm...> wrote:
>> > > Patch for hinting.js file, not sure if anyone else will find it
>> > > useful but it escapes auto-focused input fields (such as on
>> > > google.com) which mess up the current vimprobable2 mode detection
>> > > (focused input without being in insert mode).
>> >
>> > This is an interesting one. I think there are two options, out of
>> > which this is one. The other way would be to actually go to INSERT
>> > mode automatically if a form element is focused (which would mean
>> > re-introducing focus watchers in some limited way).
>> >
>> > Everyone - which behaviour is preferable?
>>
>> I still don't get why we need an INSERT mode at all.  I would prefer
>> that all keys are passed to the input field if and only if the cursor
>> in that field is visible/blinking.
>
> So this is a vote for option 2.
>
> Hannes
>

Re: [Vimprobable-users] Fw: DuckDuckGo as a search option in Vimprobable

[Hans-Peter D. <hpd...@gm...>]

On 20:55 Fri 20 Jan     , Hannes Schüller wrote:
> Please see the e-mails below. I believe someone has suggested this
> search engine before. Personally, I don't have any experience with it.
> So I'd like to hear everyone's opinion about including it into the
> default set of search engines (e.g. as "d"). Yes or no?

It's already my default, so yes.

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Hannes S. <ha...@yl...>]

Hut <hu...@la...> wrote:
> > Matt Carter <je...@gm...> wrote:  
> > > Patch for hinting.js file, not sure if anyone else will find it
> > > useful but it escapes auto-focused input fields (such as on
> > > google.com) which mess up the current vimprobable2 mode detection
> > > (focused input without being in insert mode).  
> > 
> > This is an interesting one. I think there are two options, out of
> > which this is one. The other way would be to actually go to INSERT
> > mode automatically if a form element is focused (which would mean
> > re-introducing focus watchers in some limited way).
> > 
> > Everyone - which behaviour is preferable?
> 
> I still don't get why we need an INSERT mode at all.  I would prefer
> that all keys are passed to the input field if and only if the cursor
> in that field is visible/blinking.

So this is a vote for option 2.

Hannes

Re: [Vimprobable-users] [patch] to escape auto focused inputs on page load

[Hut <hu...@la...>]

> Hello Matt!
> 
> Matt Carter <je...@gm...> wrote:
> > Patch for hinting.js file, not sure if anyone else will find it useful
> > but it escapes auto-focused input fields (such as on google.com) which
> > mess up the current vimprobable2 mode detection (focused input without
> > being in insert mode).
> 
> This is an interesting one. I think there are two options, out of which
> this is one. The other way would be to actually go to INSERT mode
> automatically if a form element is focused (which would mean
> re-introducing focus watchers in some limited way).
> 
> Everyone - which behaviour is preferable?
> 
> Hannes
> 

I still don't get why we need an INSERT mode at all.  I would prefer
that all keys are passed to the input field if and only if the cursor in
that field is visible/blinking.  Now you can be in the INSERT mode
without a blinking cursor and you can have a blinking cursor without
being in INSERT mode.  This makes no sense to me, I would've already
changed it if I knew how.

Regards, Hut

Re: [Vimprobable-users] [Patch] Slightly off-topic - Patch for suckless tools "tabbed"

[Matt C. <je...@gm...>]

Sorry all, original patch may not work if you use on tabbed as I
forgot to include another minor change in the diff - new function
named "byebye" which you can add a bind for in your config.h file that
will automatically exit tabbed and all embeded windows (I use ^c).

-Matt

On 1/20/12, Jason Ryan <jas...@gm...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 21/01/12 09:10, Matt Carter wrote:
>> Hello all,
>>
>> For whatever reason, I feel crippled without using vimprobable2 with
>> tabbed (I also change window managers frequently so its nice to have
>> consistent behavior with multiple vimprobable2's), however opening new
>> tabs on the left makes me lose my already opened windows place (I like
>> knowing ^1 will always take me to my first opened tab).
>>
>> Attached is a patch which changes default behavior to open new tabs to
>> the right of all other tabs (instead of left).
>>
>> Thanks,
>> -Matt
>>
> Thanks Matt: I have struggled with this as well. The patch is very much
> appreciated!
>
> You should also post it to the suckless ML.
>
> Cheers,
>
> /J
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBAgAGBQJPGcz/AAoJEEReUuqxvU5AMmoH/0a9nr2TP0zXTdFnLTtK055d
> 6ewcg1s6QyyyKanpa9L57ivoidb0oYA/BDAGfAWgkMVeoSYlBGAC31IIK8pUtIxv
> DK4+sEBbU72cFRmZGGYow/bJPa8+PPpGdzwiiGnHOe20hV4dX9rYkrki7SJOW45N
> hHO3vgbq3RYJ8MBptlGvzhNT8p9okHrocP1Aydu4EJFUUfjQR4nmkSrFcG6J7m5R
> ye0qKF5ojb0UKF5rOJyfU9a+3oqE143a/v7EodtdGHkLa7iMjcp1KbscGG+cQz3d
> hVgiIlgs3nGDG+1mq0P8EVm5hwXYQwRuIWM4a1goq3crAWND34DptOSw6NeyLlA=
> =1Bv7
> -----END PGP SIGNATURE-----
>

Re: [Vimprobable-users] [Patch] Slightly off-topic - Patch for suckless tools "tabbed"

[Jason R. <jas...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21/01/12 09:10, Matt Carter wrote:
> Hello all,
> 
> For whatever reason, I feel crippled without using vimprobable2 with
> tabbed (I also change window managers frequently so its nice to have
> consistent behavior with multiple vimprobable2's), however opening new
> tabs on the left makes me lose my already opened windows place (I like
> knowing ^1 will always take me to my first opened tab).
> 
> Attached is a patch which changes default behavior to open new tabs to
> the right of all other tabs (instead of left).
> 
> Thanks,
> -Matt
> 
Thanks Matt: I have struggled with this as well. The patch is very much
appreciated!

You should also post it to the suckless ML.

Cheers,

/J
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJPGcz/AAoJEEReUuqxvU5AMmoH/0a9nr2TP0zXTdFnLTtK055d
6ewcg1s6QyyyKanpa9L57ivoidb0oYA/BDAGfAWgkMVeoSYlBGAC31IIK8pUtIxv
DK4+sEBbU72cFRmZGGYow/bJPa8+PPpGdzwiiGnHOe20hV4dX9rYkrki7SJOW45N
hHO3vgbq3RYJ8MBptlGvzhNT8p9okHrocP1Aydu4EJFUUfjQR4nmkSrFcG6J7m5R
ye0qKF5ojb0UKF5rOJyfU9a+3oqE143a/v7EodtdGHkLa7iMjcp1KbscGG+cQz3d
hVgiIlgs3nGDG+1mq0P8EVm5hwXYQwRuIWM4a1goq3crAWND34DptOSw6NeyLlA=
=1Bv7
-----END PGP SIGNATURE-----

Re: [Vimprobable-users] Fw: DuckDuckGo as a search option in Vimprobable

[Jason R. <jas...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21/01/12 08:55, Hannes Schüller wrote:
> Please see the e-mails below. I believe someone has suggested this
> search engine before. Personally, I don't have any experience with it.
> So I'd like to hear everyone's opinion about including it into the
> default set of search engines (e.g. as "d"). Yes or no?
> 
> Hannes
> 
> Start of forwarded message:
> 
> Date: Sat, 21 Jan 2012 01:16:16 +0530
> From: Prakash Swaminathan <pr...@du...>
> To: Hannes Schüller <ha...@yl...>
> Subject: Re: DuckDuckGo as a search option in Vimprobable

I set it as my default anyway; so I would welcome this...

/J


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJPGcyAAAoJEEReUuqxvU5AeZYH/iBiBJyTEDvJZp89HnuYTY6q
eX8M0eUqqgKhre0f9ARjPziWIxCsQjYX0aKM6GzGQGVRW4krQmVHTFg7WmegJCXf
qTdLb56hE8zQeT5Pqz5rGk+vvlIzVnzLyvroaE8WowxJ0hywUFK2A+UUT7XQvX33
QEs0KX/cNmWbEH2JAQEMhxxDQ7IJQWZpksWhdfKOX103tibTkP/mrY0JpMptdi9o
D+uYDiF2/7Zot8Medn0G0/0hN8dgJAlwRUgTOIjJavNbNjmluAeelgMRU5+jo9TH
Mk+rYIjttRdo6QAdqO8UdqxHRZES64fM+2j3/ooDA1e1xqPadkvyiIGbCwFPCd0=
=KOZA
-----END PGP SIGNATURE-----

[Vimprobable-users] [Patch] Slightly off-topic - Patch for suckless tools "tabbed"

[Matt C. <je...@gm...>]

Hello all,

For whatever reason, I feel crippled without using vimprobable2 with
tabbed (I also change window managers frequently so its nice to have
consistent behavior with multiple vimprobable2's), however opening new
tabs on the left makes me lose my already opened windows place (I like
knowing ^1 will always take me to my first opened tab).

Attached is a patch which changes default behavior to open new tabs to
the right of all other tabs (instead of left).

Thanks,
-Matt

Re: [Vimprobable-users] Fw: DuckDuckGo as a search option in Vimprobable

[Matt C. <je...@gm...>]

I've heard of it before, ran a few queries, results seem pretty good.

I'd vote yes.

Thanks,
-Matt

On 1/20/12, Hannes Schüller <ha...@yl...> wrote:
> Please see the e-mails below. I believe someone has suggested this
> search engine before. Personally, I don't have any experience with it.
> So I'd like to hear everyone's opinion about including it into the
> default set of search engines (e.g. as "d"). Yes or no?
>
> Hannes
>
> Start of forwarded message:
>
> Date: Sat, 21 Jan 2012 01:16:16 +0530
> From: Prakash Swaminathan <pr...@du...>
> To: Hannes Schüller <ha...@yl...>
> Subject: Re: DuckDuckGo as a search option in Vimprobable
>
>
> Hello Hannes,
>
> Please feel free to forward this email to your users and let us know
> their views.  We would be happy to answer any questions your users have.
>
> I have summarized the links:
>
> PRIVACY:
> -  http://duckduckgo.com/privacy.html
> -  http://donttrack.us/
> -  http://dontbubble.us/
>
> GOODIES:
> -  http://duckduckgo.com/goodies.html
>
> ABOUT:
> -  http://duckduckgo.com/about.html
>
> Kind regards,
> Prakash
>
> 2012/1/21 Hannes Schüller <ha...@yl...>
>
>> Hello Prakash!
>>
>> Prakash Swaminathan <pr...@du...> wrote:
>> > DuckDuckGo is a general search engine with instant answers, less
>> > spam/clutter and real privacy (http://duckduckgo.com/privacy.html).
>> >
>> > We are the default search engine in Linux Mint and available in
>> > Opera and other browsers, and can offer your users a compelling
>> > alternative search option.
>> >
>> > It looks like we are a good solution to the search question in your
>> > FAQ. Who do you recommend that we contact to introduce DuckDuckGo?
>>
>> Is it ok if I forward your mail to our users mailing list to ask
>> everyone for their views?
>>
>> Hannes
>>
>>
>
>
> --
> Prakash Swaminathan  http://duckduckgo.com/
> 503-928-7721  Skype: PrakashSwami
>
> DuckDuckGo in TIME's 50 best websites -- http://ti.me/qzTtlG
>