Provide option to extract with conversion and keep original filenames about ciderpress

[fadden]

This might be considered orthogonal to the feature request, but: would it make sense to avoid the rename by having Merlin32 accept both ".S" and ".S.TXT"?

I think the answer to that depends on the answer to the question, "what should happen when you double-click on the file in Windows?" If you'd like it to open your text editor of choice, then having it end in ".TXT" would be reasonable. If it's supposed to open an editor specific to ".S" files, then naming them ".S.TXT" makes less sense.

(I haven't used Merlin32.)

[roughana]

Thanks for the suggestion, but I don't think that's the right way to go.
Having the Merlin files as .S gives Windows the opportunity to associate a relevant app. I can imagine wanting different behavior for .S vs . txt.
Within a large project there are many references to .S files within Merlin source files that would need to be replaced. This would divide the source from its original heritage and co-mingling within a source code repository would be messy.
Regards
Andrew

Sent from my iPhone

On 7 Jul 2015, at 6:42 am, Andy McFadden [email protected] wrote:

This might be considered orthogonal to the feature request, but: would it make sense to avoid the rename by having Merlin32 accept both ".S" and ".S.TXT"?

I think the answer to that depends on the answer to the question, "what should happen when you double-click on the file in Windows?" If you'd like it to open your text editor of choice, then having it end in ".TXT" would be reasonable. If it's supposed to open an editor specific to ".S" files, then naming them ".S.TXT" makes less sense.

(I haven't used Merlin32.)

—
Reply to this email directly or view it on GitHub.

[fadden]

Change pushed in 4.0.3-a3.