{"id":33174,"date":"2021-07-20T16:23:33","date_gmt":"2021-07-20T20:23:33","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=33174"},"modified":"2021-07-26T14:56:45","modified_gmt":"2021-07-26T18:56:45","slug":"bbedit-14","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/07\/20\/bbedit-14\/","title":{"rendered":"BBEdit 14"},"content":{"rendered":"

Bare Bones Software<\/a> (tweet<\/a>):<\/p>\n

BBEdit 14.0 and later feature built-in support for the Language Server Protocol<\/a>,\n(occasionally referred to here as “LSP”, not to be confused with\nLightspeed Pascal).<\/p>

[…]<\/p>

Completions supplied by the language server are significantly more accurate and complete than those available using the built-in mechanisms.<\/p>

If a language server supports the “signature help” feature, BBEdit enables the “Show Parameter Help” command on the Edit menu; choosing this will open a panel providing assistance for filling in function parameters at the current insertion point (if applicable).<\/p>

If a language server reports issues (errors and warnings) for a file in which you’re editing, ranges corresponding to those issues get highlighted according to their severity, and the corresponding lines are highlighted in the line number bar.<\/p>

[…]<\/p>

Command-double-click on a word will direct the request to an appropriate language server and perform the equivalent of “Go to Definition”, if possible.<\/p><\/blockquote>\n\n

I’m really excited about this, as it enables all sorts of IDE-type features. I’d long hoped that Xcode would add an API to make its indexing information available to external editors. In a way, this is better because it also works with languages not supported by Xcode. It uses an open protocol that’s implemented by various open-source language implementations. If you’re using a custom language, you can write your own LSP server.<\/p>\n\n

As you might expect, to get this working requires installing a server package for each language (links here<\/a>). C-family languages and Swift “work” out of the box if you have Xcode installed. I put that in quotes because, although<\/a> the language server is pre-installed and pre-configured:<\/p>\n\n

clangd<\/code> relies on a “compilation database” which provides necessary information\nabout compiler options and lists the files relevant to the current project workspace.\nThe compilation database is a JSON file named “compile_commands.json<\/code>” which lives at\nthe root directory of the project.<\/p><\/blockquote>\n\n

Without this, it won’t even know what NSString<\/code> is. There’s a sample shell script that you can set up to generate the compile_commands.json<\/code> for each Xcode project. Note that this JSON only contains information about the project files and how they’re compiled. It’s not a list of the actual symbols to be indexed, like with ctags<\/a>, so it does not need to be regenerated frequently.<\/p>\n\n

One issue I ran into is loose C\/Objective-C files that aren’t part of an Xcode project. For example, I like to view\/search the header files from Apple’s SDKs. It’s not obvious how to generate a compilation database for those files, nor where to put it. So I end up with spurious warnings about types (even intptr_t<\/code>) and macros (such as API_AVAILABLE<\/code>) that were declared in an included file. My workaround for this is to configure .h<\/tt> files as Objective-C++ and then turn off LSP for Objective-C++ files. I mostly care about it in .m<\/tt> files, anyway.<\/p>\n\n

The compilation database does not include information about Swift files, and sourcekit-lsp<\/code> for Swift doesn’t seem to be able to figure out my project structure itself. So, when editing a Swift file, I get live reporting of syntax errors, which is great, but it doesn’t offer completions of symbols from the same framework or know how to find definitions. But neither, thankfully, does it show warnings for symbols that it doesn’t know about.<\/p>\n\n

More new stuff from the release notes<\/a>:<\/p>\n

Notes are mostly like ordinary text documents, except that you don’t have to remember to save them or even make up a name if you don’t want to. BBEdit keeps notes all together in a “notebook”. Notes exist on disk as text files; there’s no secret file format involved.<\/p>

[…]<\/p>

Added “Repeat Last Command” to the Edit menu.<\/p>

[…]<\/p>

When dragging an image or an HTML file into a Markdown document, BBEdit will generate appropriately formatted Markdown references.<\/p>

[…]<\/p>

Added the ability to drag files (not folders) from an FTP\/SFTP browser window to the Finder (and other applications that want files). When the item is dropped in its destination, BBEdit will download the file as indicated.<\/p>

[…]<\/p>

Added “Precompose Unicode” to the Text menu. This command will convert decomposed Unicode pairs (such as a letter followed by a combining accent or diaresis) into a single Unicode character, where possible.<\/p>

[…]<\/p>

Added a new script attachment point, to provide additional control over the text generated when you drop an image file into a BBEdit editing view.<\/p><\/blockquote>\n\n

It also adds language modules for R, Lisp, Go, and Rust—and a nice new icon for Big Sur. This is definitely one of the bigger BBEdit upgrades.<\/p>\n\n

Pricing is unchanged, $50 for new licenses and $30 for upgrades.<\/p>\n\n

See also:<\/p>\n