[florianPat]

The script returns with exit code 1 even if the "exit 0" in the end is run.
This is due to the trap that always triggers...
I now just reset the trap after the user interaction.
Is that the right approach?

---

Note

Prevents unintended non-zero exits caused by an overbroad trap in interactive flow.

• Updates wait_for_user to trap only SIGINT (Ctrl-C), removing EXIT so the cleanup handler no longer runs on normal script completion

^{Written by Cursor Bugbot for commit 0c422f0. This will update automatically on new commits. Configure here.}

[netlify]

✅ Deploy Preview for setup-lando ready!

Name	Link
🔨 Latest commit	0c422f0
🔍 Latest deploy log	https://app.netlify.com/projects/setup-lando/deploys/6959a37ade96a7000875bf77
😎 Deploy Preview	https://deploy-preview-110--setup-lando.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 47 (🔴 down 7 from production) Accessibility: 98 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for get-lando canceled.

Name	Link
🔨 Latest commit	0c422f0
🔍 Latest deploy log	https://app.netlify.com/projects/get-lando/deploys/6959a37a5d489b0008e9b431

[pirog]

looking at this again i think the issue is trap 'stty sane; tput sgr0; echo; exit 1' SIGINT EXIT should actually be trap 'stty sane; tput sgr0; echo; exit 1' SIGINT eg we only trap something like CTRL-C and not EXIT itself.

[florianPat]

That makes sense, I changed that and amended :)