Craig Dickson wrote:
Michael D. Schleif wrote:
Craig Dickson wrote:
Michael D. Schleif wrote:
How would you like to handle 0x08, 0x0a or 0x0d ??? Remember, we are
talking about text handling here, not binaries . . .
We can sensibly limit ourselves to printable
Craig Dickson wrote:
Eric G. Miller wrote:
Yea, but don't you need a switch to change drives?
c:\ cd d:\cygwin
c:\ Does not compute...
c:\ d:
d:\ cd cygwin
d:\cygwin
Okay, that isn't the real error message... That whole drive letter
thing is way dainbramaged...
The
Erik Steffl wrote:
Of course, if you want to admit that MacOS and Win32 can do something
better than Unix can -- which is the obvious implication of a lot of
what you've said on this subject --, be my guest.
? how could that be? what's the difference (ms-mac-unix)? the only
difference
Michael D. Schleif wrote:
Craig Dickson wrote:
Eric G. Miller wrote:
Yea, but don't you need a switch to change drives?
c:\ cd d:\cygwin
c:\ Does not compute...
c:\ d:
d:\ cd cygwin
d:\cygwin
Okay, that isn't the real error message... That whole drive letter
Michael D. Schleif wrote:
Funny, you not only twist my words; but, you still will not take
literally your own words, ``well, it's a valid character, why shouldn't
it be there?''
Liar. Who's twisting words here? I never wrote what you attribute to me.
I said all PRINTABLE characters should be
On Thu, 20 Dec 2001 00:21:51 -0600, Michael D. Schleif wrote:
Craig Dickson wrote:
Eric G. Miller wrote:
snip
However, your example is actually wrong. cd d:\cygwin is a perfectly
legal MS-DOS command; it sets the current working directory for drive D
to \cygwin, regardless of what your
Craig Dickson wrote:
Michael D. Schleif wrote:
Craig Dickson wrote:
Eric G. Miller wrote:
Yea, but don't you need a switch to change drives?
c:\ cd d:\cygwin
c:\ Does not compute...
c:\ d:
d:\ cd cygwin
d:\cygwin
Which keystrokes did I miss? I even
On Wed, Dec 19, 2001 at 09:46:41PM -0800, Erik Steffl wrote:
...
let's note that it's mostly the shell, basically all other tools
handle any characters properly (not talking about shell scripts, those
all depend on how careful the author was).
The only reason the shell is special in this
Michael D. Schleif wrote:
Craig Dickson wrote:
...
the least if the filesystem simply didn't accept them. But spaces are
meaningful to people, and should be allowed and properly supported by
the shell and other standard tools.
Yes, I can understand reasons to want to use whitespace in
On Thu, 20 Dec 2001 01:03:30 -0600, Gary Turner [EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2001 00:21:51 -0600, Michael D. Schleif wrote:
In fact, using win98se;
c:\WINDOWSa: enter = a:\
a:\cd c:\home enter = a:\
a:\c: enter = c:\home
thus you have changed the working directory
On Thu, 20 Dec 2001 01:10:21 -0600, Michael D. Schleif wrote:
Craig Dickson wrote:
Michael D. Schleif wrote:
Craig Dickson wrote:
Eric G. Miller wrote:
Yea, but don't you need a switch to change drives?
c:\ cd d:\cygwin
c:\ Does not compute...
c:\ d:
d:\
On Thu, 20 Dec 2001 01:10:21 -0600, Michael D. Schleif [EMAIL PROTECTED]
wrote:
Craig Dickson wrote:
Michael D. Schleif wrote:
Craig Dickson wrote:
Eric G. Miller wrote:
Yea, but don't you need a switch to change drives?
c:\ cd d:\cygwin
c:\ Does not
Thank you, all of you, for the responses to the question most succinctly
expressed by my subject and, arguably, poorly expressed in the body of
my original post.
I am sorry that some of my words have been taken out of context; but,
like whitespace in directories and filenames -- only an example
On Thu, Dec 20, 2001 at 01:42:07AM -0600, Michael D. Schleif wrote:
I am also sorry that Wednesday was not a very jovial day for me and my
surly nature obtained.
Let this be the end . . .
Dammit! I'm just ready to plonk the guy and he shows his human side.
--
Nathan Norman - Staff
Craig Dickson wrote:
Erik Steffl wrote:
Of course, if you want to admit that MacOS and Win32 can do something
better than Unix can -- which is the obvious implication of a lot of
what you've said on this subject --, be my guest.
? how could that be? what's the difference
Ken Irving wrote:
On Wed, Dec 19, 2001 at 09:46:41PM -0800, Erik Steffl wrote:
...
let's note that it's mostly the shell, basically all other tools
handle any characters properly (not talking about shell scripts, those
all depend on how careful the author was).
The only reason
On 19 Dec 2001 22:23:26 -0500
Matt [EMAIL PROTECTED] wrote:
This isn't a gui vs. console flame war. Many of us, myself included,
use the console quite a bit -- tex over wysiwyg for most written texts,
if you ask me. Lilypond over Finale for musical scores...
Well here you are clearly wrong.
On Wed, 19 Dec 2001 19:58:06 -0800
Eric G. Miller egm2@jps.net wrote:
c:\ cd d:\cygwin
c:\ Does not compute...
c:\ d:
d:\ cd cygwin
d:\cygwin
Okay, that isn't the real error message... That whole drive letter
thing is way dainbramaged...
Sorry, you are right, I always forget about that
On Wed, 19 Dec 2001 20:50:31 -0800
Craig Dickson [EMAIL PROTECTED] wrote:
Christoph Simon wrote:
Someone already stated that the space is a token separator (in many
computer related contexts, not just limited to unix like OSs, but
including MS-Windows). Also, if you find your for-loop
* Craig Dickson ([EMAIL PROTECTED]) spake thusly:
Dimitri Maziuk wrote:
Wrong. There's a reason why people with half a clue don't put
spaces in paths, and inadequacy of tools is not it. Unless your
computer can read minds, it has no way of telling when the
whitespace's supposed to be
Michael D. Schleif wrote:
Whitespace has -- nearly -- always been a possible character within
directories and filenames; but, like rfc's, there has been a convention
by which we *nix'ers avoided and proselytized against such use. I
believe that the ``questionable'' tools can be re-written;
On Wed, Dec 19, 2001 at 06:32:18PM -0600, Dimitri Maziuk wrote:
Wrong. There's a reason why people with half a clue don't put
spaces in paths, and inadequacy of tools is not it. Unless your
computer can read minds, it has no way of telling when the
whitespace's supposed to be input
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've always
detested, from an sa standpoint ;
For example, on my upgraded potato box I may want to do something this
simple:
grep pump `find /etc/ -type f`
* Michael D. Schleif ([EMAIL PROTECTED]) spake thusly:
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've always
detested, from an sa standpoint ;
...
On Wed, Dec 19, 2001 at 12:26:05PM -0600, Michael D. Schleif wrote:
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've always
detested, from an sa standpoint ;
For example, on my upgraded potato box I may want
Michael D Schleif [EMAIL PROTECTED] writes:
MDS More and more, *nix developers are following the dark path of using
MDS whitespace in directory and filenames -- something which I've always
MDS detested, from an sa standpoint ;
MDS
MDS For example, on my upgraded potato box I may want to do
Ken Irving wrote:
On Wed, Dec 19, 2001 at 12:26:05PM -0600, Michael D. Schleif wrote:
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've always
detested, from an sa standpoint ;
For example, on my
Dimitri Maziuk wrote:
I'd file a bug against kde 2 and debian menu package (I presume
that's the one responsible for .../hookdir/Debian/...)
I would guess afterstep, rather than debian menu, considering the whole
path.
Craig
:[EMAIL PROTECTED]
-Original Message-
From: Michael D. Schleif [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 19, 2001 1:58 PM
To: debian-user@lists.debian.org
Cc: Debian Users List Service
Subject: Re: How to handle whitespace in filenames ???
Ken Irving wrote:
On Wed, Dec 19
Service
Subject: Re: How to handle whitespace in filenames ???
Ken Irving wrote:
On Wed, Dec 19, 2001 at 12:26:05PM -0600, Michael D. Schleif wrote:
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've
Michael D. Schleif wrote:
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've always
detested, from an sa standpoint ;
well, it's a valid character, why shouldn't it be there? IMO the
situation where users are
Erik Steffl wrote:
Michael D. Schleif wrote:
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've always
detested, from an sa standpoint ;
well, it's a valid character, why shouldn't it be there? IMO the
* Erik Steffl ([EMAIL PROTECTED]) spake thusly:
...
generally, filename should be allowed to be basically any text. I see
no reason to limit it (well, the general consesnsus among most of the
unix(-like) implementations is that you cannot include '\0' and '/').
And I see no reason to put
Dimitri Maziuk wrote:
* Erik Steffl ([EMAIL PROTECTED]) spake thusly:
...
generally, filename should be allowed to be basically any text. I see
no reason to limit it (well, the general consesnsus among most of the
unix(-like) implementations is that you cannot include '\0' and '/').
Michael D. Schleif wrote:
How would you like to handle 0x08, 0x0a or 0x0d ??? Remember, we are
talking about text handling here, not binaries . . .
We can sensibly limit ourselves to printable characters for filenames;
it's silly to suggest that if you let people use spaces, next they'll
want
Michael D. Schleif wrote:
Erik Steffl wrote:
Michael D. Schleif wrote:
More and more, *nix developers are following the dark path of using
whitespace in directory and filenames -- something which I've always
detested, from an sa standpoint ;
well, it's a valid character,
Dimitri Maziuk wrote:
* Erik Steffl ([EMAIL PROTECTED]) spake thusly:
...
generally, filename should be allowed to be basically any text. I see
no reason to limit it (well, the general consesnsus among most of the
unix(-like) implementations is that you cannot include '\0' and '/').
Dimitri Maziuk wrote:
Wrong. There's a reason why people with half a clue don't put
spaces in paths, and inadequacy of tools is not it. Unless your
computer can read minds, it has no way of telling when the
whitespace's supposed to be input separator, and when it's just
a part of
Craig Dickson wrote:
Dimitri Maziuk wrote:
Wrong. There's a reason why people with half a clue don't put
spaces in paths, and inadequacy of tools is not it. Unless your
computer can read minds, it has no way of telling when the
whitespace's supposed to be input separator, and when
Craig Dickson wrote:
Michael D. Schleif wrote:
How would you like to handle 0x08, 0x0a or 0x0d ??? Remember, we are
talking about text handling here, not binaries . . .
We can sensibly limit ourselves to printable characters for filenames;
it's silly to suggest that if you let
Craig Dickson wrote:
Dimitri Maziuk wrote:
Wrong. There's a reason why people with half a clue don't put
spaces in paths, and inadequacy of tools is not it. Unless your
computer can read minds, it has no way of telling when the
whitespace's supposed to be input separator, and when
On Wed, 19 Dec 2001 16:56:26 -0800
Craig Dickson [EMAIL PROTECTED] wrote:
Michael D. Schleif wrote:
How would you like to handle 0x08, 0x0a or 0x0d ??? Remember, we are
talking about text handling here, not binaries . . .
We can sensibly limit ourselves to printable characters for
If Unix were just being developed today, without thirty years of history
and backward-compatibility to worry about, I'd submit a bug report for
things like this. I understand why it works the way it does; I just
think it was a mistake.
cheers applause nods of approval
While it doesn't
cd c:\Program Files
Pure Linux users always forget to learn basic windows know-how before
trashing it -- cd c:\Program Files would work just fine. cd
/mswin/Program Files would work just fine as well, no? I was feeling
ghetto today so I typed cd /mswin/Program\ Files and got around just
On 19 Dec 2001 22:23:26 -0500, Matt [EMAIL PROTECTED] wrote:
cd c:\Program Files
Pure Linux users always forget to learn basic windows know-how before
trashing it -- cd c:\Program Files would work just fine. cd
/mswin/Program Files would work just fine as well, no? I was feeling
Michael D. Schleif wrote:
Craig Dickson wrote:
Michael D. Schleif wrote:
How would you like to handle 0x08, 0x0a or 0x0d ??? Remember, we are
talking about text handling here, not binaries . . .
We can sensibly limit ourselves to printable characters for filenames;
it's silly
Christoph Simon wrote:
Someone already stated that the space is a token separator (in many
computer related contexts, not just limited to unix like OSs, but
including MS-Windows). Also, if you find your for-loop
counter-intuitive, you are demonstrating to use variables without
bearing in
Eric G. Miller wrote:
Yea, but don't you need a switch to change drives?
c:\ cd d:\cygwin
c:\ Does not compute...
c:\ d:
d:\ cd cygwin
d:\cygwin
Okay, that isn't the real error message... That whole drive letter
thing is way dainbramaged...
The drive letter thing is indeed quite
Craig Dickson wrote:
...
Of course, if you want to admit that MacOS and Win32 can do something
better than Unix can -- which is the obvious implication of a lot of
what you've said on this subject --, be my guest.
? how could that be? what's the difference (ms-mac-unix)? the only
difference
49 matches
Mail list logo
