Jump to content

ziru

Level 2
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

11 Neutral

1 Follower

About ziru

  1. You are right that Code Block might not be justified as the top priority. It actually came out as one of the experimental features created during the company's hackweek in Jan. This was mentioned in the forum post of the 6.5 beta 1. Since we already have this feature baked in internal builds, we'd like to share with other Evernote users who also want this (off by default) and like to see how big the audience it would be.
  2. The Mac App Store version has been submitted and will be released soon. The Direct Download version can be downloaded here.
  3. I don't know how to change the font, but in case you want to change the font size, here is how: http://cl.ly/3H2R2D1O2D1A
  4. Re @kominetz and @fnl: See this earlier post regarding why we chose “⌘+” / “⌘-” for the Zoom feature and “⌘>” / “⌘<” for the font size change feature. As to the Zoom feature, it is off by default. You need to go to Preferences -> Software Update -> Enable zoom. COMMAND-+ and COMMAND-SHIFT-+ are treated as the same thing in Evernote, if you enabled the Zoom feature. Does that not work for you?
  5. There are a few ways you can create a new Code Block (after enabling the Code Block feature from Preferences): - Click the {} button from the UI formatting bar (with no text selected) - Press Cmd+Ctrl+B - Type ``` and then press Enter (if you have Auto Format feature enabled in Preferences -> Formatting) Once a new Code Block is created, the cursor should be placed within the empty Code Block. You can then use Cmd+V or context menu to paste code from your code editor into the note. Another possible way is to first paste the code into the editor as usual, and then select all text of the code, and then click the {} button or press Cmd+Ctrl+B to convert the currently selected text into a Code Block. Hope that helps.
  6. Can you please provide the exact version number of the Evernote app (from the menu Evernote -> About)?
  7. Sounds weird. I cannot reproduce it. Does anyone else see this issue? What tag name do you use? And what is the search query? Thanks,
  8. We do have some support for advanced searches, but not yet have a friendly UI. Here is the search grammar page: https://dev.evernote.com/doc/articles/search_grammar.php You might be interested to read the sections about the use of "created:" and "updated:" operators. Back to your specific cases: "for all notes created on Oct. 15th" - you can use this query: "created:20151015 -created:20151016" - it will return notes created on or after 10/15, but before 10/16 "for all notes created between Oct 15th and Oct 20th" - you can use this query: "created:20151015 -created:20151021" - it will return notes created on or after 10/15, but before 10/21
  9. It seems that you might have both the Direct Download version and the App Store version on your machine. You could try to delete the preferences (for both Direct Download and App Store versions), if you are ok with losing your local customizations. 1. Quit the Evernote app and the helper2. Delete your preferences using the Terminal app (Note: your customized preferences will be gone.)defaults delete ~/Library/Preferences/com.evernote.Evernotedefaults delete ~/Library/Containers/com.evernote.Evernote/Data/Library/Preferences/com.evernote.Evernote3. Start the Direct Download version of Evernote app, aka 6.3 beta1.Hope it helps.
  10. This sounds like a bug. Do you have the reproducible steps? Thanks, Updated: I think I have found the way to reproduce this. Will file a ticket to get it fixed.
  11. If you are using the latest 6.2 release, you can find those 40 notes with DN: by searching for "DN:". It should stop the prefix matching, and should not return notes with DNS/DNA/midnight but not the exact word DN at all. Unfortunately, we have a known issue with our search highlighting, and so it could still highlight DNA, midnight, DNS, etc. We are working on fixing this misleading issue as well.
  12. Thanks for the response, but... Why did you switch from double quotes to single quotes? It is my experience that single quotes do not work correctly in Evernote Windows. My bad. I mean without double quotes for the prefix matching by default, and using double quotes to stop prefix matching.
  13. You can put quotes around DN: to stop the default prefix matching, aka search for "DN:" (with the double quotes). It should match notes with "DN", "DN:", "dn=", but not "DNS", "dnoonnan". As to the symbols like colon, Evernote fulltext search currently does not index such symbols. Most symbols are treated as word delimiters, instead of part of the word. Example 1: if the note contains DN-ABC, you can find this note by DN, or ABC. Evernote note search does not cover infix matching (which will not only slow down the search if # of notes become big, but also return many unwanted results). That is, searching for N, BC, C will not get you the above note. Example 2: if the note contains Latitude:51.23, you can find this note by latitude, or 51.23. If we indexed symbols like ':' and treat it as part of the word, then the user will only no longer be able find this note by 51.23, because we do not support infix matching. With the above being said, there are some uses of symbols we want to reevaluate sometime. For example, the pound character in "C#" or the leading at symbol in "@Awfki". Such uses should better be considered as part of the word, rather than a word delimiter.
  14. We did care about users on Macbook Air, and use old models of Macbook Air with dual cores and even less RAM to test internally, against accounts with lots of notes, and accounts with smaller number of notes but with big attachments. Still, our testing might not be comprehensive, and we would like to know how it works out for real users including you. We do expect an initial CPU spike for some users as Marcus mentioned in the release note, but expect the usage will drop after a couple of minutes. Also, the reindexing is supposed to run at background and not blocking UI. However, our testing might not be comprehensive, and we would like to know how it works out for real users including you. Do you mind letting us know how long the app run at high CPU usage? Is this the first-time sync or your account has already downsynced everything before this upgrade? If OK, please send your activity log, and better with the process sampling result to Marcus. We would definitely want to take a look. Thanks. Btw, here is how to get a sampling for a unresponsive process on Mac: http://www.thexlab.com/faqs/activitymonitor.html#AM-Sample-Process
  15. How do we know when it is done? I have a Macbook (2015) and I have no clue when it is busy. There is no HD light and indexing isn't a particularly processor intensive activity. I have almost 8,000 notes at around 7GB in size. I didn't leave it open for a long period of time, maybe 30-45min max before I closed the lid and went to work. Should I leave it open for an hour or more tonight? We do emit a completion message in activity log, but not via UI. You don't need to wait for the completion, nor leave it open at night. The reindexing will continue when you open the lid again. Even if you quit the app, it will pick up the job when you open the app again. For most users, we hope the reindexing will go unnoticeably.
×
×
  • Create New...