Search the Community
Showing results for tags 'bullet points'.
Found 3 results
-
As seen from the screenshots, when I annotate a screenshot that I've captured and pasted below some bullet points, the appearance of the bullet point above it changes. The bullet point that was hollow (indented one level further than normal bullet points) becomes filled. Any work arounds/ways to reverse would be appreciated. Also just hoping to flag this as a but so it might be fixed in a future update? Before annotating a pasted screenshot: After annotating a pasted screenshot: Notice how the bullet point directly above the annotated image has changed! -
I've noticed that I can't put a code block or table under a bullet points. Is this intentional or is it some kind of bug? I'm running Evernote under Windows 10.
-
- 1
-
-
- code block
- tables
- (and 1 more)
-
Recently bullet points stopped working for me in my usual workflow. I often copy and paste text and links from other sources into bullet lists. So before I could start a bullet list, paste a link, hit enter, the next bullet point appears. Now, whenever I paste in a bullet point and hit enter, then I just get a blank space and bulleting is then completely broken. even without pasting, I can't create a new bullet item unless previous ones exist. I've tried various things to attempt to fix up the list but it remains broken. I saw the Windows thread on bullet points which indicates this feature has a history of problems. The only workaround I have is to create a template list with a bunch of entries as in * x * x * x * x In this case I can replace an "x" by pasting the link and then use the next "x". But this is a PITA when for instance I want an new bullet item between two I've already pasted into as in: * x * x * I already pasted here * And here * x * x Now I'm screwed again. Unless I use the existing x's to create new one's and re-copy and paste those items leaving an entry between for the new item I want to paste. This is not acceptable workflow. Is this a known issue? Is there any known work around/fix for this issue?
