LineSmith Support

The Commands Are Not in Xcode's Editor Menu

Keep LineSmith in your Applications folder, and launch it at least once before enabling its extensions. macOS offers the extensions to Xcode from wherever it registered the app, and only while that copy stays put, so keeping a single copy in Applications avoids stale or duplicate entries in System Settings.

On macOS Sequoia 15 or later, open System Settings ▸ General ▸ Login Items & Extensions. Under Extensions, select By App, click the info button next to LineSmith, then turn on both Line and Editor+. Click Done. If you're viewing By Category, open Xcode Source Editor instead.

On macOS Sonoma 14, open System Settings ▸ Privacy & Security, scroll to Extensions under Others, then open Xcode Source Editor and enable both Line and Editor+.

Quit and reopen Xcode, open a project and select a source code file. Look under the Editor menu, not Edit. Xcode reads its source editor extensions at launch.

If the commands are still missing, try the checks below and include the results when contacting support.

Another Source Editor Extension Behaves the Same Way

Try another Xcode Source Editor extension on the same Mac and in the same Xcode installation. Follow that app's setup instructions and enable its extension before testing.

First, check whether it appears under Xcode Source Editor extensions in System Settings. Then restart Xcode, open a source code file and check whether its commands appear in the Editor menu.

If the other extension is also missing, this may point to a shared Xcode or macOS extension registration issue. It does not establish the cause on its own.

If the other extension works while LineSmith does not, that helps us focus on LineSmith's extension packaging or registration. Send us the other extension's name and the result of both checks.

If Xcode Source Editor Extensions Are Missing System-Wide

If the Xcode Source Editor category is missing or another properly enabled extension also fails to appear, you can try the following workaround reported by other extension developers. It is not a guaranteed fix for every macOS or Xcode version.

Quit Xcode. In Finder, locate the Xcode app you actually use. Rename it — Xcode.app to Xcode-Temp.app, for example — then rename it back. Reopen that copy of Xcode and check System Settings and the Editor menu again with a source file open.

If you manage multiple Xcode installations, keep track of the original name and path and use your Xcode manager to restore its expected naming. You do not need to delete Xcode or move it to the Trash for this check.

If this does not help, contact support with the checks above and the paths of your Xcode installations. Further registration troubleshooting depends on which copy of Xcode you use.

Assigning Keyboard Shortcuts

Shortcuts are assigned in Xcode, not in LineSmith: open Xcode ▸ Settings ▸ Shortcuts — the pane is called Key Bindings on Xcode versions before 26 — and search for the command by name.

If a chord does nothing, another Xcode command or a system shortcut is probably claiming it first. Xcode marks conflicting bindings in the same pane.

Bindings are stored against a command's identifier, which never changes between LineSmith versions, so they survive app updates.

A Command Did Nothing

Some commands decline on purpose rather than guess. Generate Memberwise Initializer and Generate CodingKeys stop when the declaration uses multi-binding or complex multi-line properties the scanner cannot read safely, when a member shares a line with the type's opening or closing brace, or when the type already has one. Generate Memberwise Initializer also stops at a property wrapper with no initial value, and at a property with no type annotation whose value is anything but a plain literal or a call with no arguments, such as Date().

Split Line by Comma needs a single line containing a comma outside a string, regex literal or code-completion placeholder. Join Lines declines on the last line of a file.

The nine Editor+ commands read Swift syntax and are meant for Swift files. The 22 Line commands work in any file Xcode's source editor opens.

Upgrading from TextPlus

LineSmith is the same App Store record that shipped as TextPlus, renamed in version 2.0. Updating in place keeps everything.

All 19 inherited command identifiers are unchanged, so the keyboard shortcuts you assigned in Xcode keep working. The 12 new commands use new identifiers and replace nothing.

Tips and Billing

Tips are optional and unlock nothing — the app is identical with or without one, so there is no purchase to restore. You can tip again whenever you like.

Tip purchases are processed by Apple. Refunds and billing questions have to go to Apple rather than to us.