AlbertR

Yep - and vice versa: You cannot embed tables inside other types of text (bulleted lists, other tables a.s.o.). Looks like this (new) kind of text blocks are allowed only on top level of any nesting rules. But I'm sure (hope for us all) that there will come up nesting possibilities like in Notion 😉

You are right - as I'm used to quit my Windows apps by clicking the "X" right in the title bar (which normally sends a WM_QUIT message to the application to quit itself), I did not see the difference, sorry.

... citing @PinkElephant and adding my need... Recurring Tasks Tagging of Tasks Adding content to tasks, especially URLs / links Showing Tasks in a List View with congruent possibilities (configure, sort, modify, ...)

Sorry for re-posting what I've written before some weeks - but @Austin G promised to investigate this for upcoming versions... So: do we have a chance to get it back in near future? Since we got Tasks, many Legacy users are hot to jump - but surely not without some core features. This is one of them 😉

And BTW: Commands like taskkill /f /fi "imagename eq Evernote*" seem usefull (kills all Evernote-Processes in one action) but also kill Legacy-processes because they carry the same name 😞.

Quitting the app does NOT help. EN-Process keep alive to speed up re-starts. The only way to surely kill them is to use the Task Manager. This methodology is OK in most cases (Legacy did the same). But sometimes it is a pain if a restart is blocked by any broken subprocess 😞. @kbhasi: Yes, with new Tasks feature they invite users to use EN-10 without getting beloved old features running (Import folders, compact and fluidy UI, overall-speed, sparingly resource usage, ...). Their decision - hope they will "support" Legacy for a long time...

Oups, before some months You spent more hope 😉

I'm also using tags with special characters (including "!" as a first character) and found that almost all do work correct even if you use wildcards to select all tags starting with "!poll". The only exception is "<" and ">". By using these starting characters, wildcard do not work. I've a support ticket open around that. Regarding you finding without wildcards: This might be a problem on server site: Legacy maintains a local index to speed up such searches. EN10 is more server-centric. Maybe it takes some time until the index on server is up-to-date to answer your request. I'm sure, your problem will go away after some time (hours?). Even this is true, you should open a support ticket to get a more credible answer 😉

Oups, exactly what I would have recommended 😉 Seems that your launching program (OneNote?) cached the old setting. Unfortunately, even re-installing Legacy will not correct this registry setting so you have to change it on your own... But after that really all programs respect it (Word, Excel, Chrome, IE, ...).

And there is another reason for this simple solution: Templates cannot be instrumented with tags. If you create a "template" in a special notebook, you may supply it with appropriate tags to jump-start your new note.

Are these modifications to Windows Defender settings of higher risk? If not, it would be fine if you could share it to others who are looking for speed enhancements. THX

Just a small addendum: I installed a new computer before 2 days, installed both versions (V10 and Legacy) and started to search within the notes immediately after installing. And whow - V10 seemed to have all notes available immediately. Legacy took a longer time to answer with complete search results. Only after a complete sync, all notes have been found. But after then it was much faster that V10... Conclusion: V10 has a more sophisticated sync methodology - based on what the user needs this moment. But because of more iNet traffic it needs, it sometimes needs more time to sync specific note's content (even it V10 knows, that a note contains what I'm looking for, it needs some time to show me the content). Legacy allways tries to sync everything until it is completely mirrored on your HDD/SSD... From a professional user's point of view, the good old Legacy mode makes more sense: I have the disc space, I have the processor speed and I really need fluent answers even if my iNet performance lacks. For beginners oder semi-professional users, V10 impresses with total cloud functionality across different devices and device types.

Yes it is the right folder - but(as you mentioned correctly) it is not required. It may be not complete because there is no "sync complete" indicator available.

Didn't start at all or simply running into a never-ending loop showing something like "wait..."? (sorry - have a German installation). I had the never ending case and just killed all Evernote processes. Next start was OK.

The only thing I keep in mind after my short hype is its text editor with simple and usefull capabilities to create appealing text (foldable lists, /-keystroke, ...). This page is an example of what I mean: EN-10 - was mir noch fehlt (sorry - German). All other stuff is tooo complicated to maintain (tables, databases, ...). By far not a competitor of EN - but maybe used as an idea generator 😉

"A little unkind" - OK. I've been in charge for development for a long time - such basic functionality should be either on the list of ToDos from the start on (to implement user friendly i18ned SW) or even implicit thinking of developers itself 😉 Meantime I use Legacy - which uses system dates - and AutoHotKey to support key combinations that add dates and times in various formats as I need them. My notes forinstance routinely have valid Creation Dates to sort into chronological order. But this is crazy:

We do not want to pick up the format from somewhere outside EN. We want to have it defined within EN. Is it really such hard to implement a format string like "DD.MM.YY HH:MM" that will be used everywhere inside EN when a date is to be displayed? Every simple (like GreenShot) and more sophisticated programs (like Excel) offer such a possibility. From my point of view this is a finger exercise for computer science students... But for the moment, it would be absolutely OK, to use Windows-settings of "Short date" and "Short time" - as it was the case in Legacy 😉:

Oups - don't exaggerate ;-). No one will reach monthly upload limits. Only the content of your account(s) will be cached unter %appdata%/Evernote. This is app. 5 GB with my ~15 kNotes. Storing such data below %Appdata% is common use in nearly all Windows applications. But it would be fine to get a possibility to move Evernotes' local data to a folder of user's choice like it was possible in Legacy version.

OK, so my idea (not tried out so far) to use "/" and "\" to replace my beloved ">" and "<" might be a bad idea? 😉 At the moment I'll stay with Legacy and wait for an answer to my offical support ticket (that lasts from October last year, got the 3rd ticket-ID but neither a solution nor an explanation - only a "I'm transferring this ticket to our technical support team" from where it was moved to engineering where it got lost)

Sorry, this is only true if the note has not been modified in EN-10. If it is modified (anywhere else - not around the link!) and it is synced back to the cloud, the link is removed. This is completely unacceptable because it secretly changes the content of my note.

Arghl - I cannot see specific meanings of these characters in their search syntax. And even if you're right, they should mention it anywhere in the documentation. I use ">" to point to the future and "<" to mark something in the past - was OK for many, many years and is broken now without a valid reason and without announcing it anywhere. 😡 But THX for looking into it on your side, @Mike P 🙂

Nice - I use a similar system of tags that start with a special character. In my case all tags for workflow tracking start with ">". So "tag:>*" should list all notes within my current workflow like "tag:>0-now" OR "tag:>1-next" OR "tag:>5-wait" OR "tag:>9-finalize". But the result is all the time 😞. Legacy works correct and shows all currently handled notes. This means: Wildcards do work in all cases. I checked it for some other special characters: $ is OK (your example, not used on my side) =, _, @, ~, # and ? are OK (also used in my system) > and < do NOT work (heavily used in my system) others are not checked so far.... ^sorry - ignore this picture - cannot remove it by myself 😞

Legacy allowed to use wildcards I'm tag searches. Example: "tag:y2*" finds notes with tags y2010 OR y2011 OR y2012 OR... Now it is impossible to specify an equivalent search phrase because wildcards are no more supported. Using keyword "any:" is not a solution because it cannot be combined with something an "and:".

I'm in contact with Filterize and they spoke about other (not all) users. Up to now they have no glue about reasons 😞

Yep. At least changes on Tag should not change note's update date. Tagging is often used temporarily to shrink down search result.