• Bricoleur

    is there a way to extract (or create if one does not exist within Editorial ) a uuid for editorial document?

    posted in Editorial read more
  • Bricoleur

    Thanks for the pointers.
    I was hoping it might already be in metadata (created when document created) and that it could be extracted and recorded in document or posted to other applications as useful.

    If not in the metadata then creating and storing in the text of the document would be a suitable hack for me: I'll see what I can do with the reference you point to...

    posted in Editorial read more
  • Bricoleur

    TaskPaper, TextExpander, contacts, oh my!
    iPhone, sub-workflows, and so much more.
    I'll be able to complete workflows for all my Schedule-Diary-System needs now;
    Out of the Park, omz.

    posted in Editorial read more
  • Bricoleur

    btw... Did "TaskPaper mode" make the final cut (oh please say yes...)

    posted in Editorial read more
  • Bricoleur

    Thank you, Thank you, Thank you!

    posted in Editorial read more
  • Bricoleur

    Great. Thanks @omz .... Much more elegant!

    posted in Editorial read more
  • Bricoleur

    Question: is there a way to include a comment, at the front, or end, of a Regex expression line that will be ignored when the expression is fed to the pythonista code in this workflow ...or do I have to roll my own line parser? (I don't know Regex and am simply cribbing from other sources at this point so any pointers in the right direction would be greatly appreciated.)

    OK I found answer here: http://omz-software.com/pythonista/docs/library/re.html
    (?#...)
    "A comment; the contents of the parentheses are simply ignored."

    If anyone interested this was my use case:

    I've created a front end to display many different Regex patterns and "select from list" action to give multipurpose use of this workflow.

    Two entries, for example, are:

    eMail Addresses:
    \b[!#$%&'*+./0-9=?_`a-z{|}~^-]+@[.0-9a-z-]+.[a-z]{2,6}\b
    ToC:
    ^#{1,6}\s([^#].+?)$

    The title lines do nothing but, with more than a handful of expressions being used, I simply can't trust that I will remember what each pattern extracts when I come to use some of the less frequently used entries. It would obviously be much nicer to have a line read this way:

    ^#{1,6}\s([^#].+?)$ # table of contents

    Where everything after the # is ignored as being a comment.


    So now I use:
    (?# Table of Contents ) ^#{1,6}\s([^#].+?)$

    posted in Editorial read more
  • Bricoleur

    I think you can just go into the python code ("do the search" component in the workflow) and have at it...
    If my memory serves I added the last entry myself, before taking a different approach to tackling TaskPaper functionality.

    Line 18: valid_extensions = set(['.txt', '.md', '.markd', '.text', '.mdown', '.taskpaper'])

    posted in Editorial read more
  • Bricoleur

    Thankyou!
    Great update.
    With Editorial I am this " " close to having the Schedule-Diary-System that I've been after since my first Sol-20 computer days in the prehistory of personal computing.

    The TaskPaper includes in Editorial will finally give me the S-D-S and the other things hinted, and shown, above in conjunction with the creative workflow authors in your "ecosystem" will give me the closest thing yet to my very own DynaBook!

    After a 38 year wait since my first personal computer I can wait a day, or two ;) more for perfection.

    Thanks again for a great product!

    posted in Editorial read more
  • Bricoleur

    From LeftsideWobble:
    @olemoritz @LeninRzSz and talking of the 1.1 update that was announced 6 months ago... Any new status update?

    From @olemoritz:
    @LeftsideWobble @LeninRzSz I know, I'm sorry. Hope to have some news soon. :/
    3:54pm - 10 Apr 14

    posted in Editorial read more

Internal error.

Oops! Looks like something went wrong!