Meta tags:
Headings (most frequently used words):
git, pause, why, is, using, codekit, with, one, rule, first, auto, pausing, manually, what, if, forget, switched, branches, my, settings, changed, can, you, tell, changing, stuff, there, funnier, version, of, this, page,
Text of the page (most frequently used words):
the (28), you (17), file (16), codekit (16), #settings (13), that (11), git (10), this (9), project (9), for (7), your (7), app (6), and (6), can (5), have (5), new (5), branch (5), watching (5), main (5), files (5), pause (5), branches (4), set (4), when (4), any (4), from (4), once (3), about (3), version (3), doesn (3), one (3), see (3), other (3), way (3), start (3), different (3), before (3), eslint (3), will (3), choose (3), action (3), with (3), output (3), changes (3), control (3), but (2), make (2), generally (2), process (2), what (2), are (2), why (2), stuff (2), configure (2), options (2), work (2), defaults (2), projects (2), where (2), ignore (2), calls (2), those (2), etc (2), switching (2), read (2), pausing (2), delete (2), default (2), has (2), javascript (2), named (2), sees (2), forget (2), path (2), some (2), change (2), because (2), only (2), check (2), also (2), menubar (2), bar (2), becomes (2), active (2), first (2), plugins (2), custom (2), languages (2), frameworks (2), minifier (2), tools (2), postcss (2), browsers (2), steps (2), topics (2), using (2), privacy, policy, report, bug, email, support, follow, developer, twitter, made, san, diego, yes, wrote, unfortunately, they, edited, out, bit, punching, kardashian, rest, still, pretty, humorous, blog, post, folks, tower, there, funnier, page, security, unix, allow, processes, doing, without, superuser, privileges, tell, changing, avoid, issue, instead, shouldn, note, how, supposed, example, could, debug, then, release, warn, might, not, minify, scripts, console, well, yea, had, paused, after, immediately, applied, config, codekit3, switched, changed, performing, ensures, respond, these, fake, events, boom, appears, magically, warped, back, notices, been, added, existing, information, applies, area, creates, content, event, says, okay, gone, its, deletes, old, differences, pull, switch, customized, most, likely, appear, randomly, their, happens, sequence, lots, attempts, them, finds, filesystem, mutating, underneath, expected, find, suddenly, missing, right, middle, compiling, worst, case, cause, crash, alternately, single, list, either, purple, pictured, above, press, global, keyboard, shortcut, works, toggles, tip, three, keys, left, space, plus, forward, slash, like, typing, comment, command, option, manually, automatically, optionally, happen, terminal, appropriate, box, preferences, auto, perform, large, numbers, rebasing, pulling, must, rule, faq, upgrading, mode, more, coda, sublime, text, atom, nova, editor, scripting, team, workflows, adding, environment, variables, hooks, advanced, syntax, checkers, jeet, nib, susy, zurb, foundation, bitters, bourbon, bootstrap, tailwind, gif, svg, jpeg, png, webp, image, optimizers, json, markdown, kit, slim, haml, pug, typescript, coffeescript, stylus, less, sass, bless, lightningcss, html, cache, buster, rollup, bundler, terser, babel, transpiler, npm, purgecss, autoprefixer, license, recovery, troubleshooting, know, target, build, second, paths, language, browser, sync, live, reload, getting, started, close, view, buy, now, menu, updates, help, videos, features,
Text of the page (random words):
codekit using codekit with git features videos help about updates menu buy now using codekit with git view topics close topics first steps getting started live reload browsers browser sync set language options set output paths action second steps defaults for new projects build your project set target browsers stuff to know codekit git troubleshooting license recovery postcss tools autoprefixer purgecss custom postcss plugins other tools npm babel js transpiler terser js minifier rollup js bundler cache buster html minifier lightningcss bless languages sass less stylus javascript coffeescript typescript pug haml slim kit markdown json image optimizers webp png jpeg svg gif frameworks codekit frameworks tailwind bootstrap bourbon bitters zurb foundation susy nib jeet syntax checkers eslint advanced hooks environment variables adding custom languages team workflows scripting codekit editor plugins nova atom sublime text coda 2 more read only mode upgrading from 2 0 faq one rule pause first you must pause codekit s file watching before you perform any version control action that changes large numbers of files at once switching branches rebasing pulling etc auto pause codekit 3 4 will automatically pause file watching when any version control app becomes active optionally you can also make this happen when the terminal becomes active to do that choose codekit preferences from the menubar and check the appropriate box pausing manually to do this press command option control this global keyboard shortcut works in any app and toggles codekit s file watching tip it s the three keys to the left of the space bar plus a forward slash like you re typing a comment you can also choose file pause file watching from the menubar either way you ll see the purple bar pictured above alternately to ignore file changes in a single project only un check that project in the list why because when git changes lots of files at once codekit attempts to process them but finds that the filesystem is mutating underneath it files codekit expected to find are suddenly missing or change right in the middle of compiling this can in the worst case cause a crash what if i forget most likely files in your project will appear to randomly change their settings it happens because of this sequence you have a file named main js in your project you ve customized some settings or an output path for that file you start a pull or branch switch in git git sees that main js has some differences git deletes the old main js file codekit sees the delete event and says okay this file s gone we can forget its settings and output path git creates a new file named main js with the different content codekit notices a new file has been added to the project the app doesn t have any existing settings information for that file so it applies the default settings for javascript files from your project settings area boom main js appears to have magically warped back to default settings pausing codekit s file watching before performing a git action ensures that the app doesn t respond to these fake delete events i switched branches my settings changed well yea the other branch had a different config codekit3 file when you un paused codekit after switching branches the app read that new settings file and immediately applied those settings that s how it s supposed to work this way for example you could have a debug branch where you set eslint to ignore console calls and then a release branch where eslint will warn about those calls or you might choose not to minify your scripts on one branch etc note the way to avoid this issue is to configure your project settings before you start the project see settings defaults for new projects if you configure options at the start instead of as you work your branches generally shouldn t have different settings why can t you tell git is changing stuff security unix generally doesn t allow one process app to see what other processes are doing without superuser privileges is there a funnier version of this page yes i once wrote a blog post for the folks that make tower unfortunately they edited out the bit about punching a kardashian but the rest is still pretty humorous made in san diego ca follow the developer on twitter email support report a bug privacy policy
|
