unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 17959@debbugs.gnu.org
Subject: bug#17959: support accessing FTP services via HTTP proxies
Date: Mon, 09 Feb 2015 17:04:26 +0000	[thread overview]
Message-ID: <87iofbdnj9.fsf@violet.siamics.net> (raw)
In-Reply-To: <87fvbfy8xv.fsf@violet.siamics.net> (Ivan Shmakov's message of "Mon, 12 Jan 2015 21:40:12 +0000")

>>>>> Ivan Shmakov <ivan@siamics.net> writes:

[…]

 > Thus, my suggestion would be to:

 > • allow the caller of the url*.el facilities to explicitly state
 > whether it’s interested in a document to be returned, in some code to
 > be called, or either;

[…]

 > I guess all of the above warrant separate bug reports, which I
 > hope to file shortly.

	Filed #19822 for the first point.  Once it’s decided how to fix
	that (and if), changes for url-file, url-irc, url-news, etc.,
	wouldn’t be all that a big deal.

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A





      parent reply	other threads:[~2015-02-09 17:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-06 19:15 bug#17959: eww: FTP is not supported; but with ftp_proxy, it is Ivan Shmakov
2014-11-04 16:40 ` Ted Zlatanov
2014-11-10 21:20 ` Lars Magne Ingebrigtsen
2014-11-19  8:04   ` Ivan Shmakov
2014-11-19 17:24     ` Lars Magne Ingebrigtsen
2014-12-16 20:09     ` bug#17959: support accessing FTP services via HTTP proxies Ivan Shmakov
2015-01-12 21:40       ` Ivan Shmakov
2015-02-09 16:55         ` bug#19822: url-retrieve: allow to fail when no document is associated with the URI Ivan Shmakov
2015-12-25 19:00           ` Lars Ingebrigtsen
2015-12-28 22:07             ` Ted Zlatanov
     [not found]             ` <87fuym1b2r.fsf@lifelogs.com>
2015-12-28 22:30               ` Lars Ingebrigtsen
     [not found]           ` <87r3iawdyl.fsf@gnus.org>
2015-12-25 23:47             ` Drew Adams
2019-09-30  1:03           ` Stefan Kangas
2019-09-30  5:47             ` Lars Ingebrigtsen
2019-09-30  7:21               ` Eli Zaretskii
2019-09-30  7:30                 ` Lars Ingebrigtsen
2019-09-30  8:22                   ` Eli Zaretskii
2019-09-30 14:40                     ` Lars Ingebrigtsen
2019-09-30 15:05                       ` Eli Zaretskii
2019-10-01 13:19                       ` Stefan Kangas
2019-10-01 13:37                         ` Eli Zaretskii
2019-10-01 13:44                           ` Stefan Kangas
2019-10-01 14:51                             ` Eli Zaretskii
2019-10-01 15:13                               ` Stefan Kangas
2019-10-01 15:24                                 ` Eli Zaretskii
2019-10-01 13:56                         ` Lars Ingebrigtsen
2019-10-01 14:06                           ` Stefan Kangas
2019-10-01 14:24                             ` Stefan Kangas
2019-10-01 15:13                               ` Lars Ingebrigtsen
2019-10-01 16:07                                 ` Stefan Kangas
2015-02-09 17:04         ` Ivan Shmakov [this message]

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=87iofbdnj9.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=17959@debbugs.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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