Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support more external editors
See original GitHub issueI already use BBEdit on OS X, and would prefer to continue doing so. Is there a way I can add it in as my default editor? I can open files into it from the command line and it works fine as a git commit editor, as I have this setup in my ~/.profile :
#editor
EDITOR='/usr/local/bin/bbedit'
export EDITOR
If Github Desktop were to look for my existing editor in my environment variables… that would be too easy 😉
Could I add in the command line option to edit files using BBEdit in a config file somewhere? or, as a simpler alternative, if I could select a file (usually in History…) then invoke a menu item (Under Repository, for example) to show the file itself in the Finder, instead of the repo, that would resolve my issue.
Version
Github Desktop 0.8.0 macOS 10.12.6
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:21 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
A request for Visual Studio 2017: #3148
How about making any editor available as an external, with the caveat that not all editors will have access to all features? I’ve been using the same editor for twenty years, and use it literally for everything (and have extensive clippings libraries and other custom stuff I use with it), but the only option I get for an external editor is Atom? Not cool.