ART_PREFIX("ddg", "https://duckduckgo.com/?q=%s&t=elinks";),
> INIT_OPT_SMART_PREFIX("dmoz",
> "http://search.dmoz.org/cgi-bin/search?search=%s";),
> INIT_OPT_SMART_PREFIX("foldoc",
> "http://wombat.doc.ic.ac.uk/foldoc/foldoc.cgi?%s";),
> INIT_OPT_SMART_PREFIX("g",
> "http://www.google.com/search?q=%s&btnG=Google+Search";),
> --
> 1.7.1
>
--
Prakash Swaminathan, https://duckduckgo.com/
___
elinks-dev mailing list
elinks-dev@linuxfromscratch.org
http://linuxfromscratch.org/mailman/listinfo/elinks-dev
ing rule, or if
>> the user sets config.saving_style = 1 or 2. I don't know whether
>> this risk is so bad you'd prefer using https unconditionally.
>
> Prakash, is it fine to use the non-SSL URLs (starting with http://)
> for elinks? They appear working to me...
>
> Kamil
--
Prakash Swaminathan, https://duckduckgo.com/
___
elinks-dev mailing list
elinks-dev@linuxfromscratch.org
http://linuxfromscratch.org/mailman/listinfo/elinks-dev
suggested above, and uses
>> non-SSL URIs to avoid problems on ELinks' builds without the SSL/TLS support.
>
> Thank you, I have applied the patch.
>
> Best,
>
> Petr "Pasky"
