Deleting post procesing scripts crashes slic3r

[Tinchus2009]

Version

1.2.9-1120-g13f121e

Operating system type + version

win 10 64b

Behavior

In the post processing scripsts section, once you added a scrip, you cant delet it anymore without crashing slic3r, so in fact, you never cant delet it from that printing profile.

[superjamie]

Confirming this still happens in Slic3r-1.3.0-dev-8ca6171-x86_64.AppImage

[superjamie]

You can work around it by manually editing the ini file and changing

post_process = " " 

to

post_process =

[bonm014]

Where can I find that ini file?

Edit:
found it!

C:\Users<user>\AppData\Roaming\Slic3r\print

[lordofhyphens]

On Linux / Mac, ~/.Slic3r For Windows it is buried in your AppData folder structure. Searching for "Slic3r" should find it.

…

On Dec 28, 2017 3:11 AM, "Martijn de Bont" ***@***.***> wrote: Where can I find that ini file? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4065 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB8CtUR9y-3I_TfErIQZqZZrjhGDwGbks5tE1svgaJpZM4OdcBh> .

[lordofhyphens]

Another workaround is to hit Ctrl-e for a config export, edit that and then load it and save over the old Print profile.

[bubnikv]

- Windows: "C:\Users\your_user_name\AppData\Roaming\Slic3r" or "C:\Documents and Settings\your_user_name\Application Data\Slic3r" - Mac: "~/Library/Application Support/Slic3r/" - Unix / Linux: "~/.Slic3r/"

…

On Thu, Dec 28, 2017 at 4:13 PM, Joseph Lenox ***@***.***> wrote: Another workaround is to hit Ctrl-e for a config export, edit that and then load it and save over the old Print profile. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4065 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFj5IyAnK-mTIBRdBoiPy8meeB8uq2mxks5tE7AWgaJpZM4OdcBh> .

[lordofhyphens]

@bubnikv @alexrj can you think of a reason offhand of why we wouldn't want to trim excess whitespace from ConfigOptionString objects?

I can't think offhand of a use case where you would want to keep excess whitespace before and after.

[lordofhyphens]

The other solution is to check for the problem cases in _update.