I've left both versions in this thread as they perform almost exactly the same function, for the same reason, but in two different ways. The first version is more programmerly, if you will. It produces a fast, reliable result, but Evernote does not deal with it as expected. If you clip a URL, and use the Evernote menu clipper's fast paste command, it creates a new note with the URL in the body, and the URL as a title. Which is what I was going for. If you do the exact same thing with KM, the note ends up 'Untitled'. v2 is a bit of a kludge just to get a title. It may seem better to some, as we extracted the title of the Web page to use as a title for the note, but it seems less reliable to me, even though it achieves a more useful result.
'Simple' KM macro to paste from Chrome to Evernote in the most heavy handed way possible. This was driven by the HORRIBLE system load of the Evernote Clipper, and Clearly. Both Evernote tools are so brutally slow in Chrome, I don't like to run them. They slow down everything.
This requires that the system Clipper is running, so that it can use the system shortcut 'CTL+CMD+V'.
@CareyB, your macro is a great way to quickly copy the URL to Evernote.
But I almost always need at least some content on the web page. So, I really could not do without the Evernote Clipper.
I’m using Chrome right now and it is very responsive – no delays of any kind.
So I’m not seeing the impact of Evernote Clipper you apparently are.
Could the slowness on your system be due to something else, perhaps some other Chrome extension working badly with Evernote?
You might try disabling all other Chrome extensions except Evernote, and see if that fixes the Chrome performance issue. If that does not fix the issue, then you might want to submit a bug report to Evernote.
Been there, tried all that - and more. I’ve given up. Part of the issue is that the clipper clips to Evernote online, and my macro just pastes it into the local client.
Carey, you may want to update the macro in your OP so new readers will always see the latest version. Of course, be sure to note the new ver# and date updated. This is generally the practice we encourage.
