id = "brackets" name = "Brackets" homepage = "https://github.com/adobe/brackets" description = "A modern open-source code editor for HTML, CSS and JavaScript that's built in HTML, CSS and JavaScript." # The brackets mark, from the project's site. icon = "https://brackets.io/img/brackets.svg" executables = ["brackets"] [dotfiles] # Adobe ended support for Brackets on 1 September 2021 and the repository is # archived; brackets.io now belongs to the Phoenix Code fork, so the homepage # above is the repository this entry describes. The paths remain # facts for the installs still out there and for the forks that kept the same # user directory. # # The user data directory, from the wiki page "Cache Folder" # (https://github.com/adobe/brackets/wiki/Cache-Folder), which names # ~/Library/Application Support/Brackets/cef_data on Mac, # %appdata%\Brackets\cef_data on Windows and ~/.config/brackets/cef_data on # Linux ("aka $XDG_CONFIG_HOME/brackets/cef_data"), and adds: "In the parent of # this folder, delete brackets.json and state.json if present". brackets.json # is the global preferences file — "Choosing Debug > Open Preferences File # opens the global preferences file 'brackets.json'" # (https://github.com/adobe/brackets/wiki/How-to-Use-Brackets). # # No named base directory fits: the directory is "Brackets" on macOS and # Windows but lowercase "brackets" on Linux, so the three are written out. paths = [ "~/Library/Application Support/Brackets/brackets.json", "~/.config/brackets/brackets.json", "%APPDATA%/Brackets/brackets.json", ] # Nothing to carve out: state.json (the open files and window position), # cef_data (the embedded Chromium profile) and extensions/user (installed # extensions, per the wiki's "Extension Locations") sit beside brackets.json # and none of them is named above. exclude = [] # Editor preferences — indentation, linting, live preview. The project-level # .brackets.json is per-project, not per-user, and neither file is a # credential. secret = [] # No machine_lines: the preferences are indentation, word wrap and theme, all # of which should follow the user. A path-scoped override block can name a # project directory, but which key that is depends on the user's projects.