public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: pen <pen_1232000@yahoo.com>
To: cygwin@cygwin.com
Subject: filenames with BANG
Date: Wed, 16 Nov 2011 23:46:00 -0000	[thread overview]
Message-ID: <32858508.post@talk.nabble.com> (raw)


Need help, Cant access html file from lynx, even though its readable by other
commands. 

$ ls -l "test bay#, wwid" 
-rw-r--r--+ 1 test Users 50999 Nov 17 03:22 test bay#, wwid 
$ file "test bay#, wwid" 
test bay#, wwid: HTML document, ASCII text, with very long lines 
$ head -2 "test bay#, wwid" 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" 
> 
$ lynx -dump "test bay#, wwid" 

Can't Access `file://localhost/cygdrive/e/test%20bay#,%20wwid' 
Alert!: Unable to access document. 

lynx: Can't access startfile 

Played around and found that if i create any file with "#, " lynx cant
understand it. 

Appreciate your help. 

-- 
View this message in context: http://old.nabble.com/filenames-with-BANG-tp32858508p32858508.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2011-11-16 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 23:46 pen [this message]
2011-11-16 23:49 ` filenames with HASH pen
  -- strict thread matches above, loose matches on Subject: below --
2011-01-28 11:13 3.Using Cygwin, Special filenames, Invalid filenames Masaki_Takasu
2011-01-28 11:41 ` Csaba Raduly
2011-01-28 11:45   ` Corinna Vinschen
2011-11-16 23:35     ` filenames with BANG pen
2011-11-16 23:45       ` Eric Blake
2011-11-16 23:47         ` pen

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

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

  git send-email \
    --in-reply-to=32858508.post@talk.nabble.com \
    --to=pen_1232000@yahoo.com \
    --cc=cygwin@cygwin.com \
    /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).