Jump to content

escapist

Level 1
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

5 Neutral

About escapist

  1. This is still a problem (yes, 4 years later). Absolutely ridiculous. Anyways, I've found that this works most of the time: Select all text in the note (⌘A) Format as a list (⇧⌘U) Remove list formatting (⇧⌘U) Good luck!
  2. This. This right here. It drives me absolutely insane. To reiterate the issue: When you type a hyphen into the tag field, autocomplete fires, accepting the top suggestion, injecting it into the tag field, and moving your cursor to the end of the line so you can begin typing the next tag. Well I wasn't done typing this tag! Why does typing a hyphen mean I'm done typing out a tag? Why would you assume the first alphabetical autocomplete option is the right one? It's a madhouse! A MADHOOOUSE! In short: I expect to be able to type hyphens freely into the tag field without anything clever happening. Typing a hyphen shouldn't do anything automatically. I would expect autocomplete to fire when I type RETURN or COMMA or perhaps TAB. All of these seem pretty typical. Firing autocomplete when the user types a character commonly found in a tag name seems absolutely crazy to me. Here's a video of me being driven to distraction by Evernote's overzealous tag completion: https://cl.ly/3N3h1k2K3N3d (Also: This happens on all Mac clients but just so I don't get asked, I happen to be using v6.8 Beta 2.) (Also also: This does not happen on iOS, where things behave as I would expect. Namely, the result of typing a hyphen is that autocomplete suggestions update, just as if I'd typed any other standard character.)
  3. That particular problem seems to be fixed in Beta 3. There are still some odd things about using tables, though. Here are a few thoughts: Unable to move to next cell down I couldn't find a key combination that would move my cursor down one cell. Tried Return, Cmd+Return, Opt+Return, Shift+Return, Tab, etc. All columns are always flexible width Maybe this is the best way to do it, maybe not. Personally, I find it unintuitive. It's particularly puzzling when the table is set to less than the full width of the note and then the note window is shrunk. The overall table width stays pegged to a percentage of the note width and very quickly becomes unusably narrow. Instead, I would recommend: • Table maintains width until window bounds collide with it, then it shrinks along with the window • Enforce a reasonable min-width for tables or columns Table headers I would love some type of basic support for header rows and columns, even if it's just cosmetic
  4. Super frustrating. Like, really frustrating. Basic resizing of tables and columns is completely borked. http://cl.ly/073w050b3k3y And why can't I attach this video here? a 2MB video is too much to handle? That's frustrating, too. Please download the video to wherever you keep things like that. I don't plan to keep it on my CloudApp account forever.
  5. It seems to me that automatically applying RTF formatting, on the fly, based on Markdown-like syntax is not "Markdown support". It's not "light Markdown support". The feature actively strips the Markdown characters as I enter them.
×
×
  • Create New...