computers suck, part 934,251,634,794,854
Jul. 22nd, 2004 04:24 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
chhotiiUsing Cygwin under Windows. It's supposed to be a spiffy new version of Cygwin.
So, .bashrc is such a small and simple file, I figured it would be faster to use ed to edit it than to either install emacs or learn vi. Don't trust any of the Windoze tools to edit a file that is for the consumption of a Unix program, the line-endings wouldn't go over well.
After many hours of not understanding why things Just Weren't Working, opened a file (that I had edited with ed) in notepad.exe, just for kicks. Discovered that when I make a boo-boo and hit backspace, the text passed on to ed by the terminal contains my typo and the backspace character. Not that I would have found this out using 'cat .bashrc' in the terminal window, 'cause it displays as though the typo and backspace don't exist. Same thing when I get bits of text out of the file in error messages. Ironic, had to go to Windoze to find out what was really in the file.
Turns out, all that time I was wondering why I wasn't allowed access to /usr/local/cvs, what the computer was really trying to say was, you can't have access to /usr/local.{backspace}/crs{backspace}{backspace}vs because heh, silly, it doesn't exist.
AAAAAAAAAAAAAAAAAAAAAAAAaaaaaaaaaaaaaaaaaaaaaaAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGG!!!!!!!!!!!!!!!!
No, I still don't want to learn vi.
So, .bashrc is such a small and simple file, I figured it would be faster to use ed to edit it than to either install emacs or learn vi. Don't trust any of the Windoze tools to edit a file that is for the consumption of a Unix program, the line-endings wouldn't go over well.
After many hours of not understanding why things Just Weren't Working, opened a file (that I had edited with ed) in notepad.exe, just for kicks. Discovered that when I make a boo-boo and hit backspace, the text passed on to ed by the terminal contains my typo and the backspace character. Not that I would have found this out using 'cat .bashrc' in the terminal window, 'cause it displays as though the typo and backspace don't exist. Same thing when I get bits of text out of the file in error messages. Ironic, had to go to Windoze to find out what was really in the file.
Turns out, all that time I was wondering why I wasn't allowed access to /usr/local/cvs, what the computer was really trying to say was, you can't have access to /usr/local.{backspace}/crs{backspace}{backspace}vs because heh, silly, it doesn't exist.
AAAAAAAAAAAAAAAAAAAAAAAAaaaaaaaaaaaaaaaaaaaaaaAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGG!!!!!!!!!!!!!!!!
No, I still don't want to learn vi.
no subject
Date: 2004-07-22 03:09 pm (UTC)the way it handles ctrl-c (or not), which gets in the way of "emacs -nw", and forces
you to either type out "x save-buffers-kill-emacs" to quit, or alternatively,
EXPORT cygwin=tty will eliminate that, but leav you in raw mode upon exit from emacs.
Yuck. On the other hand, the cygwin port of Xfree86 works wonderfully, so i just use
Xterm windows, which emacs -nw works fine in.
On the whole, Cygwin Is Your Friend and is the only thing that makes dealing with
windows something i can deal with.
BTW, just as in the the unix world, "od -c" is what you want to use to see what is
*really* in that file. Notepad will decieve you as well, just in different ways.
Cygwin's "od" works just fine. Also, you *can* set up cygwin to use MS-DOS-style
line termination if you want, although i never do that.
-phil
no subject
Date: 2004-07-22 03:12 pm (UTC)"less-than-sign ESC greater-than-sign" as a tag of some sort, and
deleted it. Oy.
no subject
Date: 2004-07-22 07:58 pm (UTC)