Re: [Vimprobable-users] [Patch] External URI handlers
Vimprobable is a lean web browser optimised for full keyboard control
Brought to you by:
hanness
From: Hans-Peter D. <Han...@in...> - 2012-01-12 11:15:01
|
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 |