-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing text files from Windows #39
Comments
Hey, thanks! I'm uncertain if this helps, but the
Some samples are here: https://applecommander.github.io/ac/#put-standard-input-onto-disk-image-as-a-text-file But, I expect duplicating that into a user interface ought to be done. Next round of updates. ;-) |
There's no indication anywhere I can see that there /is/ a command-line app
except for a jar file with "ac" in its name.
AppleCommander really needs some documentation on how to compile and run
it, in which you could mention that there is a command-line version.
You've spent a great deal of time writing this software, but only a small
fraction of potential users will be able to figure out how to use it.
I tried altering the batch file AppleCommander.bat to run the "ac" jar, but
I can't figure out how to run it, because I have to call the batch file on
the command line, and it doesn't pass its arguments through to the jar file.
…On Thu, Jan 23, 2020 at 9:08 PM A2 Geek ***@***.***> wrote:
Hey, thanks!
I'm uncertain if this helps, but the ac command-line app does have a -pt
and -ptx option that should handle the line endings.
-pt <imagename> <filename> put stdin in filename on image
defaulting to TXT file type, setting high bit on and replacing
newline characters with $8D.
-ptx <imagename> <filename> put stdin in filename on image
defaulting to TXT file type, clearing high bit and replacing
newline characters with $0D.
Some samples are here:
https://applecommander.github.io/ac/#put-standard-input-onto-disk-image-as-a-text-file
But, I expect duplicating that into a user interface ought to be done.
Next round of updates. ;-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#39?email_source=notifications&email_token=AAVE7BGWZM7Z2JPSRXAK7YLQ7JETJA5CNFSM4KKQ7L72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJZQEJY#issuecomment-577962535>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVE7BFFZJE3IYCZAETQSCDQ7JETJANCNFSM4KKQ7L7Q>
.
|
I wonder if this is useful? https://applecommander.github.io/install/#command-line It references how to setup on the command-line and a sample bat file. (I actually can't find
It's been a while, but I think the As far as compiling, there is this: https://github.com/AppleCommander/AppleCommander/blob/master/DEVELOPER.md Since AppleCommander uses Gradle, there is a provided link to Gradle for documentation on how to use that tooling. (It is an entire ecosystem to itself, and is a large topic.) |
Great program! I had great difficulty using it to edit a text file just now.
The file import didn't work the first time, because if you try to import a file which already exists on the disk image, then instead of replacing it, Apple Commander adds another file of exactly the same name to the disk image.
The import did start to work when I first deleted the original file from the disk image.
However, the imported file had different line endings, and so wasn't readable from Applesoft.
The file export from the .DSK file created a file on my Windows system in which each line ended with hex 0D 0A.
Importing such a file back to the disk image using Apple Commander produces a file in which each line ends (according to Apple Commander's hex dump) with 8D 8A.
What we want is a file on the disk image where each line ends with 8D.
We can get this by giving Apple Commander a Windows file where each line ends with 0D instead of 0D 0A.
Neither dos2unix nor unix2dos will produce such a file, so I used the hex editor HxD to search-and-replace 0D 0A with 0D, saved that, then imported the resulting file using Apple Commander.
It worked!
The text was updated successfully, but these errors were encountered: