Bug 52317 - Debugging on external console when FISH shell is used is broken
Summary: Debugging on external console when FISH shell is used is broken
Status: CONFIRMED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger (show other bugs)
Version: 6.2.0 (C9)
Hardware: PC Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: David Karlaš
URL:
Depends on:
Blocks:
 
Reported: 2017-02-06 13:11 UTC by Jason Imison
Modified: 2017-02-06 20:36 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
bug (215.62 KB, image/jpeg)
2017-02-06 13:11 UTC, Jason Imison
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 52317 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Jason Imison 2017-02-06 13:11:10 UTC
Created attachment 19726 [details]
bug

It fails with the message

```
$? is not the status. In fish, please use $status
```

(see attachment)
Comment 1 Lluis Sanchez 2017-02-06 18:12:39 UTC
I assume Jason confirmed it.
Comment 2 Anders Hovmöller 2017-02-06 20:36:07 UTC
Jason filed it on my behalf. The fix is probably: instead of sending "clear; open ..." to Terminal.app, you should send something like "bash -c "clear; open..."