[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number : 389 Date : 2001-07-14 Author : Dan Anderson Subject : Re: View My Batch File Size(KB) : 7
Another quick suggestion to avoid text line-wrap is attaching a simple .txt file to your posting. Two potential downsides to this approach are: 1) I don't know if the Yahoo group allows attachments, and 2) generally people do not like working with attachments because of concerns with acquiring a virus as a result of opening an attachment. ______________________________________ ----- Original Message ----- From: Michael Marquart To: Sent: Saturday, July 14, 2001 11:10 AM Subject: Re: [xxcopy] View My Batch File > > Not sure if my previous msg made it through... > This technique is used in many ng, indenting by, say, 3 characters and adding > this reminder:- > > All lines starting in column 1 have wrapped from the previous line > > @echo off > xxcopy /EC /CLONE "C:\Program Files\NoteTab Std\Documents" > "D:\backup\Documents" > xxcopy /blah /blah > echo space wasting comment here > :end > > > Michael > > > On Sat, 14 Jul 2001 09:54:18 -0500, Kan Yabumoto > wrote: > > >Jack: > > > >I don't know of any well-established convention to denote a > >line-break. It would be nice if there's one. But, if you > >use any easy-to-recognize line-break notation, the viewer > >should be able to figure out. My guess is that you are > >probably better of if you break up the text by yourself > >rather than to let Yahoo message board do it for you. > > > >Let me give my suggestions. The following lines should all > >starts with XXCOPY as the first word of each line: > > > >XXCOPY c:\test\very_long_named_file.txt d:\backup\ /H /R >> > ><< /oac:\log\my_log.txt > >XXCOPY c:\test\very\long\path\*.txt d:\mylongname_so_long>> > >> > >< >XXCOPY c:\my\last_trial\here\ d:\test // when you break u>> > ><

> > >Here, I used >> to end a line and << to resume the line. > >You may come up with your own. As long as the sequence is > >relatively unique and has no similar patterns that are likely > >to appear as the real thing, it should be OK. > > > >Any other suggestions? > > > >============================================================ > > > >But, here, let me comment on the general guideline for text. > > > >First of all, as the Moderator of this group, I would like > >everybody to conform to the "PLAIN TEXT-ONLY" policy. It > >helps keep the appearance uniform on all viewers screen. > >If you have an Email client which defaults to the HTML > >formatting, please make sure to turn off the HTML format. > > > >Even with a plain text message, you may choose between the > >auto-wrap and hard-coded line break. If you choose auto- > >wrap format and send a very long line of text, the Yahoo > >group's built-in formatter automatically breaks up the > >line into a text of fixed width. > > > >On the other hand, if you hard-code the line break, you > >will have total control of the appearance. But, when > >a line is longer than the Yahoo's line length limit, > >the appearance often becomes worse than the auto-wrap scheme. > > > >I believe it is best if we run a small experiment. > >Here it is. I am writing various length text below. > > > >---- experiment ---------------------------------- > > > >--- 200-character line (the last period is 200th character) ---- > > > >This line has exactly two hundred characters in it. It has been broken up > >by Yahoo in which the text behaves as if it were written with hard coded > >lines. The period is the 200th character, right here. > > > >--- 100-character line (the last period is 100th character) ---- > > > >This line is shorter in length (with 100 characters). The last period of > >this sentence is the 100th. > > > >--- 90-character line (the last period is 90th character) ---- > > > >This line is even shorter. xxxxxxxx xxxxxxxx The last period of this > >sentence is the 90th. > > > >--- four 80-character lines (the last period is 80th character) ---- > > > >This paragraph has 4 lines. This is to show the effect of automatic line > >break. > >The sentenses were made such that the dot at the end of line are 80th > >character. > >It's harder than I thought. If I remember, this paragraph would not look > >right. > >But, even today, the DOS box of Windows 9x is set to exactly 80 characters > >wide. > > > >-- four 70-character lines (the last period is 70th character) -- > > > >This paragraph has 4 lines. This is to show the effect of line break. > >The sentenses were made such that the dot at the end of line are 80th. > >It's harder than I thought. This paragraph should probably look right. > >So, if I remember correctly, lines with 70 characters are appropriate. > > > >-- four 60-character lines (the last period is 60th character) -- > > > >This paragraph has 4 lines. I'm getting tire of doing this. > >The sentenses were made so that each line ends at column 60. > >xxxxxxxxx xxxxxxxxx With bunch of xxxxx, it's easier to set. > >yyyy yyyyyy yyyyyy yyThis line should definitely look great. > > > >-- a very long one without a break. (paragraph with 400 chars) --- > > > >Well, this experiment is about over. Don't pay attention to what is > >written in this line. It is just a bogus line which gives you the > >appearnce of something useful. If I recall correctly, a line without a > >break will be choped up by Yahoo group's built in- formatter will insert > >line breaks so that the lines will becomes hard-coded with > >linebreaks. (This line turned out to be 400 character long.) > > > >-------------- format experiment over > >----------------------------- > > > > > > > >As I write this, I don't know how the above line should look. > >If I remember correctly, the 70-character lines would come > >out OK (I'm not sure the 80 character lines). I force myself > >to use hard-coded line break within 70 columns. > > > >But, this experiment should tell us what is the right text length > >if you were to hard code the linebreak. > > > >cheers!!! > > > >Kan Yabumoto > >==================================================================== > > > >At 2001-07-14 06:00, Jack Kitchen wrote: > >>Hello > >> > >>I would like to post my batch file in order to receive constructive > >>comments but the lines are long and they wrap making viewing very > >>difficult. Any howto's to fix this? The reason too I want to post it, > >>is the batch file has four lines for backing up four folders using > >>the /CLONE switch. After processing the first line the "batch" stops > >>and I notice that the title bar greys out. If I click the title bar I > >>can proceed to the next line and so on. Strange behavor!!! How can I > >>keep the title bar selected so the batch file processes all lines > >>without interuption? Does this all make sense? > >> > >>Below is an example of the first line of file that wraps and should > >>all be on one line...... > >> > >>xxcopy /EC /CLONE "C:\Program Files\NoteTab > >>Std\Documents" "D:\backup\Documents" > > > > > > > > > >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > > > > > > > > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > >


This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.