![]() That's somehow connected with BBEdit auto-saving unnamed documents. ![]() Hundreds of untitled documents in various stages of completion, and how I will, however, note that I don't understand why you have literally Own superset of per-project document metadata the way Scrivener does. Likely to get improved searching tools than BBEdit is to maintain its It'd be great if there was one document processing tool to rule themĪll, but there probably isn't. That's not BBEdit, of course -īBEdit's lack of integration with Git is probably one of my biggest Of the BBEdit project but not under source control, and source controlīranches arguably provide another level of structure: I'm frequentlyĬreating local topic branches with git. I have a separate "In Progress" folder that's part Our product's documentation is categorized and organized by Organizing and prioritizing docs" is really going to change from person Italics by actually bolding and italicizing text, underlining links,Įtc., although I'm not sure how trivial that is.) It's hard to know whatīBEdit is failing at for you because "powerfully categorizing, tagging, Syntax highlighting engine had the capability to show Markdown bold and While this is highlyĪnecdotal, I've noticed a lot of people using BBEdit for non-coding I use BBEdit for technical writing on my job. Scrivener's tools are very much optimized for Obviously I could do those things in HTML but I'm writing a There are times I've needed to center text or even (gasp) switch I may not often be screwingĪround with tabs and stylized text, but I certainly use italics and ![]() For the audience it's primarily made for -įiction writers - this is pretty important. Like when you compile it for final output can be (and usually are)Ĭompletely different. In practice what text looks like when you're typing and what it looks Non-technical and fiction markets by and large want Word documents,īecause that's what their whole editorial flow is centered around. Technical writing still requires FrameMaker and/or SGML experience. Markdown and HTML exclusively for technical writing, but a lot of Pro writers" work the way you do, but that's not necessarily true. BBEdit and Scrivener every day, I can speak partially to this.įirst, I think it's very easy to fall into the trap of assuming "most
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |