Folding Text Workflow

This workflow is a work in progress. As I come up with more things I want to do with Folding Text program, I will be adding to this workflow. If there is something you would like to see added, just let me know. Most of the functions I found on the FoldingText website and compiled them here for easy use. The new bookmarking feature is the coolest thing!

Command Description
ft:autofocus This does the autofocus workflow. Move the todo at the current cursor to the bottom most “# Autofocus.todo” list. It creates one if there is not one.
ft:next Find the “@next” todo tag, makes it @done, and sets the next todo as @next.
ft:marked Open the current file in
ft:tagremove Gives a list of tags in the current document and will remove all the ones selected in the list.
ft:safari This gets the tabs in the current Safari Web Browser and copies their addresses to the topmost FoldingText document.
ft:chrome This gets the tabs in the current Chrome Web Browser and copies their addresses to the topmost FoldingText document.
ft:countunfolded This will count all the characters, words, and lines of text that is not folded. Great for geting word counts of an article with all non-essential areas folded away!
ft:getvisible This copies all the unfolded text to the clipboard.
ft:open This will allow you to open any FoldingText, Markdown, or plain txt files in your home directory. It looks for the ‘ft’, ‘md’, ‘txt’ extensions.
ft:gototag This will list every tag in the topmost document. When you select one, all lines without that tag are folded away. Place the cursor in a line and unfold and you are there in the document.
ft:openfilelist This will open every file you have in the FoldingText file list.
ft:AddFile This file action allows you to place files in to your FoldingText file list.
ft:showfiles This shows you every file in your file list. Selecting one will open just that one file, or bring it to the front if it is already open. Select a file with cmd and the file will be taken off the list (but not touched on the HD).
ft:docs This gives a list of FoldingText documentation documents you can select and open.
ft:addurihandler This adds a system script to handle “ftdoc://” URIs by loading the file specified in FoldingText. It works to launch bookmarks to files and a location in the file.
ft:mbkmark This gets a URI for the current cursor location in the topmost FoldingText document and adds it to the bookmark list. You have to supply a name for the bookmark.
ft:bookmarks This shows every bookmark and allows you to open it, remove it (function key), or create a markdown link to the bookmark and paste into the topmost application (command key).
ft:inbox This allows you to add a message line to the end of a block with the @inbox tag.
ft:notetag This one will get a list of tags in the top FoldingText document. The user can select a tag and then give a message. That message will be added to the end of that tag node.
Site Layout This is a File Action that you can trigger in the Alfred browser on directories only. When you run it, it creates a file of the directory structure there down with clickable links to each file for FoldingText. You have to have the FoldingText URI handler installed. Once created, it will open the file in FoldingText. The lastest version makes use of Alfred URI Handler.
ft:lastsitelayout This will show the last layout generated by the Site Layout directory action.
ft:viewtags Allows for interactively showing/hiding tags using JavaScript for Automation. This script created by Robin Trew.
ft:setsearchtag This is used for the create tag files directory command for the Alfred browser.
Set Tag File Directory This File Action sets the current directory in the Alfred Browser to the directory for creating tag search files.
Create Tag File This will take the directory in Alfred Browser and search for files with the ft extensions. Those files will be listed with the lines containing the tag set using the ft:setsearchtag command.


If you like the information here, please consider a donation to keep it going! Thanks!

comments powered by Disqus