unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jason Rumney <jasonrumney@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: What are Emacs best uses?
Date: Tue, 20 Aug 2013 18:58:36 -0700 (PDT)	[thread overview]
Message-ID: <fea5f7f8-6aaa-44db-b0f2-d06701f7aff4@googlegroups.com> (raw)
In-Reply-To: <mailman.342.1376922920.10748.help-gnu-emacs@gnu.org>

On Monday, 19 August 2013 22:35:13 UTC+8, Luca Ferrari  wrote:
> On Mon, Aug 19, 2013 at 4:04 PM, Sebastien Vauban wrote:
> 
> > --8<---------------cut here---------------start------------->8---
> 
> >       ;; use proxy
> >       (setq url-proxy-services
> >             `(("http"     . ,(getenv "http_proxy"))
> >               ("ftp"      . ,(getenv "http_proxy"))
> >               ("no_proxy" . "^.*example.com"))) 
> >               ;; disable proxy for some hosts
> > --8<---------------cut here---------------end--------------->8---
>
> Despite two extra parens in the end, no, it does not help. I tried to 
> update the package list but got "Failed to download 'gnu' archive". I
> then tried to get an URL with w3 but I got "http/80 Name or service
> unknown".

Emacs expects just hostname and port in `url-proxy-services'. Generally the http_proxy environment variable will be prefixed with "http://", as that is what some other programs expect.

Either change the above to explicitly use your proxy server details

    (setq url-proxy-services
          (("http" . "proxy-host:port")
;; etc...
          ))

or if you really want to use the environment variables, add some code to strip off the leading "http://" and any trailing "/".


  parent reply	other threads:[~2013-08-21  1:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 17:05 What are Emacs best uses? Jorge
2013-08-12 18:52 ` Peter Dyballa
2013-08-13  4:04 ` Charles Philip Chan
2013-08-17 14:11   ` Jorge
2013-08-17 20:20     ` Charles Philip Chan
2013-08-18 10:31       ` Jorge
2013-08-19 11:09         ` Phillip Lord
2013-08-19 20:21         ` Charles Philip Chan
2013-08-19  2:46     ` Eric Abrahamsen
2013-08-13 11:30 ` Phillip Lord
2013-08-13 14:43   ` Drew Adams
2013-08-13 16:05 ` W. Greenhouse
2013-08-14  8:21   ` Thomas Shannon
2013-08-15 14:41     ` W. Greenhouse
2013-08-16  9:49       ` Thomas Shannon
2013-08-14 14:51 ` Ken Goldman
2013-08-14 19:04 ` Nikolay Kudryavtsev
2013-08-19 13:52 ` Luca Ferrari
     [not found] ` <mailman.340.1376920365.10748.help-gnu-emacs@gnu.org>
2013-08-19 14:04   ` Sebastien Vauban
2013-08-19 14:35     ` Luca Ferrari
     [not found]     ` <mailman.342.1376922920.10748.help-gnu-emacs@gnu.org>
2013-08-20  8:25       ` Sebastien Vauban
2013-08-20 10:56         ` Luca Ferrari
     [not found]         ` <mailman.401.1376996210.10748.help-gnu-emacs@gnu.org>
2013-08-20 12:44           ` Sebastien Vauban
2013-08-21  1:58       ` Jason Rumney [this message]
2013-08-21  6:25         ` Luca Ferrari
     [not found] <mailman.3062.1376327401.12400.help-gnu-emacs@gnu.org>
2013-08-12 18:08 ` Pascal J. Bourguignon
2013-08-12 18:45   ` Andreas Röhler
2013-08-13 13:34   ` Joe Corneli
2013-08-13  1:52 ` Emanuel Berg
2013-08-13  3:29 ` Rustom Mody
2013-08-13 11:52 ` Dan Espen
2013-08-13 12:27   ` Filipp Gunbin
     [not found]   ` <mailman.3116.1376396894.12400.help-gnu-emacs@gnu.org>
2013-08-13 12:33     ` Dan Espen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fea5f7f8-6aaa-44db-b0f2-d06701f7aff4@googlegroups.com \
    --to=jasonrumney@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).