Subject:
|
Re: Multiple MovedTo Arguments Really Legal?
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Fri, 5 Mar 2004 18:52:35 GMT
|
Viewed:
|
883 times
|
| |
|
|
In lugnet.cad, Tore Eriksson wrote:
> In 973p11.dat the first line reads:
> 0 ~Moved to 973p1a, 973p1b, 973p1c
>
>
> L3P can obviously handle this correctly, but my utility movedto.exe for one,
> treats the input like this:
> 1 1 0 0 0 1 0 0 0 1 0 0 0 1 973p11.dat
>
> is altered to:
>
> 1 1 0 0 0 1 0 0 0 1 0 0 0 1 973p1a, 973p1b, 973p1c.dat
You are not supposed to actually use the information in the comment,
it's only informational.
The ~ tells mklist to ignore this part.
Just ignore the line, the following line type 1 will automatically redirect you to the new part.
/Lars
|
|
Message has 1 Reply:
 | | Re: Multiple MovedTo Arguments Really Legal?
|
| (...) When rendering Datsville, you'll recieve several hundreds of "Part n Moved moved to nn" messages. It is totally necessary to find a way to eliminate them, so I invented the movedto utility. (...) Yes, that's one of the uses for the "~Moved (...) (20 years ago, 5-Mar-04, to lugnet.cad, lugnet.cad.mlcad)
|
Message is in Reply To:
| | Multiple MovedTo Arguments Really Legal? [DAT]
|
| In 973p11.dat the first line reads: 0 ~Moved to 973p1a, 973p1b, 973p1c L3P can obviously handle this correctly, but my utility movedto.exe for one, treats the input like this: 1 1 0 0 0 1 0 0 0 1 0 0 0 1 973p11.dat is altered to: 1 1 0 0 0 1 0 0 0 1 (...) (20 years ago, 5-Mar-04, to lugnet.cad)
|
19 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
