finnmatti

And what you have found is something to run applescript on another app - namely iTunes - but this is not something that allows you to offer your own interface.

Since the new Evernote is built on Electron, I have to say my hopes are somewhat slim that it will be actually delivered. Electron itself at least has no AppleScript support atm and from reading the issue ticket on Github it’s not a trivial task to implement support for it.

Where does it say that applescript is forthcoming this announcement doesn't inlcude that info, neither does the What's new in Evernote for Mac include this info. So where is it from? EDIT: and of course now I found it. The announcement on the blog.

(You'll need Keyboard Maestro for this) Somewhat in the same spirit as my other posts (autocomplete helper for tags and notes) I offer a Keyboard Maestro Macro to enhance the functionality of Evernote. This time the macro is used to change a note's title and update the links to this note in other note. See the following gif: Setup/Usage Pick a note to rename Press your hotkey for the macro In the prompt enter the new title of the note Note the notifications for the macro: There is one at the beginning of the update of the links and one in the end. Wait until the macro is finished. Done! Installation/Download Just download the file and drop it onto the Keyboard Maestro App Icon in the dock, or double click the file. Afterwards you want to add a hot key trigger (I use cmd + option + E) to it. Evernote - Search and replace Title.kmmacros P.S.: See also my blog post about this.

I have the same problem when trying to clip a pdf.

The first run can take a couple of minutes to tell you the truth. But subsequent runs only ever retrieve posts created after the last run and therefore will take mere (milli)seconds... EDIT: Right now we use the internal state management of Keyboard Maestro, but it would be rather trivial to safe and retrieve to/from a textfile or - with a little bit more work - from a database. So scaling shouldn’t be an issue. I have around 5000 Notes in Evernote at the moment and have seen no problems with the current approach.

tell application "Keyboard Maestro Engine" to set NotesLastRun to getvariable "NotesLastRun" tell application "Evernote" set noteList to {} set noteSearch to find notes "created:" & NotesLastRun repeat with thisNote in noteSearch set nLink to note link of thisNote set nTitle to title of thisNote copy {nLink, nTitle} to the end of noteList end repeat return noteList end tell There you go. As you can see: It doesn't do anything too crazy. Most of the Parsing, etc. is done in KeyboardMaestro.

Similar to my autocomplete macro for tags, this macro provides a convenient way to insert inline links to other notes. You'll need Keyboard Maestro for this. Setup/Usage Download the macros (see below) Import the Macros to Keyboard Maestro Configure a hot key trigger for the selector macro and (for example) a hotkey trigger for the collector macro (although other triggers would work, too) - I use 'ctrl' + 'alt' + 'cmd' + '+' and 'ctrl' + 'alt' + 'cmd' + 'shift' + '+', respectively Run the collector macro (be patient: the first time might take a while…) You're all set! Now just type your hot key trigger for the selector macro, search for a note, press return and the macro will do the rest. Run the collector macro periodically to ensure that the newest notes are included. Subsequent runs should be fast, since we only collect new notes since the last run How it looks Download Evernote Note Autocomplete Macros.kmmacros My blog post introducing this macro.

FYI: I updated the first message of this thread to reflect that there is now a new version of the Macro available which relies on the Applescript interface of Evernote to receive the tags, instead of a note you have to maintain manually.

This is interesting! This kind of idea might be useful if I could somehow get suggested tags when writing about a certain topic, or as you use with types of notes. This makes me think that your hierarchy is probably mostly flat for reference-type tags, right? Because for me I have three tags right now that reference evernote in some form: 00-meta.01-setup.03-reading-writing.00-notizen.02-evernote 00-meta.01-setup.08-online.10-foren.02-evernoteforum 01-dev.01-website.05-new.01-evernote-playground So by this point drilling down becomes tedious. P. S.: Let me say though that your system seems interesting, too and if it works for you, that's truly great. I already have had become inspired three times by your posts!

Interesting. I tried this just now and it would work maybe even a little bit faster for the tag collector macro. The problem seems to be though, that the tags received like this are not normalized (for example my tags include Umlauts like "ä" which can be represented as a base character with an umlaut or as a pre composed character, see this for example), which means I'd need to normalize the results before I can match the tags, etc. But maybe I'll give it a try some day. Thanks for suggesting it! I guess I overlooked this possibility earlier, because I manage my tags not only for Evernote, but have a tree of tags, which is used in my filesystem, in my gmail labels my task manager, etc. The tree looks something like this: 00-meta 00-meta.01-setup 00-meta.01-setup.03-reading-writing 00-meta.01-setup.03-reading-writing.00-notes 00-meta.01-setup.03-reading-writing.00-notes.02-evernote This system has many benefits, for example it's kinda easy to remember the path to a certain tag, by just remembering the numbers, which helps in tab completion in the shell. But for Evernote's tag implementation the system is too complex. For example: The mac client's native autocompletion is always starting with the first character. So I'd need to write at least "00-meta.01-setup.03-reading-writing" before the evernote tag "02-evernote" even shows up. Also context is important to my tags. For example a meta tag "00-meta" is used often in the tag tree. Which means that the tree can't be used without writing the full path into the tag, because Evernote assumes that every tag is unique by its name alone. But this in turn means that I can't read my tags in the tag view easily anymore because it'll only show the first 24 characters. So there are some limitations inherent in the way Evernote has implemented tags. And then there is also my wish to be somewhat "platform agnostic" - meaning it should be easy enough to move to a different system, if needed. Most of my limitations and problems are solved by having a note which holds all of my tags in a readable and easily extendable format, like an unordered list. And since I have that list and since that list is also a reference for all my other contexts in which I need to put a thing into a taxonomy, I use this "single source of truth" for my Macro. Drilling down is what I use, too - when creating the taxonomy, but not when tagging itself. Because when your tag tree becomes sufficiently complex, the possibility of multiple places where a certain tag could be in the tree rises too much to make a drill down process work. If I want to tag a note with the tag "evernote", I shouldn't need to think about where the tag is or even could be. What is interesting about this though: drilling down while tagging could be useful for the kind of "process tags" that your screenshot seem to suggest.

There is now a new Version of this Keyboard Maestro Macro available. Here's the introductory blog post: Evernote Tag Autocomplete Macro Version 2 Evernote Autocomplete Macros - v2.kmmacros This is basically a slightly more polished version of what is already available here: ("Evernote - ZKN - Tag Collection2.kmmacros", "Evernote - ZKN - Tag Selection2.kmmacros") and works just as is shown in the Gif below. The difference is that it uses Evernote's Applescript Interface to receive the tags (thanks @DTLow again to point this out to me). ---- This might be a little bit too nerdy for this forum, but I thought it might still be of interest: I created two [Keyboard Maestro](https://www.keyboardmaestro.com/main/) Macros, that can be used to have powerful type ahead/autocompletion search for tags. What you'll need: For the note-based version: A note in Evernote which lists in an unordered list all your tags A Keyboard Maestro macro, which reads/parses that note and keeps a list of your tags: Evernote - ZKN - Tag Collection.kmmacros (this macro assumes you have the aforementioned note is named "Tagliste", you'll have to change the macro accordingly to make it work, ) OR: Evernote - ZKN - Tag Collection2.kmmacros Another Keyboard Maestro macro which uses the results of the other macro to make them searchable: Evernote - ZKN - Tag Selection.kmmacros OR for the new Version: Evernote - ZKN - Tag Selection2.kmmacros Now, if you press ⌃⌥⇧⌘# the tags for tags search will be updated. And if you press ⌥⇧⌘# the tag search will be displayed. This is how it looks in action: P. S.: For anyone who can read German here is a link to my blog with way more words about this: Keyboard Maestro Tag Autocomplete Makro für Evernote unter macOS Evernote - ZKN - Tag Selection.kmmacros Evernote - ZKN - Tag Collection.kmmacros