![]() I will just set the “type” of the item that contains the heading to “heading”. In particular the trouble is how I should map it to my existing underlying outline model.įor basic block level types, such as headings it’s a pretty clear mapping. Markdowns **'s are inserted automatically when you save, but you never type or edit around them.īlock level (paragraph) formatting is more difficult to figure out in some cases. So for example to bold text, you just select and choose “bold” command it as you would in any rich text editor. I just (2 days ago) got span (within single paragraph) level formatting working pretty well now. I added a bunch of magic to FoldingText to try to work around that, but I think just switching to rich text editor style (but still saving/loading plain text Markdown) is better. Markdown is the standard for writing, plain text documents have many benefits, but I hate dealing with the actual syntax as I write. This isn’t a new idea (see ), but I think (for my vision anyway) it’s the best way. What I’m working on nowĪ fundamental feature of WriteRoom 4 is to make it a “rich text” markdown editor. Kinda a waste of time (no new function), but it needed to happen eventually and I figured now is better then later. Now the code is back, but using modern JavaScript syntax instead of Coffeescript. ![]() I almost made the first beta release in November, but then decided that I needed to work on some infrastructure stuff first and that’s derailed me until recently. Nothing in particular, just a bit more lazy then I used to be. And a bit of a slowdown in the worker (me) recently. It’s not so much bloat (I hope!), but just lots of work writing an editor up from scratch. Obviously desirable would be the ability to work with a novel size documents without the machine locking up, a document library feature, the ability to split and merge documents and folding would be nice à la FT and that’s it. I guess one year on - is it time for a progress report on v4? As a daily user of Writeroom since 1.0 (I think I got my free license for 1.0 from you in exchange for a tweet!), I would really like to NOT see it become bloatware. ![]() Particularly, I keep the document I’m actually writing on the left, so it’s next to the desktop that has the Git client, then the documents I’m referring to in decreasing order of usefulness. After rebooting, WriteRoom reopens them all (usually) but doesn’t arrange them in the same order, which is annoying because the order is important to me. Unrelated to Git, but I often have several documents open in full screen windows side by side.“Revert Changes” often backs out changes that have already been saved and committed. I’ve learned from experience that the correct answer is “Save”, after which Git correctly shows I have no uncommitted changes. It even happens when I haven’t changed anything at all since opening the document. I don’t know whether this is related to Git, but WriteRoom often asks me “Do you want to save the changes made to the document …” when I close a document but really haven’t changed anything since last hitting Cmd+S and committing the file.My current workaround is to close and reopen the file. When a file that’s open in WriteRoom gets changed by another program (e.g pulling changes from a remote git repo) I wish WriteRoom would notice this and offer to reload, or just reload without asking.My workflow is WriteRoom + Git, and I’d like a couple of things related to that.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |