joecan

I updated to 4.0 and am having the same problem with the file extension and date stamp. I saw your reply about adding the extension myself so I probably should explain the workflow that is causing the problem. My text file are named like this CATEGORYx - FILE NAME - YYYY.MM.DD.txt . Because all my files are named like this and because I'm creating text files for certain categories on a regular basis, and on multiple devices, I've created a TextExpander snippet for file names. I have a snippet for each category and the snippet places the cursor where the file name would go, so in other words the cursor is placed in the middle of all that text. However, in all other situations, be it in Byword, nvALT, Drafts, etc. I don't need the .txt extension at the end of that snippet because those programs add it for me (or don't show it at all). But with this Alfred workflow when I use my snippet the DD gets cut off in favour of the .txt extension. I'd like to try to get around this without having to create a whole new set of naming snippets just for Alfred.

Thanks for pointing me to this thread. Your workflow is great and seems to do everything I want it to do. I'm having one problem. My file naming structure ends with a date format as follows YYYY.MM.DD . But the last part (.DD) is being cutoff. I suspect this has something to do with some conflict with the file extension. Is there anything I can do on my end (other than changing my naming structure )?

I was playing around with your workflow earlier. It's really nice, but... and this is mainly because I don't know what I'm doing ... I'm not really sure how I can get it to act the way I want. I rarely tag files in nvALT because I spend most of my time in Byword. And I seem to be misunderstanding your instructions on how to remove the tag, I'd prefer a way to just turn that feature off. The other problem I'm having is that the option I want (new blank text file) is the third option. It would be nice if there were separate keyword for each of those options. Lastly, how do I make it open the file in my default text editor after creation? Sorry if these questions seem silly. Trying to figure all this stuff out.

I'm trying to replicate some of my workflows in Drafts on iOS. I really don't have a clue what I'm doing with scripting or workflow creation. So I'm here to ask for help. The workflow I'm trying to replicate is txt file creation. I've found a few that do some of the things I want, but not one that replicates the whole workflow I'm looking for. Which is this: - All .txt files to save in the same folder. - What I type after the keyword trigger would be the filename, without the .txt extension. That would be added in the workflow. - After executing the Alfred workflow, my default text editor will open that file. If anyone could help with this, it would be greatly appreciated!

I've started using Drafts on iOS more and more to append & prepend to txt files that I use regularly. I'd like to use Alfred to accomplish similar things on OS X. The problem is I'm completely lost when it comes to the coding part of creating workflows and I haven't been able to find a workflow created by someone else to accomplish what I want. So I'm hoping that someone here can point me in the right direction. The developer of Drafts posted a blog post to mimic the default append functionality that Drafts has had for a while, the Journal file. However, the format isn't exactly what I'm looking for. I've attempted to edit that workflow to suit my needs, but like I said, I'm lost when it comes to that stuff. Every time I try to edit it, it breaks. What I'm looking for is as follows: - One workflow that will append just a line of text, no timestamp. - One that will append with MM/DD - [Line of Text Here]. (This isn't as important because I can accomplish it with TextExpander if I have the previous workflow) - One that will prepend with something like this: YYYY-MM-DD [Text] --- Any help would be appreciated. Be it pointing me in the direction of learning this stuff, so I can do it myself... or someone being nice enough to create the workflows. And while I'm here, a huge thanks to the Alfred Team and all the member of the community for creating such great productivity tools!