Jump to content

eric99

Level 4
  • Posts

    1,507
  • Joined

  • Days Won

    9

Everything posted by eric99

  1. locked for editing, but they are still fully readable
  2. Good to know that there is a EN alternative but out of curiosity I installed One Note again and it seems even more bloated and counter intuitive than before, no dark theme either...
  3. What import tool have you used? Have you lost any (meta) info during the process?
  4. Yes, on windows overridden settings in the config.json aren't touched by a new update. Sure, the 100 selections are sufficient for daily usage but not for reorganizing notebooks and global tagging. EN should fix this first before terminating legacy completely.
  5. Do you see these attachments in your enex and html backups ?
  6. It works in my Chrome browser with a note of 198000 words, but as I said, my windows PC has 16 GB ram, how much has your PC?
  7. Can please specify more precisely how long your note is (in MB) I have no problem with a note of 100 MB of images or with a text note of 2MB but I have to say that my windows PC has 16 MB of ram and 1TB SSD
  8. I agree, this is a win-win : immediate sync when the user needs it and less load on the server because the sync polling frequency can be reduced.
  9. Yeah, I agree but I'm afraid that's the best we can expect from this generation of web developers : everything is written in layers on layers of bloated javascript code.
  10. There is some hope that collaborative editing will work because they probably haven't implemented it themselves. I think/hope they've integrated one of the existing proofed javascript libraries for that. Of course they can still mess it up in the integration, but at least the core functionality should run smoothly.
  11. the search differs at some points, for instance: tag:* returns all notes in the normal search and only a few notes in the 'link search' . Also the normal search looks in the whole note, the 'link search' in the title only. About your example tag:*mar : a wildcard isn't supported in front of the string, only at the end like this : tag:gramm* This works even if the tag has spaces in the name.
  12. " New! Offline Notes on mobile allows access to important notes offline from anywhere. " Is this new? Maybe they mean that it is finally working now?
  13. It's a little bit different, the trick is if you start the query with "intitle:* " followed by the rest of your query, it will search in the note body as well. Example: "intitle:* john doe" will search in the full note for "john doe" . "john doe" will search only in the titles for "john doe". It's a little bit weird that we have to suppress the implicit intitle: by the prefix intitle:*
  14. why do you think that it should be polled, why can't it be pushed instead? Anyway, collaborative editing needs faster sync to prevent conflicts...
  15. I just found out that it returns all results if you type explicitly "intitle:* " in front of the rest of your query: example: "intitle:* john doe"
  16. Thanks, that explains it, but then, what is this restriction good for? Is a full note search possible as well?
  17. It is not that I want to scroll manually through the whole list, but I tried to open it because I noticed that the search results were incomplete, just a small subset from the regular search. Has anyone checked that already on a large notebook?
  18. Agreed, they might have detected the bug but decided to release without solving it
  19. yeah, nice try but they released without testing: it hangs with my notebook of 3700 notes (windows client)
  20. Now you hit the nail on the head: a unified code base for very different platforms leads to this kind of problems. I've seen such 'unification' attempts too often, it's full of specific conditional code for each individual platform resulting in multiple programs entangled in one 'unified' monolithic program.
×
×
  • Create New...