codeeditapp / codeeditcli Goto Github PK

I'd like to propose that we shorten the name of our CLI. codeedit-cli is to long of a command to type into a terminal in my opinion.

VS Code uses code
GitHub uses gh
IntelliJ IDEA uses idea
Fleet used fleet
Atom uses atom
Sublime Text uses subl
Nova uses nova
WebStorm uses webstorm

But CodeEdit uses codeedit-cli.

None of these end with -cli, so why would/should we? I am not opposed to it, I just want to be consistent with what others might expect if possible. It looks like others just use the app name unless too long to type. codeedit is the same amount of characters as webstorm so I think it is safe to use.

Some other options we can consider in addition to codeedit are cedit and ce.

Currently the created artifact cannot be executed since it has to be notarized. The required steps need to be added to the Deploy workflow.

The homebrew installation fail at build phase

swift build -c release --disable-sandbox
warning: /Users/cedricloneux/Library/org.swift.swiftpm/configuration is not accessible or not writable, disabling user-level configuration features.
warning: /Users/cedricloneux/Library/org.swift.swiftpm/security is not accessible or not writable, disabling user-level security features.
warning: /Users/cedricloneux/Library/Caches/org.swift.swiftpm is not accessible or not writable, disabling user-level cache features.
warning: 'codeeditcli-0.0.9': failed loading cached manifest for 'codeeditcli-0.0.9': Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file “manifests” in the folder “org.swift.swiftpm”." UserInfo={NSFilePath=/Users/cedricloneux/Library/Caches/org.swift.swiftpm/manifests, NSUnderlyingError=0x600002d37780 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}}
warning: 'codeeditcli-0.0.9': failed closing cache: Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file “manifests” in the folder “org.swift.swiftpm”." UserInfo={NSFilePath=/Users/cedricloneux/Library/Caches/org.swift.swiftpm/manifests, NSUnderlyingError=0x600002d20750 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}}
error: 'codeeditcli-0.0.9': Invalid manifest
/private/tmp/codeedit-cli-20230226-34880-1i80xsc/CodeEditCLI-0.0.9/Package.swift:4:8: error: no such module 'PackageDescription'
import PackageDescription
       ^
make: *** [build] Error 1

Being able to run sudo codeedit and being able to edit root/system files

or maybe able to unlock it like this

Proposed Addition

Description

Lists the installed extensions unique identifiers along with optional display name, author, status, size, and version.

Examples

Usage

codeedit --list-extensions

codeedit -le

Which would output...

johnsmith.react
janedoe.eslint
jakedaniels.prettier

You can also pass an additional flag to get more information

codeedit --list-extensions -l

Which would output...

ID                    Name      Author      Version
===================================================
johnsmith.react       React     John Smith    1.1.4
janedoe.eslint        ESLint    Jane Doe      2.1.2
jakedaniels.prettier  Prettier  Jake Daniels  1.6.3

Add for example MIT License, BSD License, Apache License or any other open source license.

Having a LICENSE file can help establish trust and openness with regard to the project and its authors, which can be important when collaborating with other developers or when publicly distributing the project.

For more information, visit the GitHub Docs:

• Licensing a repository
• Adding a license to a repository

Currently codeedit command just opens existing files and fails if you try to use it to create one. It would be more convenient if command will create and open a file if it does not exist and just open if it exist (e.g. code on VSCode works this way)

• add codeedit-cli to homebrew to make it possible to install it using brew install codeedit-cli

Requirements

• #1

Instead of

codeedit-cli Example.swift -l 43 -c 10

can we instead do something like...

codeedit Example.swift:43:10

• Change codeedit-cli to codeedit
• instead of -l and -c, the filename line and column are separated by :

This seems to be standard and is the case with VS Codes CLI. See their documentation on open for reference.

Overview

Users need to be able to open files and folders from the command line in CodeEdit.

Folder

codeedit ./my-project

File

codeedit index.html

You should also be able to add an optional line and column

codeedit index.html:50

or

codeedit index.html:50:15

References

• VS Code implementation

• add autocompletions for Fig

Requirements

• #1
• #14

Proposed Addition

Description

When opening a file, tell CodeEdit to open the file in the last active window instead of opening the file in a new window (default behavior).

Examples

codeedit Example.swift:43:10 --reuse-window

codeedit Example.swift:43:10 -r