Surface xdg-open errors from the open shell helper

[sridhar-3009]

Problem

The open() shell function silences both stdout and stderr from xdg-open:

open() (
  xdg-open "$@" >/dev/null 2>&1 &
)

When xdg-open fails (unknown MIME type, missing handler, bad path), the user
gets no output at all—the command just silently does nothing.

Reported in #6056.

Fix

Drop only the stderr redirection. The function remains non-blocking and keeps
stdout suppressed (avoids noise from handlers that write to it), but
xdg-open errors now reach the terminal:

 open() (
-  xdg-open "$@" >/dev/null 2>&1 &
+  xdg-open "$@" >/dev/null &
 )

One character change. The non-blocking / no-job-control-noise behavior from
#4366 is fully preserved.

[Copilot]

Pull request overview

This PR adjusts Omarchy’s interactive Bash open() helper so xdg-open failure messages are no longer silently discarded, while preserving the existing non-blocking behavior and keeping stdout suppressed to avoid handler noise.

Changes:

• Stop redirecting xdg-open stderr to /dev/null so errors are visible to the user.
• Keep the subshell wrapper and background execution to avoid job-control completion noise.

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.