* Samba - windows and unix end-of-line conventions
@ Rich Caloggero
` Kirk Wood
0 siblings, 1 reply; 3+ messages in thread
From: Rich Caloggero @ UTC (permalink / raw)
To: speakup
I've finally got Samba working. What I originally invissioned using it for
is to be able to administer a linux server remotely from a windows machine.
I like windows for its file browsing and easy text editing (cursors are
tracked and movement commands are easy and intuitive). I have bad hands so
typing filenames gets tedious, so running linux from the shell gets hard on
the hands. Emacspeak is ok, but I use windows for e-mail and music stuff, so
it just seems natural to use it for my user interface stuff, and linux as my
server machine.
Now for the question: the unix newline convention is to terminate lines
with just a line feed character (ascii 10). WIndows insists on seeing the
pair of characters ascii 13, followed by ascii 10. Is there a way to have
Samba do some sort of translation when a file is opened from the windows
side, perhaps based on the file extension, which would turn any unix end of
line sequences into windows sequences, and vice versa when the file was
written back to the Linux end? Seems like something someone has implemented,
but where to find it... Seems like something one could do with a shell
script, but how to get Samba to call it...
Rich
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Samba - windows and unix end-of-line conventions
Samba - windows and unix end-of-line conventions Rich Caloggero
@ ` Kirk Wood
0 siblings, 0 replies; 3+ messages in thread
From: Kirk Wood @ UTC (permalink / raw)
To: speakup
The difference between windows and unix with new lines is not something
inherant in how they store a file. If for instance you edit a file that
resides on a linux box using windows, your new lines will have the two
caracters. Now for the record, this was not some stupid trick thought up
by mr gates. If you happen to want to blame someone blame Digital for
making cpm follow this convention.
There are both windows and unix programs to either add or strip the extra
character out of the lines. Alternativly, if you just want to view a file,
you can use internet explorer. It handles the unix style files just
fine. Or you could write a new editor for use in windows. Or you could
just go with linux. Or you could just go with windows, or you could....
=======
Kirk Wood
Cpt.Kirk@1tree.net
"When I take action, I'm not going to fire a $2 million missle at
a $10 empty tent and hit a camel in the butt. It's going to be decisive."
- President George Bush
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Samba - windows and unix end-of-line conventions
@ Holmes, Steve
0 siblings, 0 replies; 3+ messages in thread
From: Holmes, Steve @ UTC (permalink / raw)
To: 'speakup@braille.uwo.ca'
This might depend on when you deal with the file. I would think the only
time this is a real issue would be when you display text contents or open
the thing up in a text editor. If this be the case, I would recommend a good
editor that will recognize the end-of-line convention in use and retain this
upon saving the file. NoteTab pro is one such editor that will do this. Thus
you can edit unix or DOS/Windows from the same place and have no difference
to you.
Sorry for the off topic nature of this message but figure this would help
this guy out til he sees more of the light and comes fully into the unix
family:).
-----Original Message-----
From: Rich Caloggero [mailto:rjc@MIT.EDU]
Sent: Wednesday, October 31, 2001 12:00 PM
To: speakup@braille.uwo.ca
Subject: Samba - windows and unix end-of-line conventions
I've finally got Samba working. What I originally invissioned using it for
is to be able to administer a linux server remotely from a windows machine.
I like windows for its file browsing and easy text editing (cursors are
tracked and movement commands are easy and intuitive). I have bad hands so
typing filenames gets tedious, so running linux from the shell gets hard on
the hands. Emacspeak is ok, but I use windows for e-mail and music stuff, so
it just seems natural to use it for my user interface stuff, and linux as my
server machine.
Now for the question: the unix newline convention is to terminate lines
with just a line feed character (ascii 10). WIndows insists on seeing the
pair of characters ascii 13, followed by ascii 10. Is there a way to have
Samba do some sort of translation when a file is opened from the windows
side, perhaps based on the file extension, which would turn any unix end of
line sequences into windows sequences, and vice versa when the file was
written back to the Linux end? Seems like something someone has implemented,
but where to find it... Seems like something one could do with a shell
script, but how to get Samba to call it...
Rich
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Samba - windows and unix end-of-line conventions Rich Caloggero
` Kirk Wood
Holmes, Steve
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).