Best Of

Update: LINQPad now uses GPT-3.5-Turbo instead of Codex, due to the latter's impending doom.

GPT-3.5-Turbo is more modern and (considerably) cheaper than Codex, however its natural language focus means that code completion tasks will inevitably output English at times instead of code (and the chance of repeating text is somewhat higher). Let me know if you come any glitches - I've already written a dozen or so transforms to minimize the issues, but there are bound to be more.

Not out of the box.

You could implement this as an extension that uses LINQPad's HTML controls. Here is a simple method that dumps content inside a div with a border:

void Main()
{
    object content = "Something you want to dump".Split();
    DumpWithBorder (content);   
}

void DumpWithBorder (object content)
{
    var dc = new DumpContainer (content);
    var div = new LINQPad.Controls.Div (dc);
    div.Styles ["border"] = "black 1px solid";
    div.Dump();
}

You could extend this with multiple DumpContainers and divs, with flexbox styles to achieve the alignment and scrolling that you want.

Check out the latest beta - it implements most of these features.

This is easily done. Will be in the next build.

I tried the same today, and the situation today is the same. Some kind of issue prevents MermaidJS from initializing correctly.
A workaround is to manually initialize it on a timer, e.g. add a call to

Util.RawHtml(
@"  <script type=""text/javascript"">
    mermaid.initialize({ startOnLoad: false});

    setTimeout(function() {
        mermaid.init(undefined,document.querySelectorAll('.mermaid'));
    }, 10);
 </script>").Dump();

to the end of the script above. That caused the diagram to render correctly, with a slight delay.

Modified Linqpad:
http://share.linqpad.net/wgdqmt.linq

Try the latest beta:
https://www.linqpad.net/linqpad7.aspx#beta

Shift+Space to AI-complete.

Let me know your thoughts.

This works with gpt-3.5-turbo, with my prototype prompts.

Stay tuned. Good things are coming!

Using the Codex model from OpenAI is the simplest approach, and would enable some interesting features such as a list of customized prompts (think: "// Bugs in the following code:" or "// A more efficient way to write this:" or "// Outstanding thread-safety issues"), as well as allowing users to tweak AI parameters. Obtaining an API key also seems fairly straightforward.

From the analysis on GitHub Copilot, it seems that a fair bit of complexity arises in deciding when to initiate a query. It's also imperfect in that it results in false positives and false negatives. False positives equate to greater cost (ultimately borne either by higher subscription fees or higher token usage); false negatives mean waiting for something to appear when nothing does. How would you feel about a key such as Shift+Space to perform an explicit AI call? It would respond immediately with "Processing...", followed by suggestion(s), with a subsequent alpha-key triggering a customized prompt injection.

Another option is to use (the more recent) LINQPad.Controls.Hyperlink. This gives you much more control:

var link = new LINQPad.Controls.Hyperlink ("test", link => {} ).Dump();
link.Styles ["color"] = "gray";

Press Ctrl+F1 and search for "LINQPad Controls" for more info.

Also note that I'll be making a change soon that will reduce incidences of the pinned taskbar issue - particularly with betas.