XPost: alt.windows7.general   
   From: V@nguard.LH   
      
   "R.Wieser"  wrote:   
      
   > Vanguard,   
   >   
   >>> IOW, it gets a signal someone tried to open a document with the same   
   >>> name it already has, but than blithely ignores al that information.   
   >>   
   >> There is no "dirty bit" to identify a file has been changed after it   
   >> has been loaded   
   >   
   > Why should a "dirty bit" be involved ?   Just throw whatever is in there out   
   > and reload the provided file.  Not really rocket science.   
   >   
   >> in any process with a file handle on it.   
   >   
   > Mistake.  As reading this thread about how wordpad (doesn't) deals with its   
   > underlying document should have shown you (there is no "handle" it keeps).   
      
   No process can open a file to read or write without first creating   
   (open) a file handle (descriptor) on it.  That's how file I/O works.   
   Once the file has been buffered, the file handle may no longer needed   
   (closed).  You'd think an editor would leave open the file handle to   
   accomodate writes, but it could also close the handle, let you make   
   edits to its buffer, and then save the changes later (open the file,   
   write, close the file).   
      
   >> yes, there is a dirty bit to let the editor there was a change to   
   >> prompt you on exit to save changes.   
   >   
   > Second mistake : trying to conflate the files "dirty" bit with the one   
   > which signals that the editors contents where changed.  Nasty move.   
      
   "signals that the editor's content were change".  That's the dirty bit,   
   change flag, or whatever term you want to use.  When you change anything   
   in the editor, it tracks there was a change.  Even if you delete a space   
   and re-add it, the dirty bit aka change flag aka pick-your-term tracks   
   there was a change.   
      
   >> You want cooperating that doesn't exist.   
   >   
   > Fourth mistake.   
   >   
   > And that was told to me (by you or anyone else) ... where ?   
      
   How about EVERYTHING that has participated here telling you about   
   workarounds instead of the miraculous command-line arguments you WISH   
   Wordpad had?   
      
   >> The root of the problem is Wordpad is   
   >   
   > (that it)   
   >   
   >> has no command-line args (other than filespec and /p),   
   >   
   > Nice to see you contradict yourself in a single line. :-)   
      
   You're not only uber pendantic, but want to omit that exclusions can be   
   specified in a rule.  Okay, let's see if you can manage to cogitate   
   using your two brain cells to figure out the following.  Syntax is:   
      
   wordpad.exe [/p]    
      
   That's it.  That's all you get.  Nothing more.  No other command-line   
   arguments available regardless of what you wish for.  You act like a   
   child that thinks everything must be your way.  Now go searching for   
   yourself to find someone citing more command-line arguments for Wordpad.   
   Enjoy wasting your time.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)