This is an issue with Coda 2, I believe Panic is working on an update. In the meantime, there is a way around it if you open the generated CSS file inside of Coda it will notice it has changed for publishing. This is an issue with Coda 2, I believe Panic is working on an update. In the meantime, there is a way around it if you open the generated CSS file inside of Coda it will notice it has changed for publishing.
Just to confirm, this issue was closed but it reappeared sometime after v2.5 correct? On Feb 2, 2016 , "Ryan Krug" [email protected]: I'm trying to carve out some free time to test these.
”) Hey, maybe I could import clippings from BBEdit? Alas, I couldn’t readily examine Coda’s clipping syntax, because its clippings are not stored in the obvious place. I delved because the process of trying to solve that problem revealed so much about Coda 2 that I was disappointed to learn. So where’s i Cloud sync to the awesomely named i Pad companion app, Diet Coda? an external script, or even just another editor for some specialized task, something I do, oh, — you are SOL. It’s not that I exactly expect those two features to talk to each other, but it’s got a so-close-yet-so-far stench that makes the lack of an explicit sync feature much more exasperating.
They’re just text, with a simple and highly translatable syntax! There is a “~/Library/Application Support/Coda/Clippings” folder … It was incredibly natural to assume that would be there. But the site publish feature is intended to duplicate sync functionality by showing you only changed files and letting you upload them and them alone. Meanwhile, in the immediately adjacent source control pane, is another large dollop of irony: Coda “knows” full well, via Git, that I’ve changed 32 files with a script, and that information about changed files is . I’m a little embarrassed to admit that I really did eagerly wait for this product, assuming all along that it would probably become my new default working environment.
The most general problem is that Coda 2 is obviously bogged down by eye candy.
Oh, and when you export them, Coda creates an opaque file, blocking reverse engineering for any casual tinkerer. That’s when I lost interest in the clipping problem. Coda 2 does sync site settings between copies, and this is something I need. After seeing that, I felt less surprised that sync is AWOL from Diet Coda, but also less forgiving. Coda looked very much like what I always had in mind to replace BBEdit. I won’t be holding my breath for the next version — despite the many genuinely neat ideas in this tool, there are too many things in Coda that are worse than just “wrong for me.” Le sigh.
I pretty routinely want to take my publishing show on the road. From Panic’s change notes for 2.0.1: “Hopefully improved the reliability of i Cloud.” No shit, because it’s pretty horrid right now.
These bookmarks appear in the Code Navigator pane, and allow you to jump to the corresponsing line of text with a single click.
⇧ top Git integration (for Git X/Gity): Zen Coding (*): and here: https://github.com/sergeche/tea-for-coda White Out (Remove trailing whitespaces): Line Commands (Move and duplicate lines): (*) What is Zen Coding?
It tells me this in a modal dialog sheet, for a file I have to open about fifty times a week, one of the eight books I’ve written. BBEdit grunts when lifting a 5MB text file, but it does not stagger. I use shortcuts for clippings in BBEdit about seven hundred times per day. If it were printed, I think I could probably still mail it in a #10 envelope. Back in the bug rant, I mentioned that I can’t assign shortcuts to clippings in Coda 2 without a kee-rash.