Brackets Linux Guide
Pages 202
- Home
- [archives] Health report data aug 2015
- [archives] Health report data jul 2015
- API Cleanup Ideas
- Areas of Expertise
- Brackets 5 15 2012 Hackathon Notes
- Brackets CodeMirror v4 Migration Guide
- Brackets Coding Conventions
- Brackets Committer Policy
- Brackets Communication Channels
- Brackets Community Testing
- Brackets Developers Guide
- Brackets Development How Tos
- Brackets Extensions
- Brackets in Browser
- Brackets JSDocs Guidelines
- Brackets Linux Guide
- Brackets Node Process: Overview for Developers
- Brackets Screenshots
- Brackets Server Smoke Tests
- Brackets shell command line arguments (proposal)
- Brackets Shortcuts
- Brackets Smoke Tests
- Building Brackets Releases
- Building CEF and Chromium
- Cache Folder
- CEF Debugging
- CEF3 vs. Chromium Content Shell
- Code Hinting API Investigation
- Code Hinting Functional Specifications
- CodeMirror v4 Integration
- Collecting End of Sprint Stats
- Command Line Arguments
- Commands, Menus and Shortcuts Implementation
- Contributing to Brackets
- Crash Logs
- Creating and Posting Brackets Hotfix Releases
- Creating Themes
- CSS Context API implementation spec
- CSSUtils, HTMLUtils
- Customize Your Code Font
- Debugging Brackets
- Debugging Test Windows in Unit Tests
- Dependency Analysis
- Extension API Research
- Extension Dependencies
- Extension Experiments
- Extension Icon Guidelines
- Extension Locations
- Extension Manager Workflows
- Extension package format
- Extension Package Manager Research
- Extension Registry Architecture
- Extension Registry Help
- Extension Repository Server API
- Extension Robustness
- Extension Testing Recommendations for SplitView
- Extension UI Guidelines
- Extension Unit Tests
- Extensions2
- File System
- File System API Migration
- File System Implementations
- File system watcher requirements
- Generating Brackets API Docs
- Google Summer of Code 2013 Project Ideas
- Grunt Setup
- Health Data
- Health Report Data
- How to Hack on Brackets
- How to Report an Issue
- How to Use Brackets
- How to write extensions
- Inline Color Editor
- Issue Clusters 1.0 Milestone
- IssueClusters
- JavaScript Code Hints
- Keyboard Shortcuts
- Language Support
- Language Support Changes
- Large Projects
- Linux Development for Contributors
- Linux Version
- Live Development: lifecycle research and future directions
- Live Development: Research for live JavaScript
- Live Preview API
- Live Preview Multibrowser
- Live Preview Overview
- Live Preview URL Mapping
- Localization
- Localization Tests
- Migrating or Syncing Brackets Configuration
- ModuleLoader
- New Code Hinting API Proposal
- Notes on CodeMirror
- Performance Metrics: JavaScript Inline Editors
- Performance Profiling
- Performance Testing
- Performance Tests Procedure
- Preferences
- Preferences Code Hints for Developers
- Preferences Overview
- Preferences System
- Preview Images Research old drafts
- Preview Images Spec
- Programmatically Opening Files in Brackets
- Pull Request Checklist
- Pull Request Process
- Pull Request Review Checklist
- Related Documents
- Release Notes
- Release Notes: 0.40
- Release Notes: 0.41
- Release Notes: 0.42
- Release Notes: 0.43
- Release Notes: 0.44
- Release Notes: 1.0
- Release Notes: 1.1
- Release Notes: 1.10
- Release Notes: 1.11
- Release Notes: 1.12
- Release Notes: 1.2
- Release Notes: 1.3
- Release Notes: 1.4
- Release Notes: 1.5
- Release Notes: 1.6
- Release Notes: 1.7
- Release Notes: 1.8
- Release Notes: 1.9
- Release notes: sprint 10
- Release notes: Sprint 11
- Release notes: Sprint 12
- Release notes: Sprint 13
- Release notes: Sprint 14
- Release Notes: Sprint 15
- Release Notes: Sprint 16
- Release Notes: Sprint 17
- Release Notes: Sprint 18
- Release Notes: Sprint 19
- Release Notes: Sprint 20
- Release Notes: Sprint 21
- Release Notes: Sprint 22
- Release notes: sprint 23
- Release Notes: Sprint 24
- Release Notes: Sprint 25
- Release Notes: Sprint 26
- Release Notes: Sprint 27
- Release Notes: Sprint 28
- Release Notes: Sprint 29
- Release Notes: Sprint 30
- Release Notes: Sprint 31
- Release Notes: Sprint 32
- Release Notes: Sprint 33
- Release Notes: Sprint 34
- Release Notes: Sprint 34.1
- Release Notes: Sprint 35
- Release Notes: Sprint 36
- Release Notes: Sprint 37
- Release Notes: Sprint 38
- Release Notes: Sprint 39
- Release Notes: Sprint 7
- Release Notes: Sprint 8
- Release notes: sprint 9
- Research: CodeMirror document linking
- Research: Design Alternatives for Split View
- Research: Drag and Drop from Finder
- Research: Extension Management
- Research: Find Replace
- Research: HTML DOM Data Structure
- Research: jQuery 2.0 Upgrade
- Research: Multiple cursors and selections
- Research: Node.JS Integration
- RESEARCH: Preference Format
- Research: Simplified LESS Support
- Research: Topcoat
- Resources
- Running Brackets Unit Tests
- Running Jasmine tests from the command line for Linux
- Simple "Hello World" extension
- Spec: Native Installers
- SplitView Architecture Notes
- SplitView Architecture Tasking
- SplitView Extension Migration Guide
- SplitView Proposed Architecture
- Suggest a Feature
- Tech Summit Product Fair Brackets
- Testing Brackets
- Testing Pritam's Linux build
- Themes
- Translations community assistance
- Troubleshooting
- Typing Speed Mini Spec
- Upgrading CodeMirror from Upstream
- User Key Bindings
- Using File Filters
- Videos
- Working with fsevents_win.node
- Working with Multiple Selections
- ZZZ (OBSOLETE) CodeMirror v3 integration
- افزونه ها در براکتس به چه معناست؟
- براکتس چیست؟
- 如何开发插件
- Show 187 more pages…
Clone this wiki locally
NOTE
As of Brackets 1.11. the Linux version is up-to-date with other platforms and this guide should not be needed anymore.
If some of the issues persists, do open an issue
Brackets Linux Guide
Parts of this guide have been contributed by @nathanjplummer and are available at https://nathanjplummer.github.io/Brackets/
How to fix common Brackets issues that may occur with the Linux Operating System.
Libcrypt11 Missing Dependency in Ubuntu
Brackets depends on libcrypt11 but newer version of Ubuntu ship with libcrypt20. If you’re using Ubuntu or a derivative (Kubuntu, Linux Mint, etc) you may get an error message similar to the following:
dpkg: dependency problems prevent configuration of brackets:
brackets depends on libgcrypt11 (>= 1.4.5); however:
Package libgcrypt11 is not installed.
dpkg: error processing package brackets (--install):
dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Errors were encountered while processing:
bracketsSolution 1: Manually Install libcrypt11
The links below will download a copy of libcrypt11 from an older version of Ubuntu. Note that libcrypt11 can coexist peacefully with newer versions.
Solution 2: Install from PPA
Ubuntu has a PPA for Brackets installs which will automatically import libcrypt11 while also keeping Brackets up to date automatically. To install from PPA, open a terminal and then:
-
sudo add-apt-repository ppa:webupd8team/brackets- If asked to install key say “yes”
sudo apt-get updatesudo apt-get install brackets
Save all-keyboard shortcut issue
Cause of issue and a workaround contributed by @haslam22 and @Pk13055
If you notice the Save all-keyboard shortcut Ctrl + Alt + S not working on some Desktop Environments such as Gnome 3, it might be overshadowed by a system shortcut to disable/enable “roll up” / “shade” on an active window.
You can enter this command (in the terminal) to disable this shortcut to get Save all working:
gsettings set org.gnome.desktop.wm.keybindings toggle-shaded "['disabled']"Alternatively, you can re-map said shortcut to another key group of your choice (for example Ctrl + Super + S) with:
gsettings set org.gnome.desktop.wm.keybindings toggle-shaded "['<Control><Super>s']"Note: The Save All option from the drop-down menu works without any modification; you can always resort to that in case you don't want to alter the system shortcut.
Lack of HiDPI support
If you have a high resolution screen, such as an Apple Retina, Brackets will ignore any HiDPI settings and present you with very small text and icons.
Step 1: Install Extension “UI Too Small”
The UI Too Small Extension increases the size of fonts inside the Bracket’s UI. Unfortunately it does not change the size of the icons. You can install the extension from the Brackets Extension manager.
- From the Brackets File Menu choose “File” -> “Extension Manager”
- Search for “Ui Too Small”
- The Extension’s author is: “Brandon Bertelsen”
- Click
Installnext to the extension name - Save your work and restart Brackets
Step 2: Change your Font Size
If the font in your work view i still too small, you can change you font size by:
- From the Brackets File Menu choose “View” -> “Themes”
- You’ll see a section Font Size:
- Increase the number in front of “px.” Be sure to leave the “px” unit.
Brackets-Electron
What is Brackets-Electron?
An alternative to the above issues is to install Brackets-Electron- a fork of Brackets that:
- Merges newer code that has not yet made it to Brackets standard
- Replaces the Brackets CEF3 Shell with a more Linux friendly Electron Shell.
Worth noting: Brackets-Electron is an unofficial fork and not supported by the Brackets team.
While being more cutting edge, and hence, potentially more error prone, Brackets-Electron does fix the above issues. Furthermore, it retains compatibility with most Brackets Extensions and can be installed alongside vanilla Brackets without conflict.
You can download Brackets-Electron here.
Install Brackets-Electron as an AppImage
While the Brackets-Electron team currently publishes .deb packages alongside the more universal AppImage format, plans are to eventually move to only AppImage Packages.
To install an AppImage:
- From the terminal, change to the directory where your AppImage is stored. Example:
cd home/user/Downloads
- Change permissions on the AppImage with command
chmod a+xchmod a+x brackets-electron-1.8.2-x86_64.AppImage
- Run image with ./imagename
./brackets-electron-1.8.2-x86_64.AppImage
Once you run the AppImage you will be given the option of installing a shortcut to Brackets-Electron in your program menu.
Click "Yes" to install to your menu.
NOTE: If you change the location of the AppImage your program link will cease to function. Put your AppImage in a more permanent location before you run it.
