vimprobable-users — Mailing list for Vimprobable users

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

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

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

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

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

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

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

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

Hello all,

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).

-Matt

Re: [Vimprobable-users] RC file consolidation

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

Hi all,

After reading Hans-Peter's post, I believe it may be more beneficial to
leave these as seperate files - although an ideal solution from my point
of view would be to combine the two options and allow these to be
configured in the rc file or in the specific file(s).  This could be
expanded to include the other files (bookmarks, quickmarks, URI
handlers), such that I could have an rc file that looked like:

searchengine ...
quickmark ...
bookmark ...

and the existing files as dynamically updated while running vimprobable.

Just another opinion.

Thanks,
-Matt

On Sun, Jan 15, 2012 at 04:34:36PM +0100, Hannes Schüller wrote:
> Here is a patch merging the functionality of the searchengines
> configuration file into vimprobablerc. See Hans-Peter's post
> (http://sourceforge.net/mailarchive/message.php?msg_id=28666686)
> concerning this subject. He brings up good points *against* this
> (though I tried to preserve the advantages from the list of use cases
> 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

> diff --git a/main.c b/main.c
> index f106245..0508db5 100644
> --- a/main.c
> +++ b/main.c
> @@ -1,6 +1,6 @@
>  /*
>      (c) 2009 by Leon Winter
> -    (c) 2009-2011 by Hannes Schueller
> +    (c) 2009-2012 by Hannes Schueller
>      (c) 2009-2010 by Matto Fransen
>      (c) 2010-2011 by Hans-Peter Deifel
>      (c) 2010-2011 by Thomas Adam
> @@ -2491,7 +2491,6 @@ main(int argc, char *argv[]) {
>      static gboolean ver = false;
>      static gboolean configfile_exists = FALSE;
>      static const char *cfile = NULL;
> -    char *searchengines_file;
>      static GOptionEntry opts[] = {
>              { "version", 'v', 0, G_OPTION_ARG_NONE, &ver, "print version", NULL },
>              { "embed", 'e', 0, G_OPTION_ARG_STRING, &winid, "embedded", NULL },
> @@ -2536,6 +2535,8 @@ main(int argc, char *argv[]) {
>      setup_cookies();
>  #endif
>  
> +    make_searchengines_list(searchengines, LENGTH(searchengines));
> +
>      /* Check if the specified file exists. */
>      /* And only warn the user, if they explicitly asked for a config on the
>       * command line.
> @@ -2551,7 +2552,7 @@ main(int argc, char *argv[]) {
>  
>      /* read config file */
>      /* But only report errors if we failed, and the file existed. */
> -    if (!read_rcfile(configfile) && configfile_exists) {
> +    if ((SUCCESS != read_rcfile(configfile)) && configfile_exists) {
>          a.i = Error;
>          a.s = g_strdup_printf("Error in config file '%s'", configfile);
>          echo(&a);
> @@ -2559,28 +2560,6 @@ main(int argc, char *argv[]) {
>          g_free(configfile);
>      }
>  
> -    make_searchengines_list(searchengines, LENGTH(searchengines));
> -
> -    /* read searchengines. */
> -    searchengines_file = g_strdup_printf(SEARCHENGINES_STORAGE_FILENAME);
> -    switch (read_searchengines(searchengines_file)) {
> -    case SYNTAX_ERROR:
> -        a.i = Error;
> -        a.s = g_strdup_printf("Syntax error in searchengines file '%s'", searchengines_file);
> -        echo(&a);
> -        g_free(a.s);
> -        break;
> -    case READING_FAILED:
> -        a.i = Error;
> -        a.s = g_strdup_printf("Could not read searchengines file '%s'", searchengines_file);
> -        echo(&a);
> -        g_free(a.s);
> -        break;
> -    default:
> -        break;
> -    }
> -    g_free(searchengines_file);
> -
>      /* command line argument: URL */
>      if (argc > 1) {
>          strncpy(url, argv[argc - 1], 255);
> diff --git a/utilities.c b/utilities.c
> index fa0db44..431147c 100644
> --- a/utilities.c
> +++ b/utilities.c
> @@ -1,6 +1,6 @@
>  /*
>      (c) 2009 by Leon Winter
> -    (c) 2009-2011 by Hannes Schueller
> +    (c) 2009-2012 by Hannes Schueller
>      (c) 2009-2010 by Matto Fransen
>      (c) 2010-2011 by Hans-Peter Deifel
>      (c) 2010-2011 by Thomas Adam
> @@ -24,30 +24,6 @@ static GList *dynamic_searchengines = NULL;
>  
>  void add_modkeys(char key);
>  
> -gboolean read_rcfile(const char *config)
> -{
> -	int t;
> -	char s[255];
> -	FILE *fpin;
> -	gboolean returnval = TRUE;
> -
> -	if ((fpin = fopen(config, "r")) == NULL)
> -		return FALSE;
> -	while (fgets(s, 254, fpin)) {
> -		/*
> -		 * ignore lines that begin with #, / and such 
> -		 */
> -		if (!isalpha(s[0]))
> -			continue;
> -		t = strlen(s);
> -		s[t - 1] = '\0';
> -		if (!process_line(s))
> -			returnval = FALSE;
> -	}
> -	fclose(fpin);
> -	return returnval;
> -}
> -
>  void save_command_history(char *line)
>  {
>  	char *c = line;
> @@ -709,71 +685,6 @@ static gboolean sanity_check_search_url(const char *string)
>      return !was_percent_char && percent_s_count == 1;
>  }
>  
> -enum ConfigFileError
> -read_searchengines(const char *filename)
> -{
> -    FILE *file;
> -    char buffer[BUFFERSIZE], c;
> -    int linum = 0, index;
> -    gboolean found_malformed_lines = FALSE;
> -    Searchengine *new;
> -
> -    if (access(filename, F_OK) != 0)
> -        return FILE_NOT_FOUND;
> -
> -    file = fopen(filename, "r");
> -    if (file == NULL)
> -        return READING_FAILED;
> -
> -    while (fgets(buffer, BUFFERSIZE, file)) {
> -        linum++;
> -
> -        /* skip empty lines */
> -        if (!strcmp(buffer, "\n")) continue;
> -
> -        /* skip too long lines */
> -        if (buffer[strlen(buffer)-1] != '\n') {
> -            c = getc(file);
> -            if (c != EOF) {  /* this is not the last line */
> -                while ((c=getc(file)) != EOF && c != '\n');
> -                fprintf(stderr, "searchengines: syntax error on line %d\n", linum);
> -                found_malformed_lines = TRUE;
> -                continue;
> -            }
> -        }
> -
> -        /* split line at whitespace */
> -        index = split_string_at_whitespace(buffer);
> -
> -        if (index < 0 || buffer[0] == '\0' || buffer[index] == '\0'
> -                || !sanity_check_search_url(buffer+index)) {
> -            fprintf(stderr, "searchengines: syntax error on line %d\n", linum);
> -            found_malformed_lines = TRUE;
> -            continue;
> -        }
> -
> -        new = malloc(sizeof(Searchengine));
> -        if (new == NULL) {
> -            fprintf(stderr, "Memory exhausted while loading search engines.\n");
> -            exit(EXIT_FAILURE);
> -        }
> -
> -        new->handle = g_strdup(buffer);
> -        new->uri = g_strdup(buffer+index);
> -
> -        dynamic_searchengines = g_list_prepend(dynamic_searchengines, new);
> -    }
> -
> -    if (ferror(file)) {
> -        fclose(file);
> -        return READING_FAILED;
> -    }
> -
> -    fclose(file);
> -
> -    return found_malformed_lines ? SYNTAX_ERROR : SUCCESS;
> -}
> -
>  void make_searchengines_list(Searchengine *searchengines, int length)
>  {
>      int i;
> @@ -800,3 +711,57 @@ char *find_uri_for_searchengine(const char *handle)
>  
>      return NULL;
>  }
> +
> +enum ConfigFileError
> +read_rcfile(const char *config)
> +{
> +	int t, linum = 0, index;
> +	char s[255], *buffer;
> +	FILE *fpin;
> +	gboolean found_malformed_lines = FALSE;
> +	Searchengine *new;
> +
> +   if (access(config, F_OK) != 0)
> +        return FILE_NOT_FOUND;
> +
> +    fpin = fopen(config, "r");
> +    if (fpin == NULL)
> +        return READING_FAILED;
> +
> +	while (fgets(s, 254, fpin)) {
> +		linum++;
> +		/*
> +		 * ignore lines that begin with #, / and such 
> +		 */
> +		if (!isalpha(s[0]))
> +			continue;
> +		t = strlen(s);
> +		s[t - 1] = '\0';
> +		if (strncmp(s, "searchengine", 12) == 0) {
> +			buffer = (s + 12);
> +			while (buffer[0] == ' ')
> +				buffer++;
> +			/* split line at whitespace */
> +			index = split_string_at_whitespace(buffer);
> +			if (index < 0 || buffer[0] == '\0' || buffer[index] == '\0'
> +					|| !sanity_check_search_url(buffer+index)) {
> +				fprintf(stderr, "searchengines: syntax error on line %d\n", linum);
> +				found_malformed_lines = TRUE;
> +				continue;
> +			}
> +			new = malloc(sizeof(Searchengine));
> +			if (new == NULL) {
> +				fprintf(stderr, "Memory exhausted while loading search engines.\n");
> +				exit(EXIT_FAILURE);
> +			}
> +			new->handle = g_strdup(buffer);
> +			new->uri = g_strdup(buffer+index);
> +			dynamic_searchengines = g_list_prepend(dynamic_searchengines, new);
> +		} else {
> +			if (!process_line(s))
> +				found_malformed_lines = TRUE;
> +		}
> +	}
> +	fclose(fpin);
> +    return found_malformed_lines ? SYNTAX_ERROR : SUCCESS;
> +}
> diff --git a/utilities.h b/utilities.h
> index eec1277..9f4aacc 100644
> --- a/utilities.h
> +++ b/utilities.h
> @@ -1,6 +1,6 @@
>  /*
>      (c) 2009 by Leon Winter
> -    (c) 2009-2011 by Hannes Schueller
> +    (c) 2009-2012 by Hannes Schueller
>      (c) 2009-2010 by Matto Fransen
>      (c) 2010-2011 by Hans-Peter Deifel
>      (c) 2010-2011 by Thomas Adam
> @@ -13,7 +13,7 @@
>  /* max entries in command history */
>  #define COMMANDHISTSIZE 50
>  
> -gboolean read_rcfile(const char *config);
> +enum ConfigFileError read_rcfile(const char *config);
>  void save_command_history(char *line);
>  gboolean process_save_qmark(const char *bm, WebKitWebView *webview);
>  void make_keyslist(void);
> @@ -31,6 +31,5 @@ Listelement * add_list(const char *element, Listelement *elementlist);
>  int count_list(Listelement *elementlist);
>  void free_list(Listelement *elementlist);
>  
> -enum ConfigFileError read_searchengines(const char *filename);
>  char *find_uri_for_searchengine(const char *handle);
>  void make_searchengines_list(Searchengine *searchengines, int length);
> diff --git a/vimprobable.h b/vimprobable.h
> index b0176b7..1ac9030 100644
> --- a/vimprobable.h
> +++ b/vimprobable.h
> @@ -1,6 +1,6 @@
>  /*
>      (c) 2009 by Leon Winter
> -    (c) 2009-2011 by Hannes Schueller
> +    (c) 2009-2012 by Hannes Schueller
>      (c) 2009-2010 by Matto Fransen
>      (c) 2010-2011 by Hans-Peter Deifel
>      (c) 2010-2011 by Thomas Adam
> @@ -176,9 +176,6 @@ enum ConfigFileError {
>  #define             HISTORY_STORAGE_FILENAME    "%s/vimprobable/history", config_base
>  #define             CLOSED_URL_FILENAME         "%s/vimprobable/closed", config_base
>  
> -/* searchengines */
> -#define             SEARCHENGINES_STORAGE_FILENAME "%s/vimprobable/searchengines", config_base
> -
>  /* Command size */
>  #define	            COMMANDSIZE	                1024
>  
> diff --git a/vimprobable2.1 b/vimprobable2.1
> index a780e6a..92706ac 100644
> --- a/vimprobable2.1
> +++ b/vimprobable2.1
> @@ -1,7 +1,7 @@
>  .\" Process this file with
>  .\" groff -man -Tascii vimprobable2.1
>  .\"
> -.TH VIMPROBABLE2 1 "JANUARY 2010" "Linux User Manuals"
> +.TH VIMPROBABLE2 1 "JANUARY 2012" "Linux User Manuals"
>  .SH NAME
>  Vimprobable \- A WWW browser based on webkit with keybindings inspired by Vim, the great editor.
>  
> @@ -313,22 +313,13 @@ https://secure.wikimedia.org/wikipedia/de/w/index.php?title=Special%%3ASearch&se
>  .P
>  
>  You can always overwrite them or define your own in
> -.I $HOME/.config/vimprobable/searchengines.
> -In this file, every line defines one shortcut for one URL in the following
> -format (without the angle brackets):
> -
> -.RS 4
> -<shortcut> <URL with exactly one %s>
> -.RE
> -
> -where the %s serves as a placeholder for the search term. Other percent signs
> -in the URL have to be escaped as %%\&.
> -
> +.I $HOME/.config/vimprobable/vimprobablerc.
> +See vimprobablerc (5) for details.
>  .B Default search engine
>  
>  If Vimprobable doesn't recognize an address as a valid URL or query to one of the
>  defined search engines, it will use the default search engine instead. See
> -.BR vimprobablerc (1)
> +.BR vimprobablerc (5)
>  on how to set this default.
>  
>  .SH FILES
> @@ -341,8 +332,6 @@ file is required if you want to use cookies.
>  
>  .I $HOME/.config/vimprobable/bookmarks
>  
> -.I $HOME/.config/vimprobable/searchengines
> -
>  .I $HOME/.config/vimprobable/cookies
>  
>  .I $HOME/.config/vimprobable/history
> diff --git a/vimprobablerc.5 b/vimprobablerc.5
> index 31755aa..7d85bb2 100644
> --- a/vimprobablerc.5
> +++ b/vimprobablerc.5
> @@ -1,7 +1,7 @@
>  .\" Process this file with
>  .\" groff -man -Tascii vimprobablerc.5
>  .\"
> -.TH VIMPROBABLERC 5 "December 2009" "Linux User Manuals"
> +.TH VIMPROBABLERC 5 "January 2012" "Linux User Manuals"
>  .SH NAME
>  vimprobablerc \- The configuration file for Vimprobable
>  .SH DESCRIPTION
> @@ -228,6 +228,18 @@ All settings can be changed on the fly by entering
>  :set followed by one of the commands in the SETTINGS section
>  above.
>  
> +.SH SEARCH ENGINES
> +
> +You can define new search engine shortcuts or override the pre-defined ones
> +using the following format (without the angle brackets):
> +
> +.RS 4
> +searchengine <shortcut> <URL with exactly one %s>
> +.RE
> +
> +where the %s serves as a placeholder for the search term. Other percent signs
> +in the URL have to be escaped as %%\&.
> +
>  .SH BUGS
>  There has not been any significant bug-hunting yet.
>  .SH AUTHORS




> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2

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


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

[Vimprobable-users] RC file consolidation

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

Here is a patch merging the functionality of the searchengines
configuration file into vimprobablerc. See Hans-Peter's post
(http://sourceforge.net/mailarchive/message.php?msg_id=28666686)
concerning this subject. He brings up good points *against* this
(though I tried to preserve the advantages from the list of use cases
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

Re: [Vimprobable-users] [Patch] External URI handlers

[Hans-Peter D. <Han...@in...>]

Hi all,

On 23:00 Wed 11 Jan     , Hannes Schüller wrote:
> As per the discussion on IRC and related to this:
> 
> Should we keep things like search engine definitions or these URI
> handlers in separate files or merge them all into vimprobablerc?
> Opinions, please.

I don't have a strong opinion on this, but here are the reasons why I
used a separate file for the search engines:

  - Easy to parse. I have a ton of scripts that use the bookmarks and
    search engine files for completion or input for dmenu, etc. These
    could theoretically be rewritten to parse the rc file, but that's
    certainly a little more work ;)

  - Easy to generate. Vimprobable could be able to add search engines
    from the UI, like it is the case for bookmarks. Or you could write
    scripts that synchronize your search engines with a different
    browser. I usually don't want programs to touch hand-written
    configuration files, so it's good to have a separate file for those
    things that can be generated.

  - Loadable on demand. Vimprobable could load the file every time it
    needs it. This is currently done for bookmarks, but not for search
    engines. It would have the benefit that changes to the file become
    instantly available in all running browser instances.


In conclusion, I think of search engines or bookmarks more as data than
as configuration. Thus they can and should be generated, manipulated
and read from vimprobable and external programs. I didn't really follow
the URI handler discussion, so I don't have an opinion on them yet.

These are quite technical reasons. The reason "I like to have all
configuration in one file" is certainly valid, too.


Regards,
HP

Re: [Vimprobable-users] [Patch] External URI handlers

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

Matthew Carter <je...@gm...> wrote:
> is it possible
> to have these types of matches done via regex matches?
> 
> For instance:
> 
> .*\.doc$ libreoffice %s
> .*\.pdf$ evince %s
> ^ftp: xterm -e wget %s

There have been two different patches for this back at the dawn of time
which nobody seemed to be really interested in. Look for the very first
posts in the archives of the previous mailing list. It should be
possible to extend these if you want to do it.

Hannes

Re: [Vimprobable-users] [Patch] External URI handlers

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

Hi all,

I agree with using one file for customization, however is it possible
to have these types of matches done via regex matches?

For instance:

.*\.doc$ libreoffice %s
.*\.pdf$ evince %s
^ftp: xterm -e wget %s


So that it would act with a similar functionality to the mailcap file
used with programs such as mutt (or alternatively just use the mailcap
file, as I believe that goes based on the content-type tags instead of
any advanced pattern matching) in addition to the new URI handling?

Thanks,
-Matt

On Thu, Jan 12, 2012 at 11:04:51AM +1300, Jason Ryan wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 12/01/12 11:00, Hannes Schüller wrote:
> > As per the discussion on IRC and related to this:
> > 
> > Should we keep things like search engine definitions or these URI
> > handlers in separate files or merge them all into vimprobablerc?
> > Opinions, please.
> > 
> My preference would be to only have to maintain my customizations in the
> one file (vimprobablerc)...
> 
> Cheers,
> 
> /J
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> 
> iQEcBAEBAgAGBQJPDgeDAAoJEEReUuqxvU5A9csIALqG/8dHs+iWHMzb9GP/VrBE
> wylO9aIeVTzSe135y1XYH3BD2O+O1HzXyAk6hjqA/PqPZ/In3hQZTRDzKJ1OmTF6
> AUwPLSY3Q2e3b1Ma6sGhgGBKnin4X32p6CNnHkWqMLfqXL+q15q/NKiOQ131TsGf
> coA2qqWyGsbXUu8Lpf9ZHEyZ67JLZ+Z6+o8/gpKL/DIiDIWlAjWvwEKEyNENveM4
> N4zgfgK7g/M3fhhcKvfOR9GPuQaaD4Ux3gto/eJBvCUY4nSkqV+oxC3iGXrzkNoP
> j61kTFTbD43rN9zfQ/56893ll34n1AuOABjN4Im7UppqAOGU0jMa89Zsfx1VAb8=
> =b6+z
> -----END PGP SIGNATURE-----
> 
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual 
> desktops for less than the cost of PCs and save 60% on VDI infrastructure 
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Vimprobable-users mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimprobable-users

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

Re: [Vimprobable-users] [Patch] External URI handlers

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

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

On 12/01/12 11:00, Hannes Schüller wrote:
> As per the discussion on IRC and related to this:
> 
> Should we keep things like search engine definitions or these URI
> handlers in separate files or merge them all into vimprobablerc?
> Opinions, please.
> 
My preference would be to only have to maintain my customizations in the
one file (vimprobablerc)...

Cheers,

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

iQEcBAEBAgAGBQJPDgeDAAoJEEReUuqxvU5A9csIALqG/8dHs+iWHMzb9GP/VrBE
wylO9aIeVTzSe135y1XYH3BD2O+O1HzXyAk6hjqA/PqPZ/In3hQZTRDzKJ1OmTF6
AUwPLSY3Q2e3b1Ma6sGhgGBKnin4X32p6CNnHkWqMLfqXL+q15q/NKiOQ131TsGf
coA2qqWyGsbXUu8Lpf9ZHEyZ67JLZ+Z6+o8/gpKL/DIiDIWlAjWvwEKEyNENveM4
N4zgfgK7g/M3fhhcKvfOR9GPuQaaD4Ux3gto/eJBvCUY4nSkqV+oxC3iGXrzkNoP
j61kTFTbD43rN9zfQ/56893ll34n1AuOABjN4Im7UppqAOGU0jMa89Zsfx1VAb8=
=b6+z
-----END PGP SIGNATURE-----

Re: [Vimprobable-users] [Patch] External URI handlers

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

As per the discussion on IRC and related to this:

Should we keep things like search engine definitions or these URI
handlers in separate files or merge them all into vimprobablerc?
Opinions, please.

Hannes

Re: [Vimprobable-users] [Patch] External URI handlers

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

Hi Hannes!
On Sat, Jan 07, 2012 at 05:19:21PM +0100, Hannes Schüller wrote:
> Disclaimer: I believe this one should be superseeded by the newer one.
> It does not cleanly apply to the current codebase anymore anyway.
> 
> Hannes
I thought I need the previous one because of the number in the filename. The
second patch applies well. But I got a lot of whitspace errors when I applied
the patch. Maybe you can fix them, that are no showstoppers, but I think later
patches (done with other editors) causes unneeded changes in patches causes by
removed trailing whitespace or removed tabs in front of code lines.

This was the git message causes by git apply:

/home/daniel/external_handlers2.patch:94: trailing whitespace.
            return TRUE;
/home/daniel/external_handlers2.patch:122: trailing whitespace.
new_generic_request(SoupSession *session, SoupMessage *soup_msg, gpointer unused)
/home/daniel/external_handlers2.patch:289: space before tab in indent.
        if (dynamic_uri_handlers != NULL) {
/home/daniel/external_handlers2.patch:290: space before tab in indent.
                for (l = dynamic_uri_handlers; l; l = g_list_next(l)) {
/home/daniel/external_handlers2.patch:291: space before tab in indent.
                URIHandler *s = (URIHandler *)l->data;
warning: squelched 34 whitespace errors
warning: 39 lines add whitespace errors.

Daniel

Re: [Vimprobable-users] [Patch] External URI handlers

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

Daniel Carl <dan...@gm...> wrote:
> On Sat, Jan 07, 2012 at 02:42:43PM +0100, Hannes Schüller wrote:
> > Testing appreciated, especially since I plan to include this into
> > the next release.
> 
> Can you please send to previous patch again. I'm unable to get it
> from the old mailinglist archive.

This one?

Disclaimer: I believe this one should be superseeded by the newer one.
It does not cleanly apply to the current codebase anymore anyway.

Hannes

Re: [Vimprobable-users] [Patch] External URI handlers

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

Hi Hannes!
On Sat, Jan 07, 2012 at 02:42:43PM +0100, Hannes Schüller wrote:
> Testing appreciated, especially since I plan to include this into the
> next release.
> 
> Hannes

Can you please send to previous patch again. I'm unable to get it from the old
mailinglist archive.

Daniel

Re: [Vimprobable-users] [Feature] Autohide for input box

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

Just to let everybody know I'm not developing this patch any further. I
agree with Daniel's feedback as to how this should be handled. However,
seeing that neither me nor him was really interested in this feature
above purely academic interest (and nobody else showed any interest), I
don't see the point.

Hannes

[Vimprobable-users] [Patch] External URI handlers

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

This is a followup to the ancient thread "Compile-time definition of
external URI handlers". This new patch allows the definition of
external handler applications on a protocol basis.

E.g., to handle FTP links with wget, create a file called
~/.config/vimprobable/urihandlers and enter the following line:

ftp:// xterm -e wget ftp://%s

FTP and mailto links are defined in config.h by default. Other handlers
can be defined at compile time in that file or at runtime as explained
above.

Testing appreciated, especially since I plan to include this into the
next release.

Hannes

Re: [Vimprobable-users] [Feature] Autohide for input box

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

Hi!

If the input widget is disabled and you focus a input field, vimprobable
switches to insert mode but we have no indicator for the state. For me
it's neccessary to see if vimprobable in insert mode or not. Maybe we
could add a little indicator in the black bar where the current URL is
displayed (somthing like [i] for insert mode, [p] for pass through and
otherwise [n] or so).

Daniel

Re: [Vimprobable-users] [Feature] Autohide for input box

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

Hi Hannse!
On Thu, Dec 08, 2011 at 11:00:11PM +0100, Hannes Schüller wrote:
> I don't care for this very much myself; I think the opening and closing
> of widgets is a visual irritation. So if anyone would like to see this
> included, please test, test, test - otherwise, I will not merge it!
> 
> Hannes

I'm undecided if this would be a nice feature, a single line more space for
browsing. For now it's irritating me, but I think I'll become accustomed with
this behaviour soon.

I think it would be more intuitive if the input widget will be removed until
nothing is show in input. If I use hinting and break it with <ESC> the input
is erased but still visible, until <ESC> is pressed a second time.

If I enable autohide an :set some value and than activate hinting, the imput
widget disappears when the hint appear. Without these bugs, this could be a
nice feature.

Daniel

[Vimprobable-users] [Feature] Autohide for input box

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

This is a highly experimental patch which introduces a new setting:

:set autohide=true

should make the input box disappear automatically whenever it is not in
use.

I don't care for this very much myself; I think the opening and closing
of widgets is a visual irritation. So if anyone would like to see this
included, please test, test, test - otherwise, I will not merge it!

Hannes

[Vimprobable-users] [Patch] Fall back from incomplete hinting mode

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

Bug reported on IRC:
- Press "f" to start hinting mode
- Click on a link with the mouse

Vimprobable stays in hinting mode, but obviously does not show any
hints on the newly loaded page. It therefore is unresponsive to any new
commands. The attached patch fixes this by automatically falling back
to normal mode.

Hannes

[Vimprobable-users] [REFACTOR] Cleaned code in toggle_proxy a little

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

Hi!

switches to use g_strdup to build proxy uri instead of g_malloc memcpy
phrases. Also added freeing for the proxy URI.

Daniel

Re: [Vimprobable-users] [PATCH] Remove feedback for toggled proxy.

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

On 04/12/11 at 10:08pm, Hannes Schüller wrote:
> I hope that with the latest upgrade, the issue of "feedback or not"
> will become more visible to regular users. Maybe someone will have an
> opinion then.
> 
If you are referring to the 'Proxy Activated' in the status bar everytime I load
a page, then yes - I would like to see it removed. I already know that I am
running a proxy :)

Cheers,

/J

-- 

Jason Ryan
http://jasonwryan.com/

Re: [Vimprobable-users] [PATCH] Remove feedback for toggled proxy.

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

I hope that with the latest upgrade, the issue of "feedback or not"
will become more visible to regular users. Maybe someone will have an
opinion then.

Hannes

[Vimprobable-users] Vimprobable1 0.9.24.2 & Vimprobable2 0.9.11.2 released!

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

This is mainly another bugfix release:

- Fix for ;O und ;T hinting modes (Daniel Carl)
- New hinting modes to open images (;i and ;I) (Daniel Carl)
- Automatic switch back to normal mode from insert mode now occurs when
  loading starts (Hannes Schüller)
- Fix pointer reset after interrupting command history search with ESC
  (Daniel Carl)
- Check both http_proxy and HTTP_PROXY when command is called from
  vimprobablerc (Daniel Carl)

Re: [Vimprobable-users] [PATCH] Use GList for command history

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

Merged

Re: [Vimprobable-users] [PATCH] Fix for missed HTTP_PROXY evaluation in setup_settings()

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

Merged